| |
Results |
|
CMNBAT90 Modifications in ChangeMan ZMF 5.6
|
CMNBAT90 Modifications in ChangeMan ZMF 5.6
|
|
|
|
How to add CMNBAT90 for new Compressed Listing Lib Types.
|
How to add CMNBAT90 for new Compressed Listing Lib Types.
|
|
|
|
Missing ILOD (SRC-LOD relationship) records caused by inconsistent BLKSIZE on &&BAT90CTL
|
In ZMF 8.1+ all references to the temporary CMNBAT90 control file (&&BAT 90 CTL) were changed to consistently specify BLKSIZE=0. However, some customers have retained customisations in those skels, or are using other skels based on the old format, which result in a mixture of BLKSIZE=0 and BLKSIZE=3200 being specified for the same &&BAT90CTL file within the same staging jobs.
|
|
|
|
COBOL Compile failure after the precompile step of a DB2 program causes CMNBATCH to issue an RC=12.
|
When the COBOL compile step for a DB2 program fails, CMNBAT90 has already run to create records to tie the DBRM relationship back to the source. When the COBOL compile step subsequently fails, the DBRM member does not get copied to the staging dataset, due to the bad condition code, as that step runs after the compile step. When The CMNBATCH / FAILURE step subsequently runs, RC=12 is issued due to the missing DBRM in the staging library and issues the following message:
|
|
|
|
S0C4 abend in module IEWBFDAT under z/OS 1.5, z/OS 1.6 or z/OS 1.7
|
Customers may experience an S0C4 abend in module IEWBFDAT or CMNBINDF, during audit, DB2TM, Impact Analysis, or CMNBAT90 . When ZMF program CMNBINDF runs to read program objects, it may choose to use the "fast data binder access method" which in turn calls IBM module IEWBFDAT. If the customer is running z/OS 1.5, z/OS 1.6 or z/OS 1.7, this may result in an S0C4 abend in IEWBFDAT or in CMNBINDF.
|
|
|
|
Various abends in ZMF client programs that call IBM's Binder using the Fast Data Interface
|
There are several ZMF functions that call IBM's Binder (Audit, Impact Analysis, DB2TM, and CMNBAT90 ). Any, or all of these programs may exhibit problems when accessing program objects (PDSE).
|
|
|
|
How does Audit determine a source to load relationship?
|
- the SSI in the ISAL (Source and Load) record If the SSI values from the above do not match a SYNCH9 will be flagged in audit. The SSI is generated by CMNSSIDN and then passed to the LINK step to generate the IDENTIFY record. CMNBAT90 /CMNBATCH is used to create the records in the package master.
|
|
|
|
PROMOTION RESPONSE TIME DEGRADATION
|
NOTE: Packages built prior to implementing this change may produce different results than the prior version if CMNBAT90 was not used to build the component relationships (ILOD records). In this case, CMNBAT90 must be used.
|
|
|
|
Example for using the new CMN$$CND skel, to alter condition code processing in compile processes.
|
Looking at the CMN$$LNK skeleton, the following in yellow is found between the beginning of the link job step and the job step that runs program CMNBAT90 : //LINK&L#N
|
|
|
|
Sample skel customization to support SSI in load components when the compiler generates a name card in the object deck.
|
* // DD DISP=(OLD,PASS),DSN=&&&&LCT * )ENDSEL &CUSTLNK1 NE NONAME //BT 90 &TLODLTP EXEC PGM= CMNBAT90 , *** RECORD &TLODLTP NAME(S)
|
|
|
