This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
Control-M for z/OS
Control-M for z/OS
All versions of the following products: Control-M for z/OS Control-M/Restart Control-D Control-V Control-M/Tape Control-M/Analyzer Control-O Control-M/JCL Verify
When applying INCONTROL maintenance , many GIM24001E, GIM24002E, GIM23901E and GIM30223E errors in the APPLY job. Message ASMA044E & ASMA068S also are generated.
In the sysout of the job you also may see many ASMA044E & ASMA068S error messages such as:
** ASMA044E Undefined symbol - SECPROD
** ASMA068S Length error - SECPROD
The messages may appear for many source elements.
Problem with level of HLASM. Refer to IBM
bmc development managed to reproduced this failure using the a copy of HLASM at IBM PTF level UI53046.
They noticed that the Assembler listing at this PTF level reports:
0HIGH LEVEL ASSEMBLER, 5696-234, RELEASE 6.0, PTF UI51638
This is due to that fact that "PTF UI53046 on MVS failed to update the PTF number in the HLASM listing heading, so it still shows the previous level PTF UI51638" as described in the error description for APAR PI93326.
To resolve this problem you will need to contact IBM. Send then the sysout of the APPLY job faling with the above information and ask them which IBM APARs need to be applied to resolve this problem. In previous instances IBM have recommended APAR UI54379 bit it is best to refer the problem to IBM to see what they recommend.
The problem can also be identified as follows:
1) Failing assembly (maybe - though not exclusively - with ASMA044E or ASMA140W or ASMA110S)
2) The High Level Assembler is at PTF UI51638 or UI53046 (or, according to the APAR description, UI53045 or UI53047). The PTF level is indicated on the first page of each source assembly listing e.g.
1 High Level Assembler Option Summary (PTF UI51638) Page 1
3) On examination of the assembly listing, the primary input (i.e. the assembler source member being assembled) appears to be truncated following a COPY statement.
Item 3. above will be pretty difficult to identify but items 1 and 2 exist, then there is a very high chance that this may be the reason for the problem.