| |
Results |
|
Exit CMNEX035 has syntax error in X35@SCAN & X35@SCRN table entries.
|
DC CL3'@*' library type that start with @ The comments indicate this is intended to be a prefix/mask (starts with) entry but they are missing the '*' wildcard marker. Note: There is also a typing mistake in the exit where ' scan ' is spelled 'sacn'
|
|
|
|
New Features in ChangeMan ZMF 8.2
|
... during mass baseline scanning . Mass Baseline Scanning ... macro detection will take place . ... your impact analysis database with macro information ... ... a Db2 table . ... , create a table , and load ... output into the table in one job ... ... above steps have occurred , the following ... ... access, an error message is issued ... ... on the ATTRIB Table ... on the ATTRIB table to a value ... ... The CMNMODTB single table has been replaced by a table for each library ... ... CMNMODTB into separate tables is similar to ... ... which creates a table for each library ... tables exist for only ... The tables are controlled
|
|
|
|
Minor error in CMNEX027 table format description
|
In changes made in CMN ZMF 5.5 we removed the ability to control the panel input from the exit. In removing this field from the CMNEX027 table the subsequent table entries in the description were not re-numbered. That is, entry number 3 was removed and the description now reads 1, 2, 4, 5 and 6. This can cause some confusion and requires tidying up.
|
|
|
|
CMNEX034 causing CMNDB2TM to incorrectly report IA table out of date
|
BASELINE RIPPLE DB2 TABLE MAINTENANCE. BASELINE INFORMATION IN DB2 TABLE NOT CURRENT, UNABLE TO FIND BUN FOR APPL/LIBTYPE: SNEA/JCL YOU NOW NEED TO RUN CMNAS000 TO SYNCHRONIZE YOUR I/A DATABASE WITH YOUR BASELINE.
|
|
|
|
CMNDB2TM incorrectly reporting IA table out of date
|
BASELINE INFORMATION IN DB2 TABLE NOT CURRENT, UNABLE TO FIND BUN FOR APPL/LIBTYPE: AUDI/JCT YOU NOW NEED TO RUN CMNAS000 TO SYNCHRONIZE YOUR I/A DATABASE WITH YOUR BASELINE. BUN table used in this execution follows:
|
|
|
|
'CMNALLIO unable to read/write logfile' during admin update
|
Anyway, the LOG request does fail which causes CMNADMIN to take an error exit hence, the table data mentioned above is not preserved.
|
|
|
|
Correct grammar errors in CMNEX035
|
The following grammatical errors were found in CMNEX035. ... 000337 * Library Type table for checkout: ... 000426 * to be eliminate from the selection list for scan .
|
|
|
|
CMNBSCAN not finding all occurrences of scan data.
|
... Criteria for this Scan : Scan Data 1 : ... ... Dataset Name to Scan :LLEERSS. ... ... SHIP_ORDER TABLE 000043 ... * 14 members scanned *** ... with trailing blank incorrectly produces: ... Criteria for this Scan : Scan Data 1 : ... ... Dataset Name to Scan :LLEERSS. ... //* ADD TO THE SHIP_ORDER TABLE 000043 *** 14 members scanned *** ... C. Note the following lines match the scan criteria specified in step B above (trailing blank) but, do not show up in scan results: ... Scan performed in ZMF 5.5 produces same incorrect results.
|
|
|
|
Intermittent S0C4 in CMNIMPFL, offset=8FA during audit.
|
SYSTEM COMPLETION CODE=0C4 REASON CODE=00000011 ... PSW AT TIME OF ERROR 078C0000 800A1AA2 ILC 6 INTC 11 ... They can also go days running audit without the abend occurring . There were other cases in the CLARIFY data base where other customers reported the S0C4 in CMNIMPFL at the same offset. ... CMN2621A - Neither DB2 nor the IA Table are available, Terminating.
|
|
|
|
FAQ - DB2 Option Changes in ZMF 8.1.1
|
... to create these tables will result in DB2 errors during attempts to ... ... (where the tables created by DB ... ... I create the tables and bind the ... ... .1 ZMF system . ... can create the tables and bind the ... Read on please. ... to create the tables and bind the ... ... DB2 admin tables (created and ... ... PACKAGESET SPECIAL REGISTER WHILE TRYING TO FORM ... ... the DB2 tables introduced in ZMF ... . the 3 tables created by DB ... ... 2 hosting the tables defined by DB ... ... defined the following tables on DBT3 ... ... to host the tables created by DB ...
|
|
|
