Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML Audit and LCT components
Audit and LCT components
CMS-XML Can the SSI information be plugged into easytrieve modules? Currently information is not and is causing SYNCH9 errors at audit time.
Moreover, if the customer wants to include the SETSSI control statement as input to the binder through SYSLIN DD, the value specified in the SETSSI control card will override the value set by the SSI= option. This way, the customer can build their own LCT or have CMNSSIDN create one with the SSI= option in PARM intact.
MS-WORD ChangeMan ZMF Hilo Documentation Content and Notes
This feature is really no different than using a link control (LCT) member during a link, and specifying a member name in the NAME control card that is different from the source component member name. This is because these alternate load module member names are actually fed into the CMNSSIDN program to generate a NAME LCT control card that has the alternate member name.
CMS-XML Sample skel customization to support SSI in load components when the compiler generates a name card in the object deck.
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 Replace a sub-routine using RELINK
There are several possibilities to solve this problem: 1. Ensure that all 'composite' load modules have linkcards ( LCT ). 2. Modify skel CMN$$SSI to contain the following logic:
CMS-XML COBOL V5.1 in ChangeMan ZMF
If customers want to implement COBOL V5.1 prior to ZMF 8.1, they will need to create their own custom procedure and skels. Please note the following CR is a prereq for using COBOL V5.1. DEF170282 - CMNSSIDN IDENTIFY missing from modules assembled with GOFF parm
CMS-XML 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.
CMS-XML DB2 Stored Procedures and DSNALI vs. DSNRLI
1. Utilize link edit control cards ( LCT ) to specify which module to include. For example, a stored procedure named DWPSP01P runs in WLM. Create an LCT member named DWPSP01P with the following contents. INCLUDE SYSLIB(DSNRLI)
CMS-XML Autoresolve of load-to-load and object-to-load audit errors
3. If CMNEX022 is inactive or if no corresponding entry for the target composite library type is found in the exit, then autoresolve will attempt to submit a relink of the composite load with REPLACE cards for the affected subroutines. This is achieved through use of the CMNSSIDN RMB parameter (please refer to the CMN ZMF Customization Guide for additional information).
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs