Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
HomeFree Questions
Showing posts with label Mainframe Tools. Show all posts
Changeman Tools Tutorials
CHANGEMAN
Changeman is version control utility of HOUSEHOLD which manages and automates t
he process of implementing applications/systems software from a development envi
ronment to the production environment. Changeman uses the strategy of packages w
hich will include all the information which has to be move into the production e
nvironment. Change man does this job by managing movement of change package inf
ormation in five distinct environments
1) Development
The development environment is used for application progr
am development. The development environment may or may not exists under the cont
rol of changeman
2) Staging
The staging environment is a transition environment
, where all the testing and editing of the work libraries are initiated
3) Baseline
The baseline environment is a copy of the current pr
oduction libraries which are managed by changeman. These libraries are used in
the case of application testing
4) Production
The production environment is a set of libraries where
the production version of application resides
5) Backup
The backup environment consists of the libraries whi
ch contains the previous versions of production software
A changeman package is a logical definition for the collection of items associa
ted with a change or development request. The associated items include work data
sets which are managed by changeman. In a typical change request the following
can be the associated members
1)
2)
3)
4)
5)
6)
Source Code
Copy Books
Load Modules
DBRM libraries
Service request
JCL
When a change man package is created, it creates a set of data sets to store all
the associated items or termed as COMPONENTS. The data sets are usually a Parti
tioned Organization ones with a unique naming convention. All the changeman con
trolled data sets will have a high level qualifier as OIN1. The data set will b
e something like
PICM.CP000000.OIN1. #NNNNNN.??? ,
where #NNNNNNN is the Changeman package number which the item or component is as
sociated, and ??? is the associated member or component type.
Project Pneumonic:
Within the Package Master, HOUSEHOLD has divided work up by Project Mnemonics . Pro
jects have been used to divide change management by application support groups l
ike HLFG, OIN1 etc. There is internal security within CM that allows specificall
y named components to belong only to one project. For example, a payroll source
member may be secured so that only payroll projects Pneumonic are authorized to
access it.
There are different stages before installing the package and they are DEVelopmen
t, PROmtion, AUDit trailing, FReeZing, APProval etc. When a package is created
it will be in DEV status, once the modules/programs are checked into the package
and promoted to test, the package will be in promote status. AUDit trailing wil
l be done for that package to make sure that everything is okay. Later the packa
ge will be FRoZEn and it will be in FRZ status. Once the package gets to FRZ sta
tus nothing can be done to the programs/modules involved with it. The last stage
is APProval state, i.e., the managers here have to approve our
changes and once all the approvals are obtained the package will be moved into
production on the install date specified while creating the package. This is jus
t a brief idea of how the changeman works.
WORKING WITH CHANGEMAN
The changeman utility can be accessed from the ISPF main menu by giving a C. The
following screen will be displayed
--- CHANGE MAN
OPTION ===>
1 Build
2 Freeze
3 Promote
4 Approve
5 List
B Backout
C CDF
D Delete
L Log
N Notify
O OFMlist
Q Query
R Revert
T Tutorial
X Exit
5) When all of the components in a change package have been tested and user si
gn-off has been obtained, you must submit the change package for AUDIT. The audi
t process verifies whether or not all of your components are in synch. For examp
le, if no changes are made to a component, the AUDIT will detect that staging an
d baseline libraries are duplicate.
6) After running a successful audit, the next step is to FREEZE the package. A
change package must been in FRZ status before the Approval process can take pla
ce. Once a package is in the FROZEN stage you can only browse the components
7) All normal planned application packages must be approved by PEER, MANAGER, AP
PLICATIONS CCB Approvers and CHANGE MANAGEMNENT Implementers.
8)
9) Once the necessary approvals have been obtained by CM, the package is ready
for installation. During the installation, CM submits the migration jobs to cop
y all the components from staging libraries to production libraries. Once this i
s complete, CM sends a BASELINE RIPPLE message to the creator of the package. This
indicates all current and backup versions have been successfully updated. In th
e event of a back-out, CM will take the current version (0) generation and copy
the -1 version into baseline
To access a particular package where you have the components to be edited or cha
nged, note the Package number it will be usually like OIN1000060, OIN1000092
etc. Enter the option 5 (LIST) from the changeman menu got through ISPF main menu.
The below screen is the outline when you enter on the LIST option
--------------------------- PACKAGE LIST PARAMETERS --------------------------COMMAND ===>
SPECIFY SELECTION CRITERIA:
PACKAGE ID
===> OIN1000092 (Full name or pattern; blank for list,
or '*' for all packages)
PACKAGE STATUS
===>
(DEV, FRZ, APR, REJ, DIS, INS,
BAS, BAK, OPN, CLO, TCC or DEL)
CREATOR'S TSO-ID
===>
WORK REQUEST ID
===>
DEPARTMENT
===>
PACKAGE LEVEL
===>
(1-Simple, 2-Complex,
3-Super, 4-Participating)
PACKAGE TYPE
===>
(Planned or Unplanned)
PACKAGE TIME SPAN
===>
(Permanent or Temporary)
FROM INSTALL DATE
===>
(YYYYMMDD)
TO INSTALL DATE
===>
(YYYYMMDD)
FROM CREATION DATE
===>
(YYYYMMDD)
TO CREATION DATE
===>
(YYYYMMDD)
OTHER PARAMETERS
===>
(Y/N)
Press ENTER to process; Enter END command to exit.
The PACKAGE-ID will be the package id which was last accessed by you. If you wa
nt to accesses a package OIN1000092. Enter the package OIN1000092 in the package
-id field and hit enter which will display you the package list screen which is
displayed below.
COMMAND ===>
SCROLL ===> CSR
PACKAGE ID STA INSTALL LVL TYPE
WORK REQUEST DEPT PROMOTE AUD CREATOR
10) __ OIN1000092 DEV 20001231 SMPL PLN/PRM HIERARCHY
HFC LEVEL1
VEN63
1
There are two types of commands which can be entered first is on the command l
ine and second on the underscores before the package name. Here are some of the
command commands which you usually enter on the package prompts
1) S1
Stage components (Dev Lib list)
2) C1
Check out components (Baseline/promotion)
3) S2
Stage components (Package list)
4) QP
Query change package information
5) AP
Audit a package
6) PD
Promotion and Demotion
7) F1
Freezing a package online
Check out Components (Option C1)
If a component (program or copybook or subroutine, assembler table e
tc) is present in the baseline library which is nothing but the group of changem
an Partitioned datasets (PDS). A component when checked out into a changeman pa
ckage should be assigned with a type. The component type should be correct beca
use as mentioned previously changeman generates JCLS to compile the component au
tomatically. To tell changeman to use the correct procedure to use for compilati
on we should specify the type. For e.g. if we are having a simple COBOL program,
then the compilation should be done only to create and a load module so changem
an identifies this and uses a procedure. If there is COBOL program with DB2 acc
ess then changeman should be told to compile the program with a DB2 option i.e.
generate a JCL which uses procedure for compiling a DB2 cobol program. So depend
ing on the type the sources for the baseline library are defined to change.. As
discussed previously, For each type we incorporate into a package it will go as
member to a partitioned group of datasets created at the time of creating the pa
ckage. The following are component types supported by changeman
LIB DESCRIPTION
_ HCA CICS Online Assembler
_ HCC CICS Online COBOL: load to CLM
_ HC2 CICS Online COBOL 2: load to CLM
_ HCD CICS Online COBOL w/DB2: load to CLM
_ HC4 CICS Online COBOL 2 w/DB2: load to CLM
_ HC5 CICS Online COBOL LE w/DB2: load to CLM
_ HC6 CICS Online COBOL LE: load to CL6
_ NDM NDM Processes (sys5.ndm.process)
_ NDJ NDM Jobs (HFCP.JOBLIB)
_ HBA Batch Assembler
_ HBC Batch COBOL: load to BLM
_ HB2 Batch COBOL 2: load to BLM
_ HBD Batch COBOL w/DB2: load to BLM
_ HB3 Batch COBOL LE
_ HB4 Batch COBOL 2 w/DB2: load to BLM
_ HB5 Batch COBOL 370 w/DB2: load to BLM
_ HCM CICS Online MAPs: load to MAP & CP1
_ DBR DBRM Library DB2 System
_ DBB DB2 Bind Control Cards for Plans & Pkgs
_ DCL DCLGEN Copybooks
_ RUN DB2 Run Cards
_
_
_
_
_
_
BLM
CLM
CL6
MAP
CT1
CP1
_
_
_
_
_
_
_
_
_
JB1
PR1
CC1
CC2
DMS
LST
XP1
CPY
LOD
JOBs:
PROCs:
Control Cards:
Control Cards (HFCP.CTLCARD)
DMS Control Cards
Compile Listing Library
Express: Move from test to production
Dummy, required by Change Man. DO NOT USE
Dummy, required by Change Man. DO NOT USE
The following are the corresponding libraries or partitioned datasets which are
created for a sample package OIN1000092
LIB
HB5
DBR
DBB
RUN
BLM
CP1
JB1
PR1
LST
CPY
LOD
The following are the baseline libraries that changeman searches when you reques
t change man to check out any component the type and the corresponding datasets
searched are also mentioned.
LIB
HCA
HCC
HC2
HCD
HC4
HC5
HC6
NDJ
NDM
HBA
HBC
HB2
HB3
HBD
HB5
HB4
HCM
DBR
DBB
DCL
RUN
BLM
CLM
CL6
MAP
CT1
CP1
JB1
PO00.CP000000.HFNP.SRX
PO00.CP000000.HFNP.SRX
PO00.CP000000.HFNP.DBR
PO00.CP000000.HFNP.BND
PO00.CP000000.HFNP.DCL
PO00.CP000000.HFNP.RUN
PO00.CP000000.HFNP.LNK
PO00.CP000000.HFNP.PGM
PO00.CP000000.HFNP.PGM
PO00.CP000000.HFNP.PGM
PO00.CP000000.HFNP.SRX
PO00.CP000000.HFNP.CPY
PO00.CP000000.HFNP.JCL
PR1
LST
CC1
CC2
DMS
XP1
LOD
CPY
PO00.CP000000.HFNP.PRC
PO00.CP000000.HFNP.LST
PO00.CP000000.HFNP.CTC
HFCP.CTLCARD
PO00.CP000000.HFNP.DMS
SYS4.CHGMAN.DUMMY.EXPRESS
SYS4.CHGMAN.DUMMY.LOD
SYS4.CHGMAN.DUMMY.CPY
Coming back to the steps for checking out the component. Let us take the example
of checking out a component POTEB010 which is BATCH COBOL PROGRAM WHICH USES DB
2. Enter C1 at the package prompt the following screen will be displayed.
----------------------------------- CHECKOUT ---------------------------------OPTION ===>
L - List libraries where component is located
PACKAGE ID
COMPONENT NAME
===> POTEB010
LIBRARY TYPE
LANGUAGE
SOURCE LIBRARY
===> HB5
===>
===> 0
CHECK OUT TO
===> S
PERSONAL LIBRARY ===>
LIBRARY DSORG
===>
(Y/N)
(1-Online, 2-Batch)
(Y/N)
out
As described previously changeman allows you to stage from the PANVALET LIBRARY,
PARTITIONED DATASETS(PERSONAL OR OTHERS),SEQUENTIAL FILE as a component to pack
age. Specify the location of the component you want to stage in the appropriate
fields and as in the check out option specify the library type and language of
the component. In our example case of POTEB020 it is HB5. Now IF you are stagi
ng from the PANVALET library give the ORGANIZATION as PAN and if you are staging f
rom a sequential dataset then mention organization as SEQ and mention the name in
which you want to assign for the component in the package in the STAGE NAME. so
after entering the request my screen will appear as
--------------------- STAGE: FROM DEVELOPMENT ------------------- COMMAND ===>
PACKAGE ID: OIN1000092 STATUS: DEV
INSTALL DATE: 20000903
ISPF LIBRARY:
PROJECT ===>
GROUP
===>
TYPE
===>
MEMBER
===> (Blank or pattern for list; * for all members)
OTHER PARTITIONED OR SEQUENTIAL DATASET:
DATASET NAME ===> 'dh47.ven631.pgms(poteb020)'
ORGANIZATION ===> pds
(PDS, SEQ, PAN, LIB, OTH)
LIBRARY TYPE
===> HB5
(Blank for list)
LANGUAGE
===> cobol370 (Blank for list;applies to source code)
STAGE NAME
===>
(Optional if organization not SEQ)
CONFIRM REQUEST ===> YES
(Y/N)
STAGE MODE
===> 1
(1-Foreground, 2-Batch)
SUPPRESS MESSAGES ===>
(Y/N; applies to batch stage)
Unlike checkout staging compiles the program before staging into the package spe
cified, so when you ENTER to process the staging of the component in this screen i
t will show you the options for compilations, which is similar to compilation sc
reens of the compile option of a component from a package. The first screen wil
l appear as shown below.
------------------------- STAGE: COMPILE AND LINK EDIT -----------------------COMMAND ===>
PACKAGE ID: OIN1000092
STAGED NAME:
LIBRARY TYPE:
LANGUAGE:
DATASET NAME:
STATUS: DEV
POTEB020
HB5 - Batch COBOL 370 w/DB2: load to BLM
COBOL370
DH47.VEN631.PGMS
COMPILE PROCEDURE ===> COBOL370 (Blank for list; ? for designated procedure)
COMPILE PARMS
===>
(Enter JOB Name for PROCs requiring associated JOB for JCLCHECK)
LINK EDIT PARMS ===>
DB2 PRE-COMPILE ===> Y
(Y/N)
OTHER OPTIONS
===> YES
(Y to display other options)
JOB STATEMENT INFORMATION:
===> //VEN631E JOB (H54D,ITIT),'RAVI',
===> //
CLASS=S,
===> //
NOTIFY=VEN631,
===> //
MSGCLASS=T
<=== CHANGE ACCORDINGLY_____
Press ENTER to process; Enter END command to exit.
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Precaution to be taken in this screen is to verify if the Job log is mentioned i
n the JOB STATEMENT information, if not please key in the above information chan
ging the user-id of VEN631 to yours. The above is initial screen displayed befo
re submitting a job of compilation and link edit.
ENTER in the screen will show y
ou the compilation and link-edit parameters that is required for the program.
If the program has a DB2 attachment then the next screen will ask you to select
the DB2 system where the program is going to be attached. Select the DB2 system
by saying a S in the prompt of the systems as below and ENTER
---- DB2 PHYSICAL SUBSYSTEMS ---------- Row 1 to 4 of 4
COMMAND ===>
SCROLL ===> CSR
VERSION ===> ________________________________________________________
Enter S to select a DB2 subsystem and continue.
Enter END command to exit.
_
_
S
_
DB2
REMOTE
SUBSYS SITE
DB2T
DSNP
DB2D
DBLP
DB2 SYSTEM
LOAD LIBRARY
SYS4.DB2.DB2D.SDSNLOAD
SYS4.DB2.DSNP.SDSNLOAD
SYS4.DB2.DB2D.SDSNLOAD
DB2PHFC.DSNLOAD
TYPE: HB5
COMPILE ONLY
===>
CICS PRE-COMPILE
===>
EASYTRIEVE NO NAME ===>
FORMAT TO IMSTEST ===>
(TEST MFS IS DEFAULT)
JCK FULL LISTING
USER OPTION 11
USER OPTION 13
USER OPTION 15
USER OPTION 17
USER OPTION 19
===>
===>
===>
===>
===>
===>
LANGUAGE: COBOL370
??? IMS DLITCBL ENTRY
DROP INCLUDE STMTS
XPEDITER COMPILE
INCLUDE MQSERIES
USER
USER
USER
USER
USER
USER
OPTION
OPTION
OPTION
OPTION
OPTION
OPTION
10
12
14
16
18
20
===>
===>
===>
===>
===>
===>
===>
===>
===>
===>
Hitting Enter in this screen will submit a job for compilation. Note down the job
name and Job number for the reference for any compilation and link edit mistakes
.
The extra step you should do in the checkout is to edit and recompile so that it
will be in ready for testing.
PACKAGE LIST(S2)
Package list is to view the components attached with the package. To view the pa
ckage list on the package prompt enter the S2
as displayed below
----------------------------- CHANGE PACKAGE LIST ------------ Row 1 to 1 of 1
COMMAND ===>
SCROLL ===> CSR
PACKAGE ID STA INSTALL LVL TYPE
WORK REQUEST DEPT PROMOTE AUD CREATOR
S2 OIN1000187 DEV 20001231 SMPL PLN/PRM
HTS
VEN631
******************************* Bottom of data ********************************
You will be getting a screen as displayed below showing the list of members.
------------------------- STAGE: OIN1000023 COMPONENTS ------- Row 1 to 3 of 3
COMMAND ===>
SCROLL ===> CSR
NAME TYPE STATUS
CHANGED
LANGUAGE PROCNAME
ID
REQUEST
__ BUSUNIT DBB ACTIVE 20001030 080517
VEN631
__ BUSUNIT HB5 ACTIVE 20001102 083720 COBOL370 COBOL370 VEN631
__ POTEB020 HB5 ACTIVE 20001101 125342 COBOL2 COBOL370
VEN631
******************************* Bottom of data ********************************
The Members of the package is displayed in the alphabetic order, The various col
umns specifies characteristic of the Components.
Name : Specifies the name of the component
Type : Specifies the library type of the component
Status :Specifies the current status of the component saying where it is compile
d(ACTIVE), edited but not compiled (INCOMP),Frozen (FROZEN),Checked out(Check ou
t).
Changed : Specifies the date and time when the component was last modified
Language:
Language of the Component
Procname: Procedure used to compile the component when submitting a job for comp
ilation
ID
: Indicates the ID of the person who has last compiled, edited or
promoted the component.
Request :
Message field which prints the request who have made to the
component if you are doing some kind of editing, browsing etc.
Editing, Browse and recompiling a Component
After doing a list on the components you may have to edit, browse or
recompile the component according to the need. For editing the component first
position the cursor on the component s prompt on the screen mentioned and Enter a
E , the screen opens the component for editing, after editing if you want to sav
e the changes you have to go through a compilation cycle (mentioned above) other
wise all the changes will be lost. Change man automatically indicates the scre
ens for recompilation (mentioned above) plus two screens ahead of compilation sc
reens showing the changes made. Do the full cycle of compilation, even though yo
u are sure that there will be compilation errors.
Let us take for example you are going to edit the component POTEB020
in the above package. Put an E in from of the component as displayed below and hi
t Enter
------------------------- STAGE: OIN1000023 COMPONENTS ------- Row 1 to 3 of 3
COMMAND ===>
SCROLL ===> CSR
NAME TYPE STATUS
CHANGED
LANGUAGE PROCNAME
ID
REQUEST
_ BUSUNIT DBB ACTIVE 20001030 080517
VEN631
__ BUSUNIT HB5 ACTIVE 20001102 083720 COBOL370 COBOL370 VEN631
E POTEB020 HB5 ACTIVE 20001101 125342 COBOL2 COBOL370 VEN631
******************************* Bottom of data ********************************
You will get the edit screen for the POTEB020 program showing the source code.
Let us say you have edited the programs name to XXXX , When you end the editing pro
cess the next screen displayed will show you where the changes were made like be
low.
The differences are mentioned with a D and I indicating Deleted and Inserted lines i
n the old existing component and the changed component respectively. Press the f
unction key F3 to quit from this screen
Menu Utilities Compilers Help
BROWSE
D131.VEN631.CMN00307.T1604049.OUTLIST
Line 00000000 Col 001 080
Command ===>
Scroll ===> CSR
********************************* Top of Data **********************************
S E R C M P A R (MVS-3.1.1 - 1997/213)
CHSERV
THURSDAY NOVE
SYSUT1=PICM.CP000000.OIN1.#000175.HB2(CELETRS),SYSUT2=D131.VEN631.CMN00307.T1604
000100 IDENTIFICATION DIVISION.
000200 PROGRAM-ID.
POTEB020.
++++++++|+++.+<++1++++.++++2++++.++++3++++.++++4++++.++++5++++.++++6++++.++++7+>
D
000300 AUTHOR.
Ravi K Gummadapu.
--------|---.----1----.----2----.----3----.----4----.----5----.----6----.----7-I
000300 AUTHOR.
Ravi K Gummadapu..
++++++++|+++.+<++1++++.++++2++++.++++3++++.++++4++++.++++5++++.++++6++++.++++7+>
000400******************************************************************
000500* 08/15/99 SR00084 - CUSTOMER SERVICE LETTER PROJECT
000600* EXTRACT CUSTOMER RECORDS FOR THOSE WHO HAVE INSURANCE ON
000700* THEIR LOANS. LETTERS WILL BE GENERATED BASED ON THE FILE
000800* CREATED IN THIS PROGRAM.
SER71I - END OF TEXT ON FILE SYSUT1
SER72I - END OF TEXT ON FILE SYSUT2
SER75I - RECORDS PROCESSED: SYSUT1(257)/SYSUT2(257),DIFFERENCES(1)
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Pressing the function key F3 gives you the below screen which queries you to keep
the outlist dataset,to print it or to delete. Usually the option is to delete D th
e outlist dataset showing the difference.
------------------------ COMPARISON REPORT DISPOSITION -----------------------OPTION ===>
REPORT DATASET NAME:
'D131.VEN631.CMN00307.T1604049.OUTLIST'
D - Delete
K - Keep
PD - Print and Delete
PK - Print and Keep
JOB STATEMENT INFORMATION IF DISPOSITION IS PD OR PK:
===> //VEN631E JOB (H54D,ITIT),'RAVI',
<=== CHANGE ACCORDINGLY_____
===> //
CLASS=S,
<=== CHANGE ACCORDINGLY_____
===> //
NOTIFY=VEN631,
<=== CHANGE ACCORDINGLY_____
===> //
MSGCLASS=T
<=== CHANGE ACCORDINGLY_____
Press ENTER or END to process
Enter CANCEL command to exit without saving changes.
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Then what follows will be compilation and Link-edit screen discussed previously.
To browse a Component Just put B in the prompt of the component and enter it will
display you the component contents.
To recompile the component put a R in the prompt of the component and Enter to ge
t the same compile screens mentioned above. This is usually done when you want
to recompile without editing the component. A component can be recompiled only
when the status of the component is in the ACTIVE or INCOMP stage.
Note: When a package is FROZEN or when the install date has elapsed then the co
mponent in the package are unusable until the status is changed or install date
is modified.
What does Compilation do to the component?
When a component is edit or recompiled, the status of the component becomes INCO
MP. If the Compilation is successfully, the status changes back to ACTIVE. Th
is can be seen only be refreshing the PACKAGE LIST., i.e. by saying F3 in the pac
kage list and entering the package list command S2 again. Compilation and link-e
dit creates a load module in the package PDS i.e. it creates a load module and s
tores it in the load library created by the package at the time of package s crea
tion.
PROMOTION AND DEMOTION(PD)
For testing purpose, it is needed that all the load modules created should be p
resent in the test load libraries, and in case of the DB2 programs a plan has to
be created in addition to the load-module. All this functionality are done when
you are PROMOTING a component. DEMOTING reverses the previous promotion activ
ity and restores the previously existing load libraries. When you are promoting
the components in the package, you have the option for promoting all the compone
nts or promoting just one component or a list of components at a time. But ensur
e that before doing the Promotion the component is compiled successfully without
any errors. For PROMOTING ENTER A PD
in the package list screen after ending th
e S2 option i.e. on the screen which looks like the below displayed one
NOTE: First time Promoting a package should be FULL PROMOTION.
----------------------------- CHANGE PACKAGE LIST ------------ Row 1 to 1 of 1
COMMAND ===>
SCROLL ===> CSR
PACKAGE ID STA INSTALL LVL TYPE
WORK REQUEST DEPT PROMOTE AUD CREATOR
PD OIN1000023 DEV 20001231 SMPL PLN/PRM
HTS
VEN631
******************************* Bottom of data ********************************
It will prompt you with a panel display below which allows to specify the option
s of Promotion, Demotion or Overlay(whether you are going to overlay some other s
load module or not). The columns under the entry fields mentions the history of
the promotion and demotion activity done on this package by different persons. A
fter Entering
the desired option in the action field say P you will get a screen l
ike the below displayed one.
The next panel may be a PROMOTION/DEMOTION PANEL, the one displayed below is a p
romotion panel. The example we are going to take is to promote a component POTE
B020 of the above-mentioned package.
---------------------------- PROMOTE CHANGE PACKAGE -------- Row 1 to 10 of 17
COMMAND ===>
SCROLL ===> CSR
PACKAGE ID: OIN1000092 CREATOR: VEN631
===> p
===> B
===> 1
(Y-Yes or N-No)
===> //
===> //
NOTIFY=VEN631,
MSGCLASS=T
IMPORTANT NOTES:
C H A N G E M A N
I N F O
PACKAGE PROMOTION:
LEVEL 1
LEVEL 2
LEVEL 3
HITRGI2/CICSD0U0
HITRGP2/CICSQ0U0
HITRGJ2/CICSD0U1
THE PROG
AT THIS TIME DB2 WILL BE SHARED ACROSS THE LEVELS SO IN THIS CASE YOU
CANNOT TEST THE SAME PROGRAM IN MULTIPLE REGIONS BECAUSE WHEN THE OTHER PERSON P
ROMOTES(BINDS) THEIR PROGRAM THE FIRST PROMOTE(BIND) WILL NO LONGER BE IN EFFEC
T
NON-DB2 PROGRAMS CAN BE TESTED IN MULTIPLE REGIONS CONCURRENTLY
BECAUSE THE LOAD LIBRARIES ARE UNIQUE FOR EACH REGION
-------------------------------------------- THE END ---------------------------------------------------------
Progrrams
Sample Mainframe Program's
SQL Codes
TSO/ISPF
VSAM
VSAM Program's
VSAM Tutorials
MAINFRAME PROGRAM'S
JCL Sample Program's
VSAM Sample Program's
DB2 Sample Program's
COBOL Sample Program's
CICS Sample Program's
SUBSCRIBE TO
Posts
All Comments
TOTAL PAGEVIEWS
SUBSCRIBE VIA EMAIL
Subscribe
Delivered by FeedBurner
ABOUT ME
My photo
M siva raman
Gingee, Tamilnadu, India
View my complete profile
MAINFRAME230
Loading