Find Answers

Filter Search Results

Ask a Question

Example: "Database could not be verified"

Results

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.

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.

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

Knowledgebase

Find Answers

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance