The following messages are generated by the Package shipment utility in the course of processing. Possible causes and recommended corrective actions are described along with each message.
Reason:
Informational message. This message is written to the message log when Package shipment processing is about to terminate. It records the final return code for this run.
Action:
None.
Reason:
Informational message. This message is written to the message log when the input is free of syntax errors and the destinations and Packages exist. Both conditions must be met in order to receive this message.
Action:
None.
Reason:
The verification process detected errors in the utility input that do not affect the shipment of the requested Packages.
Action:
Examine the Validation Report for warning messages ("W" as the last character in the message number). Take the corrective action associated with any message.
Reason:
The verification process detected errors in the utility input that will cause processing to terminate.
Action:
Examine the Validation Report for error messages ("E" or "S" as the last character in the message number). Take the corrective action associated with the message.
Reason:
Informational message. This message is written to the message log when the utility has determined the content of the Packages.
Action:
None.
Reason:
The Package staging process detected errors that do not affect the shipment of the requested Packages.
Action:
Examine the Message Log for warning messages ("W" as the last character in the message number) that precede this message. Take the corrective action associated with the warning message.
Reason:
The Package staging process detected errors in the utility input that caused processing to terminate.
Action:
Examine the Message Log for error messages ("E" or "S" as the last character in the message number) that precede this message. Take the corrective action associated with the error message.
Reason:
Informational message. This message is written to the message log when the Package Shipment Utility determines the following:
At this point, the host staging data sets and various control statement data sets are built.
Action:
None.
Reason:
This message is written to the message log when the utility determines that:
However, an error condition was detected that does not affect the transmission of the requested Packages. At this point, the host staging data sets and various control statement data sets are built.
Action:
Examine the Message Log for warning messages ("W" as the last character in the message number) that precede this message. Take the action associated with the warning message. Examine the Activity Report for detail lines flagged with a warning message.
Reason:
The staging process for this shipment was terminated due to errors.
Action:
Examine the Message Log for error messages ("E" or "S" as the last character in the message number) that precede this message. Take the corrective action associated with the error message. Examine the Activity Report for detail lines flagged with an error message.
Reason:
The execution parm passed to the staging utility or the confirmation utility was found to be in error. This message is preceded by a message stating the cause of the error.
Action:
Take the corrective action for the message that precedes this one.
Reason:
The program named in the message has abended with either a System abend (abend code = Snnn) or a user abend (abend code = Unnnn).
Action:
For information about user abends, see the corresponding sections in this guide. For information about "S0Cx" System abends, obtain a dump and contact your administrator. Other System abends typically represent set-up problems or internal errors; if resolution of the problem is not obvious, obtain a dump and contact your administrator.
Reason:
A SHIP action did not contain the Package name.
Action:
Specify the Package name on the SHIP statement.
Reason:
A SHIP request did not contain a DESTINATION, and a SET DESTINATION was not in effect for that request.
Action:
Specify a destination on the SHIP request, or code a SET statement prior to the SHIP statement, specifying a destination.
Reason:
The specified Package name is not on file.
Action:
Correct the Package name specified in the SHIP request.
Reason:
The specified destination is not on file.
Action:
Make sure that the correct Package file is being accessed. Correct the destination or add a new one using the Destination Definition panel.
Reason:
When the requested Package was cast, the ENABLE BACKOUT indicator was set to "NO."
Action:
Packages can be shipped only when backout records exist. This Package cannot be shipped because backout records are not created when ENABLE BACKOUT = NO.
Reason:
The requested Package was not executed.
Action:
An unexecuted Package cannot be shipped. Either execute the Package or delay shipment until after its execution.
Reason:
A COMMIT was issued for this Package after its execution.
Action:
Packages can be shipped only when backout records exist. This Package cannot be shipped because backout records are deleted when a Package is committed.
Reason:
A Package is being shipped twice in the same run.
Action:
None. The second request is ignored.
Reason:
Two SHIP actions for the same Package were detected for the same destination. One of the actions specified OPTION OUTPUTS and the other action specified OPTION BACKOUT.
Action:
Choose one of the actions and delete the other.
Reason:
The Package header record has indicators turned on, but there are no Package backout records. If the indicators are on, Package backout records should be available.
Action:
This can indicate Package file integrity problems or an internal error. Contact your administrator.
Reason:
An error other than "Package not found" was returned by the Package file query routine.
Action:
Make sure that the Package file still exists and is catalogued. Also, make sure that the Package file DSN is correctly coded in the C1DEFLTS table being used.
Reason:
An error other than "Package not found" was returned by the Package file query routine.
Action:
Make sure that the Package file still exists and is catalogued. Also, verify that the Package file DSN is correctly coded in the C1DEFLTS table being used.
Reason:
An "out of storage" condition or an internal error has occurred.
Action:
If the reason code is "NOSTG", increase the amount of storage available to the region or decrease the number of Packages being shipped. If RC=0; then it possibly shipped in a prior Package. For other reason codes, contact your administrator.
Reason:
When the Package was executed, the return code was greater than 8.
Action:
A Package cannot be shipped if it does not execute successfully.
Reason:
The link between a Package backout record and its ID record cannot be established.
Action:
This message can indicate a Package file integrity problem or an internal error. Contact your administrator.
Reason:
The Package Shipment Utility's input data set (C1BMXIN) could not be opened.
Action:
Check for a missing C1BMXIN DD card.
Reason:
A single SHIP was coded with both OPTION OUTPUTS and OPTION BACKOUT.
Action:
Choose one option and delete the other.
Reason:
There were no SHIP statements found in the input file.
Action:
Check for misspelled action code. Make sure that the input file contains at least one SHIP request.
Reason:
Summarizes the results of a batch run.
Action:
If there are actions with errors, correct the errors, otherwise no action is required.
Reason:
The Package File I/O routine passed back an unexpected return code for one of the following requests: Extract ID, Extract Backout, Query Element Stub. The Package name and return/reason codes are displayed. For Query Element Stub, message C1BMX90I is also displayed.
Action:
Contact your administrator.
Reason:
The link between a Package backout record and its ID record cannot be established.
Action:
This message can indicate a Package file integrity problem or an internal error. Contact your administrator.
Reason:
The Package header record has indicators turned on, but there are no ID records. If the indicators are on, ID records should be available.
Action:
This message can indicate Package file integrity problems or an internal error. Contact your administrator.
Reason:
The Package header record has indicators turned on, but there are no backout records. If the indicators are on, backout records should be available.
Action:
This message can indicate Package file integrity problems or an internal error. Contact your administrator.
Reason:
An unexpected return code was passed back by the Master Control File I/O routine during a read operation for an Element master record. This message is followed by message C1BMX91I.
Action:
This message can indicate Package file integrity problems or an internal error. Contact your administrator.
Reason:
A related Package is needed to process the shipment of the Package named in the preceding C1BMX91I message. When examining the related Package, a condition was found that prevents shipment of the Package named in C1BMX91I. The possible error conditions are as follows:
A related Package is a Package that supersedes, or is superseded by, the Package being requested. A superseding Package is a Package whose execution affects the members in one or more other Packages. Therefore, Packages are considered related when at least one member that participates in the requested Package also participates in another Package.
Action:
The error condition "IS PREVENTING SHIPMENT" is an "undefined" error and should be brought to the attention of your administrator.
The error condition "IS NOT ON FILE" may be due to the use of the Package Delete Utility.
All error conditions will prevent the shipment of the Package.
Reason:
The DSN listed in the preceding message (C1BMX91I) is not cataloged.
Action:
Restore the data set.
Reason:
The DSN listed in the preceding message (C1BMX91I) could not be dynamically allocated. The message contains the SVC99 return code and reason code. If the allocation error was a "data set not found" condition (code 1708), message C1BMX36E displays.
Action:
For SVC99 return codes, see the appropriate IBM documentation.
Reason:
A dynamic allocation request failed for the named data set. The SVC 99 return code is rc2, the error code field contains S99ERROR, and the information code contains S99INFO.
Action:
For SVC99 return codes, see the appropriate IBM documentation.
Reason:
While attempting to copy members to a staging data set, the copy utility either abended or encountered an abnormal situation.
Action:
To determine whether you have received a return code or an abend code, note the following, and keep in mind that the return code is six hex characters:
Reason:
CA Endevor SCM encountered an error writing to the named data set.
Action:
Check the JES log for a message related to the I/O error.
Reason:
The C1BMXRCN data set is missing. This is the remote confirmation JCL data set. It is distributed under the name C1BMXRCN as an ISPF skeleton and should be in the ISPSLIB data set.
Action:
If remote confirmation is not desired, this message can be suppressed by creating a C1BMXRCN skeleton containing a "//*".
Reason:
Informational message. This message indicates that the user "before" exit for Package shipment cancelled this transaction.
Action:
None.
Reason:
The staging utility has encountered an I/O error reading the remote confirmation JCL data set (DDNAME=C1BMXRCN).
Action:
Check the JES log for a message related to the I/O error.
Reason:
The destination named in the message has no associated job cards.
Action:
Provide job cards for the destination through the Destination Definition panel.
Reason:
A data set name mapping rule was applied to a host CA Endevor SCM output data set and the resultant remote data set name was found to be invalid.
Action:
Examine the data set name for errors. Application of the rule may have caused the generation of a data set name containing more than 44 characters or a qualifier containing more than 9 characters. Correct the data set mapping rule or add a more specific rule to handle this particular name.
Reason:
A data set name mapping rule was found to exclude the named data set from shipment to named destination.
Action:
See the Packages Guide.
Reason:
An error was detected in defining a symbolic variable in a model control statement. The result is a return code from the symbol resolution routine. This is an internal error.
Action:
Call your CA Endevor SCM Administrator.
Reason:
Truncation occurred during Package ship model control statement symbol substitution.
Action:
Reformat the member (contained in the library associated with the DDNAME in the message) so that symbol substitution does not result in data truncation.
Reason:
The JCL used to build the remote IEBCOPY and IDCAMS job steps could not be found. The named member will be C1BMXCOP (COPY) or C1BMXDEL (IDCAMS DELETE). These members were provided as ISPSLIB skeletal members under those names.
Action:
Make sure that the named data set contains the members. See the Packages Guide.
Reason:
An error was detected while performing a FIND or READ action on the named model transmission control card data set and member. The return code is in hex.
Action:
Consult the JES log for messages associated with the error.
Reason:
The record of shipment has been marked "confirmed".
Action:
None.
Reason:
The confirmation utility was passed date and time that do not correspond to any shipment date/time recorded for any destination.
Action:
Someone may have deleted the Packages associated with this shipment before the confirmation could be executed. Check the date and time specification and resubmit the request.
Reason:
The confirmation utility was passed a date and time that do not correspond to any shipment staging date/time for the named destination.
Action:
Someone may have deleted the Packages associated with this shipment before the confirmation could be executed. Check the date and time specification and resubmit the request.
Reason:
An error was encountered in trying to extract the confirmed record of shipment. The text of this message will contain a "PKMRnnnn" message ID and text describing the cause of the error.
Action:
Take the corrective action dictated by the "PKMRnnnn" message.
Reason:
An error was encountered in trying to replace the confirmed record of shipment. The text of this message will contain a "PKMRnnnn" message ID and text describing the cause of the error.
Action:
Take the corrective action dictated by the "PKMRnnnn" message.
Reason:
When processing the named model member, the statement displayed as an 80 character card image was in error.
Action:
This message will be followed by message C1BMX66I for symbolic substitution errors or C1BMX67E for all other errors. Refer to information contained in these messages.
Reason:
The card image shown in the preceding C1BMX65I message is redisplayed after symbolics have been substituted. Truncation has probably occurred.
Action:
If truncation has occurred, rearrange the model statement or break it up into two statements.
Reason:
A command error or sequence error has occurred in the model statement displayed in the preceding C1BMX65I message. The level number shows the depth of nested @INCLUDE statements. If the level number is *SYSTEM*, no @INCLUDE statements are in effect. The "EXPECTING" clause tells what was expected and the "BUT FOUND" clause tells what was found instead.
Action:
Correct the statement in error.
Reason:
The confirmation utility could not mark the record of shipment "confirmed". This message is preceded by a message stating the cause of the error.
Action:
Take the corrective action for the message that precedes this one.
Reason:
For MODEL PARM the text is a legend describing the format of the parm. For ACTUAL PARM the text is an image of the actual parm received by the staging utility (C1BMX000).
Action:
None.
Reason:
The required portion of the staging or confirmation parm includes the character string "C1BMX000", the date, the time, and the function.
Action:
Correct the parm.
Reason:
The parm passed to the staging utility or the confirmation utility did not contain all the required parameters.
Action:
Correct the parm.
Reason:
The parm passed to the staging utility or the confirmation utility consists of several parameters separated by commas. A comma was found to be missing after one of the following fields: "C1BMX000", DATE, TIME, FUNCTION, OPERATION, CONDITION, CODE_VALUE, or DEST_ID.
Action:
Correct the parm.
Reason:
The parm passed to the confirmation utility did not contain all the required fields. One of the following was missing: FUNCTION, USER ID, OPERATION, CONDITION, CODE_VALUE, or DEST_ID.
Action:
Correct the parm.
Reason:
The parm passed to the staging utility or the confirmation utility contained superfluous data.
Action:
Correct the parm.
Reason:
The parm passed to the staging utility or the confirmation utility contains an invalid shipment date (second parameter in the parm).
Action:
Correct the date. If the message indicates that $CURR_DT is invalid; then the C1BMXDTM DD statement is missing in one or more of the following ISPF skeletons: C1BMXJOB, C1BMXHCN, C1BMXRCN. The format of the C1BMXDTM DD statement. can be found in the skeleton examples found in the Packages Guide.
Reason:
The parm passed to the staging utility or the confirmation utility contains an invalid shipment time (third parameter in the parm).
Action:
Correct the time. If the message indicates that $CURR_TM is invalid; then the C1BMXDTM DD statement is missing in one or more of the following ISPF skeletons: C1BMXJOB, C1BMXHCN, C1BMXRCN. The format of the C1BMXDTM DD statement. can be found in the skeleton examples found in the Packages Guide.
Reason:
The parm passed to the staging utility or the confirmation utility contains an invalid function. Valid values are SHIP (to execute the shipment staging utility) or CONF (to execute the shipment confirmation utility).
Action:
Correct the function CODE.
Reason:
The first variable data field (see preceding message C1BMX70I) passed as a parm to the confirmation utility was incorrect. This is the operation field. Possible values are shown in the message.
Action:
Correct the operation field.
Reason:
The second variable data field (see preceding message C1BMX70I) passed as a parm to the confirmation utility was incorrect. This is the condition field. Possible values are shown in the message.
Action:
Correct the condition field.
Reason:
The third variable data field (see preceding message C1BMX70I) passed as a parm to the confirmation utility was incorrect. This is the return code field. Possible values are shown in the message.
Action:
Correct the return code.
Reason:
The third variable data field (see preceding message C1BMX70I) passed as a parm to the confirmation utility will be ignored when the condition (2nd variable data field) is "AB" or "EX".
Action:
Code "****" to eliminate this warning.
Reason:
Informational message. This multi-line message may follow messages C1BMX30E and C1BMX34E.
Action:
Take the corrective action of the preceding message.
Reason:
Informational message. This message precedes messages C1BMX35E, C1BMX36E, and C1BMX37E.
Action:
Take the corrective action of the message that follows.
Reason:
Warning message. This message indicates that a member of a Package being shipped has been superseded by another Package.
Action:
Verify the status of this member.
Reason:
Informational message. This message is preceded by message C1BMX91I and followed by message C1BMX35E. The message specifies the last related Package that was successfully processed before an error condition was detected (as reported in message C1BMX35E).
Action:
Take the corrective action for message C1BMX35E.
Reason:
A Package related to the one named in the preceding C1BMX91I message contains data which indicates that it may have been re-used, deleted and re-added, or otherwise changed. The Package named in the preceding C1BMX91I message may be unshippable or uncollectible.
Action:
None.
Reason:
Ship fails. Element cannot be shipped. It is currently in use by another user.
Action:
Retry later.
Reason:
This informational message indicates whether or not one of the standard group symbolics was created.
Action:
None.
Reason:
Informational message.
Action:
None.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|