This section details messages generated in the course of Batch Environment Administration Facility processing, along with possible causes and corrective actions to take in error situations.
Reason:
This message appears in the Action Execution report to identify the current action number that is being processed. The statement number refers to the corresponding action in the Control Statement Summary report. The SCL Object number is for the number of the object associated with the SCL statement. This number is always 1 if the object is not wildcarded. If the statement contains a wildcarded object name that generates multiple SCL statements, the statement number remains the same and the object number increments for each SCL statement generated.
Action:
None.
This message appears in the Control Statement Summary report to identify the number of the control statement that is being processed. The control statement numbers are assigned sequentially beginning at one.
Action:
None.
Reason:
The execution JCL contained the PARM=VALIDATE statement. The program only validates the syntax of the control statements. The control statements are not executed.
Action:
None. However, to execute the actions, remove the PARM=VALIDATE statement from the JCL.
Reason:
You are not authorized to perform the Batch Environment Administration Facility action identified.
Action:
Contact your administrator to obtain the necessary authorization to execute the Batch Environment Administration Facility action.
Reason:
The execution JCL did not contain the ENESCLIN DD statement. The ENESCLIN DD statement contains the Batch Environment Administration Facility control statements (SCL).
Action:
Add a valid ENESCLIN DD statement to the execution JCL and resubmit the JCL.
Reason:
The data set associated with the ENESCLIN DD statement does not have the correct attributes. The data set must be either a sequential data set, a partitioned data set with an explicit member, or an instream data set. In addition, the data set LRECL must be 80 if the record format is fixed, or at least 84 if the record format is variable.
Action:
Verify that the data set that the ENESCLIN DD statement refers to has the appropriate attributes. If not, use a data set that has the correct data set attributes and resubmit the JCL.
Reason:
The execution JCL contained an unidentified parameter on the PARM statement. The program issues message ENBE008E and terminates with a return code of 12.
Action:
Correct the invalid execution parameter in the JCL and resubmit the JCL.
Reason:
This message is issued immediately after message ENBE007E. It identifies the invalid parameter that was passed to the program.
Action:
Correct the invalid execution parameter in the JCL, and resubmit the JCL.
Reason:
The Batch Environment Administration Facility initialization routine encountered one or more errors. One or more error messages should precede message ENBE009E. The Batch Environment Administration Facility terminates with a return code of 12.
Action:
See the previous message to determine why the initialization failed and take the corrective action that the error message indicates.
Reason:
The Quorum Size associated with the Approver Group is larger than the number of Approver User IDs associated with the Approver Group. This can occur under two circumstances. First, a DEFINE APPROVER GROUP action is adding User IDs to the Approver Group and the QUORUM SIZE value is greater than the number of Approver User IDs specified on the APPROVER clause. Second, the DELETE APPROVER action is removing one or more Approver User IDs from the Approver Group, and the number of Approver User IDs that would remain is less than the existing QUORUM SIZE value.
Action:
Either reduce the QUORUM SIZE value, add more Approver User IDs to the DEFINE APPROVER GROUP action APPROVER clause, or remove one or more Approver User IDs from the DELETE APPROVER GROUP action APPROVER clause.
Reason:
The COMPARE FROM or TO COLUMN value is greater than the SOURCE ELEMENT LENGTH. The source Element length can be obtained from either the existing Type definition or from the SOURCE ELEMENT LENGTH clause.
Action:
Change the COMPARE FROM or the COMPARE TO value so that it is equal to or less than the SOURCE ELEMENT LENGTH that is associated with the Type definition.
Reason:
The symbol name identified is not defined in the processor identified in the message. The DEFINE PROCESSOR SYMBOL action can only modify symbols that are defined in the processor.
Action:
Remove the symbol name identified from the SYMBOL clause of the DEFINE PROCESSOR SYMBOL action. Also, verify that the correct PROCESSOR GROUP and PROCESSOR TYPE was specified on the DEFINE PROCESSOR SYMBOL action request. Resubmit the request.
Reason:
The MOVE, GENERATE, or DELETE processor that was specified on the DEFINE PROCESSOR GROUP action was not found in the Stage 1 or Stage 2 processor load library for the System identified in the message.
Action:
Verify that the DEFINE PROCESSOR GROUP action specifies the correct processor name.
Reason:
The MOVE, GENERATE, or DELETE processor that was specified on the DEFINE PROCESSOR SYMBOL action was not found in the Stage 1 or Stage 2 processor load library for the System identified in the message.
Action:
Verify that the DEFINE PROCESSOR SYMBOL action specifies the correct processor name or type (or both).
Reason:
The specified processor load library could not be allocated. The Dynamic Allocation (SVC 99) service error code and information codes are shown.
Action:
Refer to the appropriate IBM documentation for your operating System for an explanation of the S99INFO and S99ERROR codes. Take any corrective action possible and resubmit the request. If the problem persists, contact your administrator.
Reason:
The STAGE ONE LOAD or LIST LIBRARY and the corresponding STAGE TWO LOAD or LIST LIBRARY refer to the same data set. The DEFINE SYSTEM action continues processing.
Action:
None. If the STAGE ONE LOAD or LIST LIBRARY should be different than the corresponding STAGE TWO LIBRARY, use the DEFINE SYSTEM action to make the appropriate change.
Reason:
The Processor LOAD or LIST library specified in the message was not found in the System catalog.
Action:
Verify that the correct data set was specified on the DEFINE SYSTEM action. If necessary, allocate the data set specified on the request. Resubmit the request.
Reason:
The Processor LOAD or LIST library that was specified on the DEFINE SYSTEM action has incorrect data set attributes. For information on the correct attributes for the processor, see the Administration Guide. LOAD and LIST libraries.
Action:
Verify that the correct data set was specified on the DEFINE SYSTEM action. Verify the data set attributes of the data set specified and, if necessary, reallocate the data set with the correct attributes. Resubmit the request.
Reason:
The BASE, DELTA, SOURCE OUTPUT, or INCLUDE LIBRARY name contains an invalid &C1. symbol.
Action:
Make sure that the &C1. symbol is spelled correctly. For a list of valid &C1. symbols, see the Administration Guide.
Reason:
The BASE, DELTA, SOURCE OUTPUT, or INCLUDE LIBRARY identified was not found in the System catalog.
Action:
Verify that the data set name specified is correct. If the data set name is correct, allocate the data set. Resubmit the request.
Reason:
The COMPARE FROM and TO column values fall outside the standard column range for the language identified. The DEFINE TYPE continues processing the request.
Action:
If the COMPARE column range identified in the message is correct, no changes are necessary. For a list of the standard COMPARE column ranges for each standard language, see the SCL Reference Guide.
Reason:
The NUMBER OF ELEMENT LEVELS or the NUMBER OF COMPONENT LEVELS value is greater than the CONSOLIDATE ELEMENT AT LEVEL or the CONSOLIDATE COMPONENT AT LEVEL value.
Action:
Specify a NUMBER OF ELEMENT LEVELS or NUMBER OF COMPONENT LEVELS value that is less than or equal to the CONSOLIDATE ELEMENT AT LEVEL or the CONSOLIDATE COMPONENT AT LEVEL value.
Reason:
The DEFINE action requires the clause that is identified by the clause field.
Action:
Add the required clause to the DEFINE statement. Resubmit the request.
Reason:
The DEFINE SYSTEM action requires a valid STAGE ONE LOAD LIBRARY or STAGE TWO LOAD LIBRARY clause.
Action:
Specify a valid STAGE ONE LOAD LIBRARY or STAGE TWO LOAD LIBRARY clause on the DEFINE SYSTEM request. Resubmit the request.
Reason:
This clause can only be used with LOCAL, NDM and XCOM transmission methods.
Action:
Correct the syntax and resubmit the job.
Reason:
An update to the destination record changed the transmission method from one that supports USS file transmissions to one that does not support USS file transmissions. The update removed the USS HOST PATH NAME PREFIX value from the destination record. The original prefix name is displayed in the message.
Action:
None.
Reason:
An update to the destination record changed the transmission method from one that supports USS file transmissions to one that does not support USS file transmissions. The update removed the USS REMOTE PATH NAME PREFIX value from the destination record. The original prefix name is displayed in the message.
Action:
None.
Reason:
The DD statement specified on the BUILD SCL TO DDNAME clause was not allocated in the execution JCL.
Action:
Add the DDname specified on the TO DDNAME clause to the execution JCL and resubmit the request.
Reason:
The data set specified on the BUILD SCL FOR action TO DSNAME clause could not be located in the System catalog.
Action:
Verify that the data set specified on the BUILD SCL FOR action TO DSNAME clause exists. Either correct the TO DSNAME clause or allocate a new data set. Resubmit the request.
Reason:
The member name specified on the BUILD SCL FOR action TO DSNAME MEMBER clause already exists in the data set specified and the REPLACE clause was not specified.
Action:
Either specify the name of a member that does not exist on the MEMBER clause or specify the REPLACE clause to replace the existing member. Resubmit the request.
Reason:
The data set associated with the BUILD SCL FOR action TO clause does not have the correct attributes for the action. The data set must be either a sequential data set or a partitioned data set with explicit member. In addition, the data set LRECL must be 80 if the record format is fixed, or at least 84 if the record format is variable.
Action:
Either refer to a data set that has the correct attributes for the BUILD SCL FOR action or reallocate the data set identified with the correct attributes.
Reason:
The path name prefix value cannot exceed 732 characters
Action:
Correct the syntax and resubmit the job.
Reason:
The path prefix or path name specification did not have a trailing “/” character and contains the maximum number of characters.
Action:
Correct the syntax and resubmit the job.
Reason:
The path prefix or path name specification must have a beginning “/” in its name.
Action:
Correct the syntax and resubmit the job.
Reason:
The name cannot exceed 768 characters.
Action:
Correct the syntax and resubmit the job.
Reason:
The DELETE action has successfully deleted the Environment Object definition.
Action:
None.
Reason:
The System specified on the DELETE SYSTEM action cannot be deleted because at least one Type is associated with the System.
Action:
Delete all of the Types associated with the System and resubmit the request.
Reason:
The System specified on the DELETE SYSTEM action cannot be deleted because at least one Subsystem is associated with the System.
Action:
Delete all the Subsystems associated with the System and resubmit the request.
Reason:
The Type specified cannot be deleted because an Element is associated with the Type. The message identifies the name and inventory location of the Element associated with the Type.
Action:
Delete all of the Elements associated with the Type and resubmit the request.
Reason:
The Subsystem specified cannot be deleted because an Element is associated with the Subsystem. The message identifies the name and inventory location of the Element associated with the Subsystem.
Action:
Delete all of the Elements associated with the Subsystem and resubmit the request.
Reason:
The Processor Group specified cannot be deleted because an Element is associated with the Processor Group. The message identifies the name and inventory location of the Element associated with the Processor Group.
Action:
Delete all of the Elements associated with the Processor Group and resubmit the request.
Reason:
The Batch Environment Administration Facility has completed execution. The program terminates with the return code specified.
Action:
None.
No matches were found for Type Sequence in Environment env-value, Stage stg-value, System sys-value.
Reason:
The action used name masking to specify the Environment, Stage, System, or any combination thereof. No match was found.
Action:
Verify that the correct Environment, Stage, and System were specified. Resubmit the request.
Reason:
The Batch Environment Administration Facility initialization routine was unable to dynamically load the named program. The initialization routine fails and the program terminates.
Action:
Verify that the execution JCL contains the appropriate data sets in the CONLIB DD statement. Check the JES System log for the job and for any System messages that may indicate a System error. If any System errors are present, take corrective action for those errors. If the problem persists, contact your administrator.
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action detected that the SYSTEM specified on the DEFINE, DELETE, or BUILD SYSTEM action was defined at only one of the two Stages in the Environment.
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action detected that the SUBSYSTEM specified on the DEFINE, DELETE, or BUILD SYSTEM action was defined at only one of the two Stages in the Environment.
Reason:
The ENVIRONMENT specified on the DEFINE, DELETE, or BUILD SCL FOR action is not defined. This occurs if the Environment is not defined in the C1DEFLTS table or if you are not authorized to access an Environment that is defined in the C1DEFLTS table.
Action:
Verify that the Environment is valid. If the Environment is defined, contact your administrator to determine if you should be authorized to access the Environment.
Reason:
The ENESCLIN data set did not contain any valid action SCL statements. Either the data set was empty, or the data set contained syntactically invalid statements.
Action:
Verify that the ENESCLIN DD statement refers to a data set that contains Batch Environment Administration control statements (SCL). Correct the execution JCL as needed and resubmit the request.
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action specified a SYSTEM that is not defined to the ENVIRONMENT identified.
Action:
Verify that the correct Environment and System were specified on the request, and resubmit the request.
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action specified a SUBSYSTEM that is not defined to the ENVIRONMENT and SYSTEM identified.
Action:
Verify that the correct Environment, System, and Subsystem were specified on the request, and resubmit the request.
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action specified a TYPE that is not defined to the ENVIRONMENT, SYSTEM, and Stage IDentified.
Action:
Verify that the correct Environment, System, Stage, and Type were specified on the request, and resubmit the request.
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action specified an APPROVER GROUP that is not defined to the ENVIRONMENT.
Action:
Verify that the correct Environment and Approver Group were specified on the request, and resubmit the request.
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action specified a PROCESSOR GROUP that is not defined to the Environment, System, Type, and Stage IDentified.
Action:
Verify that the correct Environment, System, Stage, Type, and Processor Group were specified on the request, and resubmit the request.
Reason:
The path prefix or path name can contain a single quote character or a double quote character, but not both.
Action:
Correct the syntax and resubmit the job.
Reason:
A $IMR error occurred in routine name. The $IMR message text follows:
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action received an error condition from the $IMR service. The message that follows ENBE083E identifies the error that occurred.
Action:
Contact your administrator.
Reason:
Beginning with CA Endevor SCM release 4.0, the NEXT TYPE name cannot differ from the current TYPE, because type name changes across the map are not allowed.
Action:
Verify that the correct type name is specified on the request and resubmit the request.
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action specified a STAGE ID that is not defined to the Environment.
Action:
Change the STAGE ID clause to a valid Stage ID. Resubmit the request.
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action used name masking to specify the System name, Environment name, or both. No match was found.
Action:
Verify that the correct Environment and System were specified. Resubmit the request.
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action used name masking to specify the Subsystem name, System name, Environment name, or a combination thereof. No match was found.
Action:
Verify that the correct Environment, System, and Subsystem were specified on the request, and resubmit the request.
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action used name masking to specify the Type name, System name, Environment name, or a combination thereof. No match was found.
Action:
Verify that the correct Environment, System, Type, and Stage were specified on the request, and resubmit the request.
Reason:
The Environment specified on the BUILD SCL FOR ENVIRONMENT action did not contain any Systems, Subsystems, Type, Processor Groups, or Processor Symbols.
Action:
Verify that the correct Environment was specified on the request, and resubmit the request.
Reason:
The specified function was unable to obtain the specified amount of storage. The number of bytes is specified in hexadecimal.
Action:
Increase the region size on the REGION= JCL statement and resubmit the request. If the problem persists and the DEFINE or DELETE action contains a wildcarded object name, modify the request to specify multiple explicit requests. If the BUILD SCL FOR action specifies the INCLUDE SUBORDINATES clause, remove the clause. If the ENESCLIN data set contains more than one request, submit each request as an individual job. If the problem persists, contact your administrator.
Reason:
An internal error occurred in the above function. The error text identifies the error that occurred.
Action:
Contact your administrator.
Reason:
An internal error occurred in the above function. The DEFINE, DELETE, or BUILD SCL FOR action cannot continue to process.
Action:
Contact your administrator.
Reason:
An internal error occurred in the above function. The DEFINE, DELETE, or BUILD SCL FOR action cannot continue to process.
Action:
Contact your administrator.
Reason:
An internal error occurred in the above function. The DEFINE, DELETE, or BUILD SCL FOR action cannot continue to process.
Action:
Contact your administrator.
Reason:
An internal function determined that the parser passed an invalid token. Message ENBE097S further identifies the error.
Action:
Contact your administrator.
Reason:
This message is issued with message ENBE096S to identify the parser token that was invalid.
Action:
Contact your administrator.
Reason:
An internal function determined that the parser returned an invalid token. The field that contains the invalid string appears in message ENBE099S.
Action:
Contact your administrator.
Reason:
This message is issued with message ENBE098S to identify the parser token that was invalid.
Action:
Contact your administrator.
Reason:
An unexpected return code was received from the internal function identified. See message ENBE101S. This message lists the field name and string that was passed to the above function.
Action:
Contact your administrator.
Reason:
This message is issued with message ENBE100S to identify the invalid return code.
Action:
Contact your administrator.
Reason:
An invalid parameter value was passed to the internal function identified. See message ENBE103S. This message lists the parameter name of the field and value that was passed to the above function.
Action:
Contact your administrator.
Reason:
See message ENBE102S. This message lists the parameter name of the field and value that was passed to the above function listed in message ENBE102S.
Action:
Contact your administrator.
Reason:
An error occurred when trying to create a new Tagged Field Object. The DEFINE, DELETE, or BUILD SCL FOR action cannot continue processing.
Action:
Contact your administrator.
Reason:
An invalid keyword value was used in function "FUNCTION NAME." See message ENBE106S. This message lists the keyword and the value of the keyword.
Action:
Contact your administrator.
Reason:
See message ENBE105S. This message lists the keyword and the value of the keyword used in the above function listed in message ENBE105S.
Action:
Contact your administrator.
Reason:
An unexpected return code was received from function "FUNCTION NAME." See message ENBE108S. This message lists the field name and data set name that was passed to the above function.
Action:
Contact your administrator.
Reason:
See message ENBE107S. This message lists the field name and data set name that was passed to the function listed in message ENBE107S.
Action:
Contact your administrator.
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action for the object identified has completed with the return code indicated. If the return code is not zero, one or more messages should be written to indicate the reason for the non-zero return code.
Action:
None.
Reason:
The DEFINE SYSTEM action created or modified the System definition identified.
Action:
None.
Reason:
The DEFINE SUBSYSTEM action created or modified the Subsystem definition identified.
Action:
None.
Reason:
The DEFINE TYPE action created or modified the Type definition identified.
Action:
None.
Reason:
The Type Sequence record listed associated with the Environment, System, and Stage IDentified was created or updated.
Action:
None.
Reason:
The BUILD SCL FOR action has created DEFINE SCL for the System identified.
Action:
None.
Reason:
The BUILD SCL FOR action has created DEFINE SCL for the Subsystem identified.
Action:
None.
Reason:
The BUILD SCL FOR action has created DEFINE SCL for the Type identified.
Action:
None.
Reason:
The BUILD SCL FOR action has created DEFINE SCL for the Processor Group identified.
Action:
None.
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action used name masking to specify the Processor Group, Environment name, System name, or Type name, or a combination thereof. No match was found.
Action:
Verify that the inventory locations specified on the ENVIRONMENT, SYSTEM, TYPE, STAGE, and PROCESSOR GROUP clauses are valid, and resubmit the request.
Reason:
The BUILD SCL FOR action has created DEFINE SCL for the Approver Group identified.
Action:
None.
Reason:
The BUILD SCL FOR action determined that there were no Types associated with the System and Stage IDentified.
Action:
None.
Reason:
The BUILD SCL FOR action has created DEFINE SCL for the Type Sequence definition at the Environment, System, and Stage IDentified.
Action:
None.
Reason:
The DEFINE APPROVER GROUP action is modifying an existing Approver Group. The number of Approver User IDs that will be added to the Approver Group will cause more than 16 Approver User IDs to be associated with the Approver Group. An Approver Group can only contain 16 Approver User IDs.
Action:
Decrease the number of Approver User IDs specified on the DEFINE APPROVER GROUP action APPROVER clause, and resubmit the request.
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action used name masking to specify the Approver Group name, Environment name, or both, and no match was found for a name masked value.
Action:
Verify that the ENVIRONMENT name and the APPROVER GROUP name specified on the action are valid.
Reason:
An internal function received an invalid parameter value. Message ENBE126S identifies the invalid parameter that the routine received.
Action:
Contact your administrator.
Reason:
See message ENBE125S. This message lists the parameter name of the field and string that was passed to the above function listed in message ENBE125S.
Action:
Contact your administrator.
Reason:
The Approver User ID specified on the DELETE APPROVER GROUP action APPROVER clause was not defined to the Approver Group. The DELETE APPROVER GROUP action continues to process.
Action:
Verify that the Approver User IDs specified on the APPROVER clause are correct. Also verify that the correct Approver Group and Environment were specified on the request, and resubmit the request.
Reason:
The APPROVER ID user ID was successfully deleted from the APPROVER GROUP identified.
Action:
None.
Reason:
The DEFINE APPROVER GROUP action has either created or modified the Approver Group identified.
Action:
None.
Reason:
The Approver Group specified on the DEFINE, DELETE, or BUILD SCL FOR action is not defined.
Action:
Verify that Approver Group, Environment, System, Stage, Subsystem, and Types specified are correct, and resubmit the request.
Reason:
An attempt was made to DEFINE an APPROVER RELATION that already existed.
Action:
Verify that Approver Group, Environment, System, Stage, and Subsystem specified are correct, and resubmit the request.
Reason:
The DEFINE PROCESSOR GROUP action has created or updated the Processor Group identified.
Action:
None.
Reason:
The DEFINE APPROVER RELATION action has created or modified the Approver Relationship between the Approver group and the inventory location identified.
Action:
None.
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action specified a wildcarded SHIPMENT DESTINATION name and there were no matches for the wildcarded SHIPMENT DESTINATION name.
Action:
Verify that the correct Shipment Destination name was specified, and resubmit the request.
Reason:
The DEFINE PROCESSOR SYMBOL action requires at least one SYMBOL clause. The SYMBOL clause identifies the SYMBOL name that will be updated by the action.
Action:
Add at least one SYMBOL clause to the DEFINE PROCESSOR SYMBOL action, and resubmit the request.
Reason:
The BUILD SCL FOR action has created DEFINE SCL for the Processor Symbols associated with the Processor Group identified.
Action:
None.
Reason:
The DEFINE PROCESSOR SYMBOL action is only valid if the GENERATE, DELETE, or MOVE Processor Name is not *NOPROC*.
Action:
Verify that the correct Environment, System, Type, Stage, Processor Group, and Processor Type were specified, and resubmit the request.
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action received an error condition from the $PKMR service. The message that follows ENBE138E should indicate the error that occurred.
Action:
Review the message that follows ENBE138E. Contact your administrator.
Reason:
The BUILD SCL FOR SHIPMENT DESTINATION action was unable to determine the transmission method associated with the Shipment Destination. The SCL for the TRANSMISSION METHOD clause was assigned the value *UNKNOWN*.
Action:
Use the DEFINE SHIPMENT DESTINATION action to correct the TRANSMISSION METHOD associated with the Shipment Destination. The SCL created by the BUILD SCL FOR SHIPMENT DESTINATION action will contain an invalid transmission method.
Reason:
The SHIPMENT DESTINATION define SCL statement is still generated even though the host and/or remote path names are invalid. Single and double quotes cannot be used together in the path-name. If this syntax is used, this Define action will fail.
Action:
You will need to adjust the affected path name.
Reason:
The BUILD SCL FOR SHIPMENT DESTINATION action has created DEFINE SCL from the Shipment Destination identified and any associated Mapping Rules.
Action:
None.
Reason:
The DELETE or BUILD SCL FOR action specified a SHIPMENT DESTINATION that is not defined.
Action:
Verify that the Shipment Destination specified on the DELETE or BUILD SCL FOR SHIPMENT DESTINATION action is correct, and resubmit the request.
Reason:
An unrecoverable error occurred while processing the DEFINE PROCESSOR SYMBOL action. A detailed message follows this message.
Action:
Examine the detailed message and take the appropriate action.
Reason:
The Processor Symbol identified is not defined to the Processor identified.
Action:
Verify the symbol name specified on the DEFINE PROCESSOR SYMBOL action SYMBOL clause is spelled correctly. Verify that the correct Environment, System, Type, Stage, Processor Group, and Processor Type were specified, and resubmit the request.
Reason:
The symbol name specified in the DELETE PROCESSOR SYMBOL action SYMBOL clause did not have an override assigned or the symbol does not exist in the processor.
Action:
None.
Reason:
The user specified a DELETE PROCESSOR SYMBOL action and ALL the Processor Symbol override values were deleted.
Action:
None.
Reason:
The DELETE PROCESSOR SYMBOL action has deleted the number of symbols indicated from the Generate, Move, or Delete Processor identified.
Action:
None.
Reason:
An internal CA Endevor SCM service returned an error condition. The DEFINE, DELETE, or BUILD SCL FOR action cannot continue processing.
Action:
Contact your administrator.
Reason:
An internal routine encountered an unrecoverable error. The DEFINE, DELETE, or BUILD SCL FOR action cannot continue processing.
Action:
Contact your administrator.
Reason:
The above Processor Symbol will be created or updated unless a processing error occurs.
Action:
None.
Reason:
The DEFINE SHIPMENT DESTINATION action has created or updated the Shipment Destination identified.
Action:
None.
Reason:
The DEFINE PROCESSOR SYMBOL has added the processor symbol overrides for the GENERATE, MOVE, or DELETE Processor associated with the Processor that is identified.
Action:
None.
Reason:
The DELETE PROCESSOR GROUP action has deleted the Processor Group identified.
Action:
None.
Reason:
The GENERATE, MOVE, or DELETE Processor associated with the Processor Group specified on the BUILD SCL FOR PROCESSOR SYMBOLS action did not contain any symbols. The BUILD SCL FOR action cannot, therefore, create any DEFINE SCL statements.
Action:
None.
Reason:
The BUILD SCL FOR action TO location data set failed validation. The previous error message indicates the reason for the failure.
Action:
See the previous error message and take the corrective action associated with the error. If the data set has an invalid data set attribute, either respecify the correct TO location, or reallocate the data set with the correct attributes, and resubmit the request.
Reason:
The BUILD SCL FOR APPROVER RELATION action has created DEFINE SCL to relate the Approver Group identified to the inventory location identified.
Action:
None.
Reason:
The BUILD SCL FOR SHIPMENT MAPPING RULE action has created a DEFINE SCL statement for the data set Mapping Rule identified and associated with the Shipment Destination identified.
Action:
None.
Reason:
The DEFINE SHIPMENT MAPPING RULE action has created or modified the Mapping Rule for the data set specified.
Action:
None.
Reason:
The Shipment Destination identified was created, updated, or deleted.
Action:
None.
Reason:
The DELETE or BUILD SCL FOR action specified a SHIPMENT MAPPING RULE that was not defined for the Shipment Destination specified.
Action:
Verify that both the SHIPMENT DESTINATION and the HOST DATA SET clauses are correct, and resubmit the request.
Reason:
Informational message to confirm that the USS mapping rule has been deleted for the specified destination and path name.
Action:
None.
Reason:
The Shipment Destination specified is in use by another user. Only one user can process a Shipment Destination at a time.
Action:
Resubmit the request at a later time.
Reason:
The ELEMENT DELTA FORMAT IS FORWARD and the DO NOT COMPRESS BASE clauses are mutually exclusive. If the ELEMENT DELTA FORMAT IS FORWARD clause is specified, the DO NOT COMPRESS BASE cannot be specified; or, if the DO NOT COMPRESS BASE clause was specified, the ELEMENT DELTA FORMAT IS FORWARD clause cannot be specified.
Action:
Change the DO NOT COMPRESS BASE clause to COMPRESS BASE; or, change the ELEMENT DELTA FORMAT IS FORWARD to ELEMENT DELTA FORMAT IS REVERSE. Resubmit the request.
Reason:
When ELEMENT DELTA FORMAT IS FORWARD is specified, the base files have to be compressed, and the DO NOT COMPRESS BASE clause cannot be specified.
Action:
Change the DO NOT COMPRESS BASE clause to COMPRESS BASE or change the ELEMENT DELTA FORMAT IS FORWARD to ELEMENT DELTA FORMAT IS REVERSE. Resubmit the request.
Reason:
The NUMBER OF ELEMENT LEVELS TO CONSOLIDATE or the NUMBER OF COMPONENT LEVELS TO CONSOLIDATE value must not be zero when the corresponding CONSOLIDATE Element LEVELS or CONSOLIDATE component LEVELS clause is specified.
Action:
Specify a value of greater than zero for the NUMBER OF ELEMENT LEVELS TO CONSOLIDATE or the NUMBER OF COMPONENT LEVELS TO CONSOLIDATE clause. Resubmit the request.
Reason:
The NUMBER OF ELEMENT LEVELS TO CONSOLIDATE or the NUMBER OF COMPONENT LEVELS TO CONSOLIDATE must be zero when the corresponding CONSOLIDATE Element LEVELS or CONSOLIDATE component LEVELS clause is specified.
Action:
Specify a value of zero for the NUMBER OF ELEMENT LEVELS TO CONSOLIDATE or the NUMBER OF COMPONENT LEVELS TO CONSOLIDATE clause. Resubmit the request.
Reason:
The NUMBER OF ELEMENT LEVELS TO CONSOLIDATE or the NUMBER OF COMPONENT LEVELS TO CONSOLIDATE must not be zero when the corresponding CONSOLIDATE Element LEVELS or CONSOLIDATE component LEVELS clause is specified.
Action:
Specify a NUMBER OF ELEMENT LEVELS TO CONSOLIDATE or the NUMBER OF COMPONENT LEVELS TO CONSOLIDATE value that is greater than or equal to zero. Resubmit the request.
Reason:
The NUMBER OF ELEMENT LEVELS TO CONSOLIDATE or the NUMBER OF COMPONENT LEVELS TO CONSOLIDATE value must be zero when the corresponding CONSOLIDATE Element LEVELS or CONSOLIDATE component LEVELS clause is specified.
Action:
Specify a NUMBER OF ELEMENT LEVELS TO CONSOLIDATE or the NUMBER OF COMPONENT LEVELS TO CONSOLIDATE value of zero. Resubmit the request.
Reason:
The data set logical record length (LRECL) for the SOURCE OUTPUT DATA SET associated with the DEFINE TYPE action is smaller than the SOURCE ELEMENT LENGTH value associated with the Type. The SOURCE OUTPUT DATA SET logical record length must be greater than or equal to the SOURCE ELEMENT LENGTH value.
Action:
Verify that the correct SOURCE ELEMENT LENGTH value was specified. Verify that the correct SOURCE OUTPUT DATA SET was specified. Correct either the SOURCE ELEMENT LENGTH value or the SOURCE OUTPUT DATA SET value. If necessary, reallocate the SOURCE OUTPUT data set so that it has a record length that is at least as large as the SOURCE ELEMENT LENGTH value.
Reason:
The BASE, DELTA, INCLUDE, or SOURCE OUTPUT data set has invalid attributes for a TYPE data set.
Action:
For information on the attributes of the Base, Delta, and Source Output libraries, see the Administration Guide.
Reason:
An internal CA Endevor SCM service was unable to validate the data set identified in the message. A second error message should follow message ENBE171E to indicate the error that occurred.
Action:
See the corrective action associated with the error message that should follow message ENBE171E.
Reason:
An internal error occurred while processing the DEFINE, DELETE, or BUILD SCL FOR TYPE SEQUENCE action.
Action:
Contact your administrator.
Reason:
The NUMBER OF ELEMENT LEVELS or the NUMBER OF COMPONENT LEVELS is greater than the corresponding CONSOLIDATE ELEMENT AT LEVEL or CONSOLIDATE COMPONENT AT LEVEL value.
Action:
Specify a NUMBER OF ELEMENT LEVELS or NUMBER OF COMPONENT LEVELS clause value that is less than or equal to the corresponding CONSOLIDATE ELEMENT AT LEVEL or CONSOLIDATE COMPONENT AT LEVEL clause value.
Reason:
The CONSOLIDATE ELEMENT AT LEVEL or the CONSOLIDATE COMPONENT AT LEVEL VALUE was less than the corresponding NUMBER OF ELEMENT LEVELS TO CONSOLIDATE or NUMBER OF COMPONENT LEVELS TO CONSOLIDATE value.
Action:
Specify a CONSOLIDATE ELEMENT AT LEVEL or a CONSOLIDATE COMPONENT AT LEVEL clause value that is greater than or equal to the corresponding NUMBER OF ELEMENT LEVELS or NUMBER OF COMPONENT LEVELS clause value.
Reason:
The SIGNOUT DATA SET VALIDATION IS ACTIVE cannot be specified if the Signout option is not active for the System.
Action:
Change the SIGNOUT IS NOT ACTIVE clause to SIGNOUT IS ACTIVE or change the SIGNOUT DATA SET VALIDATION IS ACTIVE to SIGNOUT DATA SET VALIDATION IS NOT ACTIVE.
Reason:
The SIGNOUT DATA SET VALIDATION IS ACTIVE cannot be specified if data set signout validation was already activated for the System.
Action:
Change the SIGNOUT IS NOT ACTIVE clause to SIGNOUT IS ACTIVE or change the SIGNOUT DATA SET VALIDATION IS ACTIVE to SIGNOUT DATA SET VALIDATION IS NOT ACTIVE.
Reason:
An application ABEND occurred during execution of the Batch Environment Administration Facility. Processing is unable to continue.
Action:
Contact your administrator.
Reason:
No USS mapping rule is defined for the specified host path name and destination.
Action:
Verify the syntax to make sure you specified the correct information.
Reason:
An error occurred when attempting to write SCL statements for a BUILD SCL FOR action.
Action:
See the JES Message log to determine if there were any System errors. If so, take the corrective action associated with the error. Resubmit the request. If the problem persists, contact your administrator.
Reason:
The Batch Environment Administration Facility or the ISPF dialog is currently processing an Environment definition associated with the Environment and System specified. Only one user at a time can access an Environment definition in an Environment and System. The current request is terminated.
Action:
Resubmit the request at a later time.
Reason:
There are no approver group relationships defined for the approver group identified in the Environment.
Action:
Verify that the correct approver group was specified in the request. Resubmit the request after any changes are made.
Reason:
The data set specified on the BUILD SCL FOR action TO DSNAME clause was sequential. The action also contained the MEMBER clause. The MEMBER clause is inconsistent with the data set organization, so the BUILD action ignores the clause.
Action:
None. However, to eliminate the message, remove the MEMBER clause from the action. Alternatively, specify a partitioned data set for the TO DSNAME.
Reason:
An error occurred while attempting to validate the attributes of the STAGE ONE or TWO LOAD or LIST library. A second message may follow message ENBE190E to indicate the reason for the failure.
Action:
If a second error message was issued, follow the corrective action described for the message, and resubmit the request.
Reason:
The Element Type delta format is defined as either full Image or log. The regression percentage value has no meaning or purpose for the types defined as full image and log.
Action:
The value must be set to zero. If omitted on a new definition, it defaults to zero.
Reason:
You cannot change a type definition from Full Image to Reverse or Forward delta or from Reverse or Forward to Full Image delta, if Elements exist at the specified location for this type.
Action:
None.
Reason:
Values must be a-z, A-Z, 0-9, or blanks. Embedded blanks are not allowed.
Action:
Define a file extension name that satisfies the naming standard.
Reason:
You cannot change the Source Element Length in a type definition, if Elements exist at the specified location for this type.
Action:
None.
Reason:
The Batch Environment Administration facility abended with the code identified. The current action will terminate processing immediately and any remaining, unexecuted actions will not be executed.
Action:
Resubmit the request. If the problem persists, contact your administrator. You will need to create a diagnostic dump of the ABEND before you contact your administrator, however. Add the following card to the execution JCL and resubmit the request:
//SYSABEND DD SYSOUT=*
This JCL statement creates a diagnostic dump when the ABEND occurs.
Reason:
A Batch Admin job was submitted with Build Type Sequence SCL. This SCL refers to type sequencing under a particular Environment, Stage, and System. When the Global Type Sequencing feature is turned on at the site level, the type sequencing definitions are ignored. The Build SCL action fails.
Action:
No action is required. However, you may want to remove the Build Type Sequence SCL statements in Batch Admin jobs submitted in the future to avoid getting this message and to prevent other actions in this job from being executed due to the return code value.
Reason:
A Batch Admin job was submitted with Define Type Sequence SCL. This SCL refers to type sequencing under a particular Environment, Stage, and System. When Global Type Sequencing is turned on at the site level, these definitions are ignored. The Define SCL action completes and creates or updates the local Type Sequence. However because the Global Type Sequence is in effect, the local Type Sequence order will not be used for action processing.
Action:
No action is required, but you may want to remove the Define Type Sequence SCL statements in Batch Admin jobs submitted in the future to avoid getting this message.
Reason:
Value specified in the APPROX MEMBERS PER CYL is not within range.
Action:
Specify the correct value.
Reason:
The Batch Environment Administration Facility or the ISPF dialog is currently processing a Type definition associated with the Environment and System specified. Only one user at a time can access a Type definition in an Environment and System. The current request is terminated.
Action:
Resubmit the request at a later time.
Reason:
The SHIPMENT USS MAPPING RULE define SCL statement for the named destination is still generated even though the host and/or remote path names are invalid. Single and double quotes cannot be used together in the path-name. If this syntax is used, this Define action will fail.
Action:
You will need to adjust the affected path name.
Reason:
The program is beginning to parse the user-supplied control statements.
Action:
None.
Reason:
The program has completed parsing the control statements and no errors were detected.
Action:
None.
Reason:
The program has completed parsing the control statements. One or more errors were detected in the control statements. None of the actions specified will be performed.
Action:
Refer to the Batch Environment Control Statement Summary Report to determine the error that terminated the request. Take the corrective action that the error message indicates, and resubmit the request.
Reason:
The execution JCL contained the PARM=VALIDATE statement. The program only parses the control statements. The control statements will not be executed.
Action:
None.
Reason:
The DEFINE TYPE action did not specify the required SOURCE ELEMENT LENGTH clause.
Action:
Add the SOURCE ELEMENT LENGTH clause to the DEFINE TYPE statement, and resubmit the request.
Reason:
The DEFINE SYSTEM action did not specify the required COMPARE FROM COLUMN clause.
Action:
Add the COMPARE FROM COLUMN clause to your DEFINE TYPE statement, and resubmit the request.
Reason:
The DEFINE action clause identified specified a value that is outside the valid range for the clause. See the SCL Reference Guide to determine the valid value range for the clause that was identified.
Action:
Specify a valid value in the clause. Resubmit the request.
Reason:
The DEFINE TYPE action did not specify the required LANGUAGE clause.
Action:
Add the LANGUAGE clause to your DEFINE TYPE statement.
Reason:
The DEFINE TYPE action did not specify the required BASE LIBRARY or or DELTA LIBRARY clause.
Action:
Add the BASE LIBRARY or DELTA LIBRARY clause to the DEFINE TYPE action and resubmit the request.
Reason:
The DEFINE action contained a wildcard value for the NEXT SYSTEM, SUBSYSTEM, TYPE, or PROCESSOR GROUP.
Action:
Specify a fully qualified NEXT clause. Resubmit the request.
Reason:
The DEFINE TYPE SEQUENCE action SEQUENCE clause contained at least two (type name, sequence number) pairs that specified the same sequence number. For example: SEQUENCE=((TYPE1,15),(TYPE2,15)). The
sequence number values must be unique.
Action:
Change the duplicate sequence numbers so that the values are unique, and resubmit the request.
Reason:
The DEFINE TYPE SEQUENCE action SEQUENCE clause contained at least two (type name, sequence number) pairs that specified the same Element type. For example: SEQUENCE=((TYPE1,15),(TYPE1,25)). The Element
type values must be unique.
Action:
Change the duplicate Element types so that the values are unique, and resubmit the request.
Reason:
The DEFINE TYPE action COMPARE FROM value is greater than the TO value.
Action:
Change the COMPARE FROM value to a value less than or equal to the COMPARE TO value, and resubmit the request.
Reason:
The STAGE ONE LOAD or LIST LIBRARY and the corresponding STAGE TWO LOAD or LIST LIBRARY refer to the same data set. The DEFINE SYSTEM action continues processing.
Action:
None. However, if the STAGE ONE LOAD or LIST library should be different than the corresponding STAGE TWO LIBRARY, use the DEFINE SYSTEM action to make the appropriate change.
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action contained a clause that specified an invalid value. The name identifies the DEFINE, DELETE, or BUILD SCL FOR action clause that contained the invalid parameter. In general, the values specified on a DEFINE, DELETE, or BUILD SCL FOR action clause can contain only alphanumeric and national characters. For a detailed | description of the valid characters for each action clause, see the SCL Reference Guide.
Action:
Specify a valid value for the action clause that was identified, and resubmit the request.
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action STAGE NUMBER can only be a 1 or a 2.
Action:
Change the STAGE NUMBER to a 1 or a 2. Resubmit the request.
Reason:
The language specified for the PANVALET or LIBRARIAN LANGUAGE clause is not a valid CA Panvalet or CA Librarian language.
Action:
Specify a valid CA Panvalet or CA Librarian language. For a list of valid CA Panvalet or CA Librarian languages, see the SCL Reference Guide.
Reason:
The COMPARE FROM and TO column values fall outside the standard column range for the language identified. The DEFINE TYPE continues processing the request.
Action:
If the COMPARE column range identified in the message is correct, no changes are necessary. For a list of the standard COMPARE column ranges for each standard language, see the SCL Reference Guide.
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action contained a clause that specified a wildcarded value. The name field identifies the action clause that does not support wildcards.
Action:
Specify a fully qualified value for DEFINE, DELETE, or BUILD SCL FOR action clause specified in the message. Resubmit the request.
Reason:
The DEFINE, DELETE, or BUILD SCL FOR APPROVER RELATION action contained a clause that specified a partially wildcarded value. The name field identifies the clause that does not support partial wildcards. The value specified for the clause that was identified must be either fully qualified or fully wildcarded.
Action:
Specify a fully qualified or a fully wildcarded value for the action clause specified, and resubmit the request.
Reason:
The COMPARE FROM or TO value specified on the DEFINE TYPE action is greater than the source Element length. The source Element length can be obtained from the existing type definition or from the SOURCE ELEMENT LENGTH clause.
Action:
Change the COMPARE FROM clause so that the values are less than or equal to the SOURCE ELEMENT LENGTH or change the SOURCE ELEMENT LENGTH so that it is greater than or equal to the COMPARE TO value. Resubmit the request.
Reason:
The BUILD SCL FOR action requires either the TO DSNAME or the TO DDNAME. These clauses identify the location to which the DEFINE SCL statements will be written.
Action:
Add a valid TO DDNAME or TO DSNAME clause to the BUILD SCL FOR action, and resubmit the request.
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action is missing the clause identified. The missing clause is required for the action.
Action:
Specify the missing clause and resubmit the request.
Reason:
The DELETE or BUILD SCL FOR request requires the FROM STAGE ID or FROM STAGE NUMBER clause. The request did not contain such a clause.
Action:
Add either the FROM STAGE ID or the FROM STAGE NUMBER clause to the action, and resubmit the request.
Reason:
There is a mismatch between the DEFINE TYPE request and the level of CA Panvalet or CA Librarian support that is specified in the C1DEFLTS table. The level of CA Panvalet or CA Librarian support is identified by the LIBENV parameter on the C1DEFLTS TYPE=MAIN macro. The mismatch can occur under the following circumstances:
Action:
If neither CA Panvalet nor CA Librarian are installed, do not specify the LIBRARIAN or PANVALET LANGUAGE clause. If CA Librarian is installed, use the LIBRARIAN LANGUAGE clause. If CA Panvalet is installed, use the PANVALET LANGUAGE clause. Resubmit the request.
Action:
See message ENBE942E.
Action:
See message ENBE942E.
Reason:
Symbolics were being resolved in the BASE, DELTA, INCLUDE, or SOURCE OUTPUT LIBRARY. The symbolics were invalid. Messages ENBE941 and ENBE942 contain the details of the error message. There will be plus signs (+) in the data set name for message ENBE942 to show the locations of the invalid symbolics.
Action:
Correct the symbolics in the BASE, DELTA, INCLUDE or SOURCE OUTPUT LIBRARY name. Resubmit the request.
Reason:
Type PROCESS is a special type and the language specified in the LANGUAGE clause must be CNTLPROC.
Action:
Change the language in the LANGUAGE clause to CNTLPROC and resubmit the request.
Reason:
The DEFINE TYPE SEQUENCE action requires at least one valid SEQUENCE clause but the request did not contain a SEQUENCE clause.
Action:
Add the appropriate SEQUENCE clause to resequence the Type names into the sequence that you want, and resubmit the request.
Reason:
The Sequence Number specified must be between 0 and 9999.
Action:
Change the invalid sequence number to a value between 0 and 9999, and resubmit the request.
Reason:
The BUILD SCL FOR action specified both the TO DDNAME and the TO DSNAME clauses. These clauses are mutually exclusive. Only one of the clauses can be specified.
Action:
Remove either the TO DDNAME clause or the TO DSNAME clause, and resubmit the request.
Reason:
The Type Sequence number specified on the SEQUENCE clause cannot be a multiple of 10, for example, 10, 20, 30, and so on. The Type Sequence number can be any value that is not a multiple of 10.
Action:
Change any sequence numbers specified that are multiples of 10, and resubmit the request.
Reason:
The Maximum Number of (type, sequence) pairs is 256. Since the maximum number of TYPES for one SYSTEM is 256, it is not possible to resequence more than 256 (type, sequence) pairs.
Action:
Remove any (TYPE, SEQUENCE) pairs that are not valid, and resubmit the request.
Reason:
If the DEFINE PROCESSOR GROUP is for the Group *NOPROC*, the clause identified is not allowed on the request.
Action:
Remove the invalid clause from the DEFINE PROCESSOR GROUP request and resubmit the job.
Reason:
GENERATE, DELETE, or MOVE Processors cannot be named with Reserved Processor names. The following Processor Names are reserved by CA Endevor SCM: BASICDEL, BASICGEN, DPPROCESS, and GPPROCSS.
Action:
Specify a valid, non-reserved name for the GENERATE, DELETE, or MOVE processor, and resubmit the request.
Reason:
The FROM or TO Processor Group Name must be a valid Processor Group, and cannot be *NOPROC*.
Action:
Change the FROM or TO PROCESSOR GROUP name to the name of a valid Processor Group, and resubmit the request.
Reason:
The DEFINE or DELETE PROCESSOR SYMBOL action specified a duplicate symbol name on the SYMBOL clause.
Action:
Change the duplicate symbol names so that the names are unique, and resubmit the request.
Reason:
The duplicate Approver ID was specified. The Approver IDs specified for an Approver Group must be unique.
Action:
Remove the duplicate Approver ID from the APPROVER clause of the DEFINE APPROVER action, and resubmit the request.
Reason:
An Approver Group can have a maximum of 16 Approver User IDs. The DEFINE APPROVER GROUP action specified more than 16 Approver User IDs on the APPROVER clause.
Action:
Specify a maximum of 16 Approver User IDs on the APPROVER clause of the DEFINE APPROVER GROUP action, and resubmit the request.
Reason:
The DEFINE SHIPMENT DESTINATION action specified an invalid TRANSMISSION METHOD. For a list of valid Transmission Methods, see the SCL Reference Guide.
Action:
Correct the TRANSMISSION METHOD clause. Resubmit the request.
Reason:
The REMOTE NODENAME, HOST UNIT, or REMOTE UNIT name contains embedded blanks.
Action:
Remove the embedded blanks from the REMOTE NODENAME, HOST UNIT, or REMOTE UNIT name, and resubmit the request.
Reason:
The DEFINE PROCESSOR SYMBOL action requires at least one valid SYMBOL clause. The request did not contain any SYMBOL clauses.
Action:
Add at least one valid SYMBOL clause to the request, and then resubmit the request.
Reason:
The DEFINE SHIPMENT DESTINATION action REMOTE DATA SET clause and the EXCLUDE clauses are mutually exclusive.
Action:
Remove either the REMOTE DATA SET clause or the EXCLUDE clause, and resubmit the request.
Reason:
The DEFINE action did not contain the identified clause. The clause is required for the action to complete.
Action:
Add the required clause to the request and resubmit the request.
Reason:
The NUMBER OF ELEMENT LEVELS or the NUMBER OF COMPONENT LEVELS is greater than the corresponding CONSOLIDATE ELEMENT AT LEVEL or CONSOLIDATE COMPONENT AT LEVEL value.
Action:
Specify a NUMBER OF ELEMENT LEVELS or NUMBER OF COMPONENT LEVELS value that is less than or equal to the corresponding CONSOLIDATE ELEMENT AT LEVEL or CONSOLIDATE COMPONENT AT LEVEL value, and resubmit the request.
Reason:
When ELEMENT DELTA FORMAT IS FORWARD is specified, the base files have to be compressed. If the DO NOT COMPRESS BASE clause is specified, it is ignored.
Action:
None.
Reason:
The NUMBER OF ELEMENT LEVELS or the NUMBER OF COMPONENT LEVELS must be zero when CONSOLIDATE Element LEVELS or CONSOLIDATE component LEVELS is specified.
Action:
Specify a value of zero for the NUMBER OF ELEMENT LEVELS OR NUMBER OF COMPONENT LEVELS, and resubmit the request.
Reason:
The SOURCE ELEMENT LENGTH for TYPE PROCESS does not have the value of 80.
Action:
Specify a value of 80 for the SOURCE ELEMENT LENGTH, and resubmit the request.
Reason:
If the Extended Processor support option was not purchased (or missing the PROC password in the C1DEFLTS table), the DEFINE SYSTEM action does not support the STAGE ONE or LOAD LIBRARY and the STAGE TWO LOAD LIBRARY clauses.
Action:
Either remove the STAGE ONE LOAD LIBRARY or the STAGE TWO LOAD LIBRARY clauses (or both) from the DEFINE SYSTEM action and resubmit the request, or define the password and reassemble and link the C1DEFLTS table.
Reason:
If the Extended Processor support option was not purchased (or missing the PROC password in the C1DEFLTS table), the DEFINE TYPE action does not support the Type name 'PROCESS'
Action:
Either change the Type name specified on the DEFINE TYPE action and resubmit the request or define the password and reassemble and link the C1DEFLTS table.
Reason:
If the Extended Processor support option was not purchased (or missing the PROC password in the C1DEFLTS table), the DEFINE PROCESSOR GROUP action can only specify '*NOPROC*' as the GENERATE, DELETE, and MOVE Processor names. Any other Processor Name is invalid.
Action:
Either remove the GENERATE, DELETE, or MOVE PROCESSOR clauses, or change the Processor Names to *NOPROC* and resubmit the request, or define the password and reassemble and link the table.
Reason:
When the DEFINE PROCESSOR GROUP name is *NOPROC*, the generate│move│delete PROCESSOR names, if specified, must also be *NOPROC*.
Action:
Either remove the GENERATE, DELETE, MOVE PROCESSOR clauses, or change the Processor Names to *NOPROC*. Resubmit the request.
Reason:
The data set name for the DEFINE action clause identified was blank. The data set name must be a valid, non-blank name.
Action:
Specify a valid data set name for the identified clause and resubmit the request.
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action specified both the STAGE ID clause and the STAGE NUMBER clause. Only one of these clauses can be specified.
Action:
Remove either the STAGE ID clause or the STAGE NUMBER clause and resubmit the request.
Reason:
The DEFINE TYPE action specified 'CNTLPROC' on the LANGUAGE clause must CNTLPROC. The 'CNTLPROC' LANGUAGE is reserved for the Type name 'PROCESS'. The DEFINE TYPE action was for a Type other than 'PROCESS'. Therefore, the LANGUAGE clause cannot specify the value 'CNTLPROC'.
Action:
Correct the LANGUAGE clause of the Type name and resubmit the request.
Reason:
When the TYPE name is PROCESS and the PANVALET LANGUAGE is specified it must be DATA. If the LIBRARIAN LANGUAGE is specified it must be DAT. Any other values specified in these fields will be changed to DATA or DAT.
Action:
None.
Reason:
If the SIGNOUT DATA SET VALIDATION IS ACTIVE clause is specified, the SIGNOUT IS ACTIVE is a valid combination. If SIGNOUT IS NOT ACTIVE is specified you will receive this error.
Action:
Change the SIGNOUT IS NOT ACTIVE clause to SIGNOUT IS ACTIVE or change the SIGNOUT DATA SET VALIDATION IS ACTIVE to SIGNOUT DATA SET VALIDATION IS NOT ACTIVE. Resubmit the request.
Reason:
The DEFAULT PROCESSOR GROUP name was not PROCESS for TYPE PROCESS.
Action:
Change the DEFAULT PROCESSOR GROUP name to PROCESS and resubmit the request.
Reason:
If the DEFINE TYPE or DEFINE PROCESSOR GROUP is for the Type 'PROCESS', the clause cannot be specified.
Action:
Remove the invalid clause from the DEFINE TYPE or DEFINE PROCESSOR GROUP and resubmit the request.
Reason:
If the TYPE name is PROCESS the GENERATE and MOVE Processor names must be GPPROCSS and the DELETE PROCESSOR name must be DPPROCSS.
Action:
Correct the invalid processor name and resubmit the request.
Reason:
The final control statement did not contain a terminating period. All Batch Environment Administration Facility control statements must be terminated with a period.
Action:
Add a terminating period to the final control statement, and resubmit the request.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|