Messages CS1000 through CS1099

INTERNAL ERROR UPDATING THE PROFILE VARIABLE POOL

Explanation: The routine to update a PROFILE variable in the BBIVARS dataset experienced an internal error. This may be a result of a failure to allocate the required BBIVARS DDname (and dataset) for the BMC AMI Ops Automation PAS. The variable will not be rewritten to disk.

User response: Examine the BMC AMI Ops Automation PAS's JCL and ensure that a valid BBIVARS DDname is allocated. If the allocation appears valid set a slip as follows, recreate the error, and contact BMC Support with the svcdump as documentation. 

SL SET,ID=xxxx,MSGID=CS1010E,SDATA=(CSA,RGN,TRT,GRSQ),END

SYNAD EXIT ENTERED ON PROFILE - XXXXXXXX

Explanation: During variable profile data set formatting for the shown DD name, the SS synad exit was entered. This message will be shown once for an unformatted data set. Multiple occurrences of this message for the same DDname indicate a problem - Processing continues.

User response: No action is required.

UNABLE TO OPEN PROFILE - BBIVARS

Explanation: The profile dataset designated by the DDname BBIVARS could not be successfully opened. All profile variables for this pool cannot be saved during this SS session - processing continues.

User response: Add a BBIVARS DD pointing to your profile dataset to your PAS JCL. The dataset will automatically be initialized on the next PAS startup (if it was not previously initialized). See the section titled "Manual customization" in the "BMC AMI Ops Infrastructure" online documentation and BBSAMP member SSLOG for more information on creating the BBIVARS dataset.

INITIALIZING THE PROFILE DATASET - XXXXXXXX

Explanation: A variable profile dataset was specified which contained invalid data. The system will automatically format this dataset. The profile pool will then be empty.

User response: Determine the cause of the invalid contents.

I/O ERROR ON WRITE STATEMENT

Explanation: During formatting a write operation to a variable profile pool dataset failed. The dataset can not be initialized. All data set update processing for this profile data set will fail.

User response: Determine the nature of the I/O error and restart the SS.

COULD NOT OPEN PROFILE - XXXXXXXX

Explanation: During variable profile dataset formatting, the initialization routine unexpectedly was unable to open the dataset for output. This is indicative of an internal problem. The profile dataset can not be initialized.

User response: Contact BMC Software customer support.

END OF DATASET ENCOUNTERED FOR - XXXXXXXX

Explanation: The profile data set initialization routine successfully formatted the DDname shown in the message. Processing continues.

User response: No action is required.

UNABLE TO INITIALIZE THE PROFILE - XXXXXXXX

Explanation: Trying to format an uninitialized variable profile pool dataset designated by the indicated DDname, an unrecoverable I/O error was detected. No profile variables for this pool can be saved, processing will continue.

User response: Determine the reason for the I/O error. Possibly copy the profile dataset to a different volume. If the error persists contact BMC Software customer support.

SYNAD EXIT ENTERED ON PROFILE - XXXXXXXX

Explanation: The profile data set update routine detected an error trying to rewrite a variables contents to disk. The message reflects the DDname, that the error occurred on. The profile dataset cannot be updated

User response: Determine the reason for the I/O error. Possibly copy the profile dataset to a different volume. If the error persists contact BMC Software customer support.

I/O ERROR UPDATING PROFILE - XXXXXXXX

Explanation: During profile update a write operation to a variable profile pool dataset failed. The dataset can not be initialized. The message indicates the DDname, that the operation was attempted on. The variable will not be rewritten to disk.

User response: Determine the nature of the I/O error and correct.

I/O ERROR UPDATING PROFILE - XXXXXXXX

Explanation: The profile dataset update routine detected an error trying to rewrite a variables contents to disk. The message reflects the DDname, that the error occurred on. The profile dataset cannot be updated

User response: Determine the reason for the I/O error. Possibly copy the profile dataset to a different volume. If the error persists contact BMC Software customer support.

COULD NOT OPEN xxxxxxxx DD STATEMENT

Explanation: The DD statement xxxxxxxx could not be found in the SSJCL. Initialization is terminated.

User response: Ensure that the xxxxxxxx DD statement points to the correct parmlib dataset in the SSJCL.

INVALID VARIABLE FOUND IN BBIVARS - RESET

Explanation: While loading the profile pool from disk an invalid variable was detected. The loading of this variable is skipped. Initialization continues. The contents of the variable are lost.

User response: Ensure that the dataset was not somehow manually edited or shared among BBI-SSs.

PROFILE POOL DATASET USAGE > nn

Explanation: While either loading the profile pool from disk during initialization or writing a new profile variable to disk, it was discovered that the high watermark usage of the dataset exceeded nn percent of its capacity. The percentage value, nn is specified by the PROFUSED parameter in BBPARM member BBISSPxx.  The default percentage is 85. PAS initialization or VPUT processing continues

User response: It is recommended that before the next PAS restart the user run the Profile Pool Expansion utility to allocate and copy all profile variables to a larger dataset.  Please refer to the sample JCL provided in BBSAMP member XTJCL.

INITIALIZING THE PROFILE DATASET - XXXXXXXX

Explanation: A variable profile dataset was specified which was not initialized. The system will automatically format this dataset. The profile pool will then be empty.

User response: No action is required.

ABOUT TO INITIALIZE PROFILE DATASET

Explanation: During startup the BBI-SS recognized a BBIVARS dataset with invalid formatting. An operator reply is required to reformat the dataset. The message is followed by WTOR CS1026I.

User response: Determine the cause of the invalid formatting. If the dataset was never formatted this message is normal.

REPLY "U" TO CONTINUE OR "A" TO ABORT

Explanation: During startup the BBI-SS recognized a BBIVARS dataset with invalid formatting. An operator reply is required to reformat the dataset. If the abort option is chosen the profile variable dataset will be unavailable. SS startup will continue.

User response: Determine the cause of the invalid formatting. If the dataset was never formatted this message is normal.

WARNING: PROFILE DATASET WILL BE UNAVAILABLE

Explanation: During startup the BBI-SS recognized a BBIVARS dataset with invalid formatting. The operator was prompted with the following: CS1026I REPLY "U" TO CONTINUE OR "A" TO ABORT The response was A, to abort the reformat. The PAS will continue to initialize, but BMC AMI Ops Automation PROFILE variables will not be available.  It is recommended to stop the PAS and to restart with a valid dataset, or respond U to reformat a new dataset allowing access to PROFILE variables.

User response: Determine the cause of the invalid formatting and correct the issue. Stop and restart the PAS with a valid dataset, and respond U to reformat if required.

NULL OR BLANK RESPONSE RECEIVED.  PROFILE VARIABLES WILL NOT BE AVAILABLE

INVALID RESPONSE - x - RECEIVED.  PROFILE VARIABLES WILL NOT BE AVAILABLE

Explanation: During startup the BBI-SS recognized a BBIVARS dataset with invalid formatting. The operator was prompted with WTOR: CS1026I REPLY "U" TO CONTINUE OR "A" TO ABORT and responded with something other than U or A.

CS1027W will indicate either that a null or blank response was provided, or the response was a character other than a U or A. When it is a character other than U or A, the character response will be displayed within the message text. When any response other than U to reformat is provided, the dataset will not be initialized and BMC AMI Ops Automation will be started with no access to PROFILE variables.  This may impact automation that depends upon PROFILE variables.

User response: Determine the cause of the invalid response.  You will need to stop and restart the PAS with either a pre-existing BBIVARS dataset, or respond U when prompted to have a new dataset initialized.

ABEND IN CSPARMx, CHECK LOGREC

Explanation: An abend occurred while attempting to read a parmlib member or a member of the SYSPROC concatenation. The subsystem will continue to process, but errors may occur based upon what caused the abend.

User response: Diagnose and resolve the abend. Check LOGREC for the abend code and/or check to see if any dumps were produced.

(variable data)

Explanation: The SYNAD exit was driven when attempting to save the contents of the profile variable pool. It is accompanied by message CS1018E. It provides further useful information to further diagnose the cause of the problem. The subsystem will continue to shut down but the profile variable pool has most likely been corrupted.

User response: Diagnose and resolve the original problem. This situation is easily caused by allocating the BBIVARS dataset with SHR and either sharing it with another SS or otherwise writing into it.

CS1034W Unable to locate SSD for member mmmmmmmm

Explanation: While attempting to read member from the BBIPARM dataset a major control block (SSD) could not be located. There should be no impact on processing, however some "DISPLAY BBIPARM" commands might not display member mmmmmmmm correctly. Processing continues normally. Member "mmmmmmmm" might not be displayed correctly in some BBI Control Commands.

User response: Contact BMC Software Customer Support.

--- CSGSFX beginning  processing of xxxxxxxx for yyyyyyyy

Explanation: Module yyyyyyyy called CSGSFX to read member xxxxxxxx. This message was displayed because member xxxxxxxx contains a "PROCESS LIST=Y" statement. Processing continues

User response: No action is required.

--- CSPARM beginning  processing of xxxxxxxx for yyyyyyyy

Explanation: Module yyyyyyyy called CSPARM to read member xxxxxxxx. This message was displayed because member xxxxxxxx contains a "PROCESS LIST=Y" statement. Processing continues

User response: No action is required.

(PARAMETER STATEMENT)

Explanation: LIST=YES was specified on the PROCESS statement in the member identified by message CS1041I. LIST=YES indicates that this message (CS1042I) should be produced for each statement in the parameter library member. The parameter library statement is displayed as read (prior to symbol substitution).

User response: No action is required.

SYNAD EXIT DRIVEN DURING .E B SYSPROC

Explanation: While BMC AMI Ops Automation was processing a BBI Control Command to reset the BLDL table for SYSPROC, an I/O error occurred and the SYNAD exit was driven.  This error may result in the inability to schedule any EXECs or use the BMC AMI Ops Automation EXEC Manager application until the errors are resolved.

This error message is followed by CS1060E which contains detailed information about the error. The READ fails and there is failure to correctly build the BMC AMI Ops Automation EXEC Manager table. This may result in the inability to schedule any EXECs and use the EXEC Manager application.  This failure will continue until the EXEC Manager table is rebuilt without error.

User response: Determine the reason for the I/O error. Check for any recent changes to the datasets allocated to the SYSPROC ddname concatenation in the PAS JCL.  Correct any errors and issue a .rEset Bldl SYSPROC as a BBI Control Command to rebuild the EXEC Manager table.

Depending upon the nature of the error, this may require the user to stop and restart the PAS.  A WARM START is sufficient.

SYNADAF INFO: error_information_returned_by_synadaf_macro

Explanation: While BMC AMI Ops Automation was processing a BBI Control Command to reset the BLDL table for SYSPROC, an I/O error occurred and the SYNAD exit was driven. This message follows CS1059E and provides detailed information about the error.  The variable data within this message is the error information returned by the SYNADAF macro.  Data is comma separated and contains the following information:

jobname,stepname,device_number,device_type,ddname,operation_attempted,error_description,actualtrackaddressandblocknumber,access_method

Some fields may contain asterisks if the system could not get the information. The READ fails and no data is returned for the member being processed. This may result in the failure to schedule EXECs in BMC AMI Ops Automation and the EXEC Manager application may contain invalid or corrupted data.

User response: Determine the cause of the I/O error and resolve those errors. Then issue the BBI Control Command .rEset Bldl SYSPROC to rebuild the EXEC Manager table.  Once the table is rebuilt EXECs can once again be scheduled in BMC AMI Ops Automation.

Depending upon the nature of the error, this may require the user to stop and restart the PAS.  A WARM START is sufficient.

SYNADAF INFO: error_information_returned_by_synadaf_macro

Explanation: While BMC AMI Ops Automation was processing a BBI Control Command to reset the BLDL table for SYSPROC, an I/O error occurred and the SYNAD exit was driven. If the dataset in error was a PDSE or USS file, SYNADAF provides additional information about the error.  This message follows CS1060E and contains the following information:

concatenation_number,ttr_token_of_member,relative_record_number,sms_return_code,sms_reason_code,sms_diagnositic_code,unix_diag_info

Some fields may contain asterisks if the system could not get the information. The READ fails and no data is returned for the member being processed. This may result in the failure to schedule EXECs in BMC AMI Ops Automation and the EXEC Manager application may contain invalid or corrupted data.

User response: Determine the cause of the I/O error and resolve those errors. Then issue the BBI Control Command .rEset Bldl SYSPROC to rebuild the EXEC Manager table.  Once the table is rebuilt EXECs can once again be scheduled in BMC AMI Ops Automation. Depending upon the nature of the error, this may require the user to stop and restart the PAS.  A WARM START is sufficient.

CS1061E

SYNADAF INFO: error_information_returned_by_synadaf_macro 

Explanation: While BMC AMI Ops Automation was processing a BBI Control Command to reset the BLDL table for SYSPROC, an I/O error occurred and the SYNAD exit was driven. If the dataset in error was a PDSE or USS file, SYNADAF provides additional information about the error.  This message follows CS1060E and contains the following information:

concatenation_number,ttr_token_of_member,relative_record_number,sms_return_code,sms_reason_code,sms_diagnositic_code,unix_diag_info

Some fields may contain asterisks if the system could not get the information. The READ fails and no data is returned for the member being processed. This may result in the failure to schedule EXECs in BMC AMI Ops Automation and the EXEC Manager application may contain invalid or corrupted data.

User response: Determine the cause of the I/O error and resolve those errors. Then issue the BBI Control Command .rEset Bldl SYSPROC to rebuild the EXEC Manager table.  Once the table is rebuilt EXECs can once again be scheduled in BMC AMI Ops Automation.

Depending upon the nature of the error, this may require the user to stop and restart the PAS.  A WARM START is sufficient.