| |
Results |
|
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.
|
|
|
|
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.
|
|
|
|
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)
|
|
|
|
APS - Multiple Mapsets
|
/* //BT 90 CPY EXEC PGM= CMNBAT90 , *** RECORD CPY NAME(S) CREATED // COND=(4,LT)
|
|
|
