| |
Results |
|
LIST command does not list contents of entire length of module
|
LIST command is not listing contents of entire length of PDSE module (type= library ) The LIST command is only listing through x'047C'. ** MAP BIT64ATS
|
|
|
|
Contents of CPXLOAD library do not match what's listed in Install Guide
|
In reviewing the contents of 'somnode.COMPAREX.CPXLOAD', it appears that the following modules are missing: SERUPDTE CPXVB2FB
|
|
|
|
How to add CMNBAT90 for new Compressed Listing Lib Types.
|
Customer is getting SYNCH12 - orphan modules in the staging libraries and it is showing up in a couple of areas, like- load libraries and compressed list libraries . Customer added a new Compressed Listing Lib type (LSO).
|
|
|
|
DIMCM12.1: z/OS: Link List Libraries
|
There is an intermittent problem with conflicts between the link list libraries and a tasklib (STEPLIB) in the sBem. This manifests itself as the sBem loading the wrong module in the attached sub-task. For example, if is in the link list and is on the TASKLIB for the compile step, then the wrong version of IGYCRCTL gets loaded, and then the COBOL compiler fails (because a subsequent sub-module of the COBOL compiler is not in synch with the main line).
|
|
|
|
WD4ZMF: Not all package libraries listed
|
When WD4ZMF lists package library types it only displays those to which components have been explicitly staged. It does not list all associated libraries (e.g. LOD, LST, etc.). This is inconsistent with the behaviour of, for example, ZDD and also poses some usability issues (e.g. the user needs to access the ISPF client to see what load modules have been generated, what DBRMs need binding, etc.)?
|
|
|
|
STR: Building a ML for a PDSE load library.
|
In comparison tests between PDS data sets and load PDSE data sets, we found that the binder dialogs took about three times the system resources for StarTool subcommands like MAP, HISTORY, LIST , XREF, ...
|
|
|
|
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.
|
|
|
|
SSM V832 Getting S0C4 Abend in module HPSDSFTP at OFFSET=1B8C during Fingerprint processing.
|
Our production library fingerprinting abended with an S0C4 Abend. SYSTEM COMPLETION CODE=0C4 REASON CODE=00000011. This problem seems to be related to the data/time format for enterprise PL1 load modules.
|
|
|
|
SSM832 Getting S0C7 Abend during Fingerprint processing in module HPSDSFTP at OFFSET=1C36
|
This problem started after our programmers deployed a large number of PL/1 enterprise compiled load modules. SSM works fine on other libraries . It is only abending on this particular set of libraries.
|
|
|
|
STR: Load library LRECL display.
|
STR: Load library LRECL display.
|
|
|
