Find Answers

Filter Search Results
All Operating Systems:
All Others (1)
All Products:
ChangeMan ZMF (26)
All Solution Types:
Installation & Customization (1)
Product Tips & Advice (1)
Source:
Defects (25)
Solutions (1)
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
  Results
CMS-XML ERO CMNSSOBJ is not creating correct link-edit IDENTIFY statement for PL/I
ERO CMNSSOBJ is not creating correct link-edit IDENTIFY statement for PL/I
CMS-XML CMNSSIDN and CMNSSOBJ should ignore blank csect names when choosing the name to be used for the identify statement.
CMNSSIDN and CMNSSOBJ should ignore blank csect names when choosing the name to be used for the identify statement.
Similar Answers
CMS-XML Why can I not see the IDRDATA/fingerprint/eyeball information in my executable component?
The most obvious reason is that no IDENTIFY statement has been supplied to the binder/linkage editor (IEWL). If the CMNSSIDN/ CMNSSOBJ step is being included in the build procedure and the executable is a program object (i.e. it is being written to a PDSE rather than a PDS executable library) then there is another possibility.
CMS-XML CMNSSIDN IDENTIFY statement is missing from modules generated with the GOFF parameter
A component that is compiled or assembled with the GOFF parameter will generate an object file in Generalized Object File Format (GOFF). Program CMNSSIDN and CMNSSOBJ do not understand GOFF format. This results in the absence of the IDENTIFY link parameter in the LCT member fabricated or modified by CMNSSIDN.
Similar Answers
CMS-XML Missing SYNCH20! for OBJ-LOD relationship
- the baseline object has NEVER been run through a ZMF package lifecycle. Therefore it does not contain any fingerprint/idrdata/ CMNSSOBJ information.
Similar Answers

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs