|
|
|
The following messages are produced by the CA-GSS Common Service or the IMOD editor of the CA-GSS Common Service.
Reason:
This message serves as the label line for informational messages issued in response to operator commands.
Action:
No action is required.
Reason:
The text field in this message was the operand of a REXX SAY instruction executed in an IMOD. imodid is the IMOD task ID responsible for issuing the message text. name is the name of the IMOD routine containing the SAY statement, and stmt is the statement number of the SAY statement within the IMOD.
Note: It is possible for some internal routines and ADDRESS environments to produce SAY-type output.
Action:
Examine the message text to determine the appropriate action.
Reason:
Initialization of CA‑GSS version vv.rr has started.
Action:
No action is required.
Reason:
The load module modulename has an entry point at the indicated address.
Action:
Record the message for use by CA Support to aid in debugging.
Reason:
The command that you entered is not valid.
Action:
Check the validity of the command you entered.
Reason:
The security product running at your installation has determined that your user ID is not authorized to use the ISET that you have selected.
Action:
Contact your security administrator to request access to the data set.
Reason:
Although the ISET you selected appears on the menu, the associated data set does not exist.
Action:
Use the TOGGLE command to view the data set name associated with the ISET. Make sure that it is a valid data set and that it is cataloged.
Reason:
The ISET you selected is being updated by another user.
Action:
Wait a few seconds and try again.
Reason:
During dynamic allocation of an ISET, SVC 99 returned an error reason code of iscerr.
Action:
Examine the code to determine the appropriate action.
Reason:
The ISPF service service returned a hexadecimal error code of error at the location label.
Action:
Consult ISPF manuals. For assistance, contact CA Support at http://ca.com/support.
Reason:
An OPEN for a data set has failed. errorstring contains additional information.
Action:
Examine the error string to determine the appropriate action.
Reason:
A condition requiring a warning has been detected. warning message indicates the text of the warning.
Action:
Examine the warning message to determine the appropriate action.
Reason:
You are not authorized to update the current ISET. You may, however, read the contents.
Action:
Contact your security administrator to request access to the data set.
Reason:
You are not authorized to read from or write to the current ISET.
Action:
Contact your security administrator to request access to the data set.
Reason:
The currently accessed data set may not be updated.
Action:
If you require update access to this data set, return to the data set selection panel and select the data set with the E (edit) line command.
Reason:
The command you entered on the command line is not appropriate at this time.
Action:
Correct and reenter the command.
Reason:
The FIND command that just executed has failed.
Action:
No action is required.
Reason:
The ISET name specified by the SELECT command is invalid.
Action:
Correct the name specified by the SELECT command.
Reason:
The ISET you specified with the SELECT command is not defined.
Action:
Correct the name specified by the SELECT command.
Reason:
You have entered an invalid character in the left margin of one or more lines.
Action:
Remove the invalid characters.
Reason:
While processing the SRVPARM data set, a duplicate definition was encountered.
Action:
Correct the SRVPARM data set, removing duplications.
Reason:
The search operation that just executed was successful.
Action:
No action is required.
Reason:
The text of this message is input data read from a user-supplied file.
Action:
No action is required.
Reason:
The command you entered on the command line is not appropriate at this time.
Action:
Correct the command and retry.
Reason:
The IMOD name you specified already exists.
Action:
Choose another name for the IMOD.
Reason:
The command you entered on the command line is not appropriate at this time.
Action:
Correct the text you entered.
Reason:
The search operation that just executed has failed.
Action:
No action is required.
Reason:
The name you specified for an IMOD does not meet the required syntax rules for IMOD names.
Action:
Correct the name specified by the SELECT command.
Reason:
The IMOD you requested is currently being used by another user.
Action:
Wait a few seconds and try again.
Reason:
The LOAD command was successful. loaddata contains information about the load operation.
Action:
No action is required.
Reason:
The EXECUTE command was successful. executedata contains further information about the execution.
Action:
No action is required.
Reason:
Your attempt to execute an IMOD failed.
Action:
Examine the code to determine the appropriate action.
Reason:
Your attempt to communicate with an ISERVE address space failed for the reason indicated.
Action:
Examine the reason text to determine the appropriate action.
Reason:
Your attempt to load an IMOD into an ISERVE address space failed for the reason indicated.
Action:
Examine the reason text to determine the appropriate action.
Reason:
Your installation has restricted your access to this ISET to READ ONLY. The command you entered requires UPDATE access to the ISET.
Action:
Contact your security administrator about authorization to UPDATE.
Reason:
The input data referred to in message SRV103 does not contain a NAME field.
Action:
Add a NAME field to the input data.
Reason:
The data set is empty. You cannot browse an empty data set.
Action:
No action is required.
Reason:
The data set is in a format used by a previous version of the IMOD editor. The function you are attempting cannot use the IMOD in this format.
Action:
Edit and save the data set to update its format.
Reason:
The length of the NAME field in the input data referred to in message SRV103 is invalid.
Action:
Correct the data in the NAME field of the input data.
Reason:
The specified program is being edited by another user.
Action:
Wait a few seconds and try again.
Reason:
The system failed while the IMOD you selected was being edited or compiled. The original IMOD source was saved as tempsav.
Action:
Inspect the original IMOD for completeness. It is possible that the IMOD has been destroyed or damaged. If this is the case, delete the damaged IMOD and rename the IMOD tempsav. Otherwise, delete the IMOD tempsav.
Reason:
The temporary copy of an IMOD, tempsav, cannot be edited.
Action:
Rename tempsav, and then edit it.
Reason:
The temporary copy of an IMOD, tempsav, cannot be compiled.
Action:
Rename tempsav and then compile it.
Reason:
Your attempt to compile an IMOD failed. The source file may be damaged. The original IMOD source was saved as tempsav.
Action:
Inspect the original IMOD for completeness. It is possible that the IMOD has been destroyed or damaged. If either of these is the case, delete the damaged IMOD and rename the IMOD tempsav. Otherwise, delete the IMOD tempsav.
Reason:
During a compile, the compiler abended. reason indicates additional information. The original IMOD source was saved in a temporary file.
Action:
Inspect the original IMOD for completeness. It is possible that the IMOD has been destroyed or damaged. If either of these is the case, delete the damaged IMOD and rename the temporary IMOD. Otherwise, delete the temporary IMOD.
Reason:
You have begun an editing session on an IMOD that you may not update.
Action:
Contact your security administrator about authorization to UPDATE.
Reason:
Security restrictions imposed by your installation do not permit you to update this IMOD.
Action:
You can use the CREATE or COPY command to save this IMOD in a sequential data set. Contact your security administrator about authorization to UPDATE.
Reason:
The input data referred to in message SRV103 does not contain a DSNAME field.
Action:
Add a DSNAME field to the input data.
Reason:
This message can indicate an attempt to access a non-VSAM data set as an ISET, an improperly defined ISET, or a damaged ISET.
Action:
Check the validity of the ISET using IDCAMS (LISTCAT, REPRO). Check the key length, and so on, against the requirements for an ISET. For assistance, contact CA Support at http://ca.com/support.
Reason:
This message indicates that the requested rename has failed. The original IMOD is unchanged. xxyy is the return and reason code set by the VSAM POINT operation.
Action:
Check the validity of the ISET using IDCAMS (LISTCAT, REPRO). Check the key length, and so on, against the requirements for an ISET. For assistance, contact CA Support at http://ca.com/support.
Instead of renaming the IMOD, copy the text to a new IMOD and then delete the old IMOD.
Reason:
The length of the DSNAME field in the input data referred to in message SRV103 is invalid.
Action:
Correct the data set name in the DSNAME field of the input data.
Reason:
The VSAM KSDS containing the ISET does not meet the standards required by ISERVE.
Action:
Make sure that the data set is an IMOD file. Reallocate or use the IDCAMS MODIFY CLUSTER function to make sure that the data set conforms to ISET requirements.
Reason:
The ISET you have accessed has been initialized for IMODs.
Action:
No action is required.
Reason:
The ISET you have selected is a newly allocated VSAM KSDS. It could not be successfully prepared for use as an IMOD file.
Action:
Delete and reallocate the IMOD file. Refer to the Administration Guide for more information.
Reason:
You have accessed an ISET that contains no IMODs. Because you do not have UPDATE access, you cannot alter this ISET.
Action:
No action is required.
Reason:
During initialization or execution of the RELOAD command, an existing copy of controlblock was encountered at address, occupying nnnn bytes of storage. controlblock is freed.
Action:
No action is required.
Reason:
One or more margin fields contain invalid command characters.
Action:
Remove the incorrect character from the margin areas.
Reason:
The SRVCOMP module could not be loaded from the SRVLLIB DD statement. Compile operations are not possible.
Action:
Make sure that SRVCOMP is accessible through the SRVLLIB DD statement.
Reason:
The control block’s identifier characters are missing or invalid. controlblock was not deleted.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
controlblock was not deleted because FREEMAIN returned the nonzero completion code rtc.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The ISET name indicated by isetname has already been specified in your startup parameters. ISET names must be unique.
Action:
Make sure that ISET names are valid and unique.
Reason:
The ECSA routine was loaded at address and occupied nnnn bytes of storage.
Action:
No action is required.
Reason:
An attempt to release an old ECSA buffer pool is being made. The buffer pool is located at address, occupying nnnnnn bytes of storage.
Action:
No action is required.
Reason:
The subsystem buffer pool was not freed from ECSA because it was in an unknown storage subpool or unallocated storage. VSMLOC returned the nonzero completion code rtc.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The subsystem buffer pool was not freed from ECSA because the block identifier characters were missing or invalid.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The subsystem buffer pool was not freed from ECSA because FREEMAIN returned the nonzero completion code rtc.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
A new subsystem buffer pool has been allocated in ECSA at address. The area occupies nnnn bytes of storage, and mmmm buffers were allocated.
Action:
No action is required.
Reason:
The ECSA buffers could not be allocated because GETMAIN returned the nonzero completion code rtc. CA‑GSS terminates.
Action:
Determine the cause of the failure from the completion code, correct the error, and restart CA‑GSS.
Reason:
The Subsystem Control Vector Table for subsystem ID ssid exists at address.
Action:
No action is required.
Reason:
The Subsystem Vector Table for subsystem ID ssid exists at address.
Action:
No action is required.
Reason:
The Subsystem Vector Table for subsystem ID ssid was allocated at address.
Action:
No action is required.
Reason:
The CA-GSS ECSA common control block already exists at address.
Action:
No action is required.
Reason:
A new ECSA common control block was allocated at address. It occupies nnnnnn bytes of storage.
Action:
No action is required.
Reason:
An existing SUBCOM is invalid. It is not freed and will not be used.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The JES Control Table has an invalid format. CA‑GSS terminates.
Action:
Notify your systems programmer; contact CA Support if necessary.
Reason:
A Subsystem Control Vector Table (SSCVT) has an invalid format. CA‑GSS terminates.
Action:
Notify your systems programmer. For assistance, contact CA Support at http://ca.com/support.
Reason:
A Subsystem Control Vector Table (SSCVT) does not exist for subsystem ID ssid, and the operator did not reply Y (yes) to a request to create one. CA‑GSS terminates.
Action:
Restart CA‑GSS, and when message SRV146 is displayed, reply Y.
Reason:
During loading, an invalid record was encountered in the IMOD imodname residing in the file with ISET name iset and data set name dsname. The IMOD is not loaded.
Action:
Correct the invalid record, and compile and load the IMOD again.
Reason:
The IMOD imodname has been loaded from the library libname. The IMOD’s memory address memaddress is also displayed.
Action:
No action is required.
Reason:
While loading the IMOD imodname from the data set dsname, an invalid record was found. The IMOD is not loaded.
Action:
Correct the invalid record, and compile and load the IMOD again.
Reason:
While loading the IMOD imodname, a #SOURCE compiler directive was noted. The IMOD’s source code was also loaded and is available for debugging.
Action:
If source code is not required for this IMOD, remove the #SOURCE compiler directive to conserve memory.
Reason:
The IMOD imodname is being loaded.
Action:
No action is required.
Reason:
While loading IMOD imodname, a mismatch was found between the level of the compiled object code and the level of the REXX interpreter being used by ISERVE. vv.rr.mm indicated the version and release of the compiler last used to compile the IMOD. Only vv.rr is significant.
Action:
ISERVE will attempt to recompile the IMOD dynamically. Recompile the IMOD in the ISET to speed ISERVE initialization.
Reason:
An IMOD has begun execution.
Displays the unique ID assigned to the IMOD and is used to identify other messages.
Identifies the REXX program invoked initially.
Action:
No action is required.
Reason:
The address of the Process Control Block belonging to an IMOD is displayed.
Action:
No action is required. This information is for use by CA Support for system debugging.
Reason:
At the conclusion of the IMOD imodname, the number of bytes of storage required (aaaaaaaa), storage released (bbbb), and storage kept (cccccccc) for variables is displayed.
Action:
No action is required.
Reason:
Following execution of an IMOD, not all variable storage was released. The amount of storage permanently allocated is nnnnnnnn bytes.
Action:
No action is required.
Reason:
The IMOD imodname has concluded for program pgmname. icnt indicates the number of REXX statements executed.
Action:
No action is required.
Reason:
ISERVE could not load the source code for IMOD imodname. This usually indicates that the IMOD was compiled with a previous version of the IMOD editor.
Action:
Use the ISPF‑based IMOD editor to edit, save, and compile the IMOD.
Reason:
The ISERVE REXX compiler module SRVCOMP has been loaded into memory at address. The version loaded is vv.rr.mm. vv.rr should match the value indicated for ISERVE.
Action:
No action is required.
Reason:
The IMOD imodname has resumed execution following a suspension.
Action:
No action is required. This information is for use by CA Support for internal debugging.
Reason:
Error errcd occurred during the execution of the IMOD imodname in the program pgmname.
Action:
This message is followed by message SRV182. Correct any errors in the REXX program statement displayed in that message.
Reason:
This message follows message SRV181, and provides the number of the failing REXX statement (nnnnn) and the REXX error text (errtext).
Action:
Correct any errors in the REXX statement displayed.
Reason:
CA-GSS allocated the subsystem console ID consid.
Action:
No action is required.
Reason:
While attempting to recompile IMOD imodname, ISERVE was unable to obtain a copy of the compiler SRVCOMP. The IMOD is flagged as unusable and execution continues.
Action:
Make sure that the compiler module is accessible to ISERVE through STEPLIB or LNKLIST. Also make sure that the named IMOD has been compiled under the current version of the compiler.
Reason:
While attempting to recompile imodname, the compiler abended. No further attempt will be made to recompile IMODs.
Action:
Recompile the indicated IMOD from the IMOD panel. Gather dumps and diagnostics, and then call CA Support.
Reason:
An attempt was made to load IMOD imodname from the library libname, but it was an incomplete IMOD.
Action:
Compile the IMOD again.
Reason:
An attempt was made to load the IMOD imodname from the library libname, but it was not compiled.
Action:
Compile the IMOD before attempting to load it.
Reason:
An attempt was made to load the IMOD imodname from the library libname, but it contains compile time errors.
Action:
The IMOD contains invalid REXX statements. Correct them and compile the IMOD again.
Reason:
An attempt was made to load the IMOD imodname from the library libname, but it has test status only.
Action:
Give the IMOD production status before attempting to load it again.
Reason:
An attempt was made to load the IMOD imodname from the library libname, but it did not have production status.
Action:
Give the IMOD production status before attempting to load it again.
Reason:
Execution of the IMOD imodname has been suspended pending the completion of event.
Action:
Record the message for use by CA Support to aid in debugging.
Reason:
Dynamic allocation failed for reason rsncd.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
Data set dsname is required for dynamic IMOD loading, but it could not be found.
Action:
Make sure that the data set exists and is cataloged.
Reason:
Data set dsname is required for dynamic IMOD loading, but it is in use by another task.
Action:
Try again when the data set is available.
Reason:
Data set dsname is required for dynamic IMOD loading, but it could not be allocated. The most likely reason is security system denial.
Action:
Authorize the data set to have access to CA‑GSS.
Reason:
During dynamic IMOD reloading, data set dsname did not contain the IMOD imodname in usable form.
Action:
No action is required.
Reason:
The ILOG file ddname is now being recorded on.
Action:
No action is required.
Reason:
The ILOG file ddname is now full.
Action:
Dump the data from the file or reset the file.
Reason:
All ILOG data sets for the file number nn are full. Records to be recorded on this file are being discarded.
Action:
Dump the data from the file or reset the file.
Reason:
Due to an execution error of the IMOD or in response to a CANCEL IMOD operator command, the IMOD identified by imodid has been canceled.
Action:
If the cancellation was due to a run-time error in the IMOD, you should correct the logic and recompile the IMOD.
Reason:
While loading the object code for IMOD imodname, ISERVE determined that the object code’s version is incompatible with its REXX interpreter. The IMOD was dynamically recompiled and is available for use.
Action:
To speed ISERVE initialization, recompile the IMOD.
Reason:
While loading the object code for IMOD imodname, ISERVE determined that the object code’s version is incompatible with its REXX interpreter. The IMOD was dynamically recompiled but a compile-time error occurred. The IMOD could not be made available for use.
Action:
Edit the IMOD to correct the error, and then recompile it.
Reason:
The IMOD identified by imodid has issued an external subroutine call to imodname.
Action:
No action is required. This message is useful in determining the failing routine if an error occurs.
Reason:
Dynamic allocation failed for the data set dsname.
Action:
Before retrying the failed operation, make sure that the data set:
Reason:
The OS LOAD issued for SRVCOMP has failed. Automatic compilation of IMODs is not possible.
Action:
Check for the availability of the SRVCOMP load module.
Reason:
ISERVE received a STOP command and is shutting down. consid identifies the operator console where the command was issued.
Action:
No action is required.
Reason:
During initialization, an enqueue on subsystem ID SYSTEM could not be obtained. CA‑GSS will wait on the resource.
Action:
Terminate the CA‑GSS system that is using the subsystem ID.
Reason:
CA-GSS has successfully initialized for version vv.rr and subsystem name ssid.
Action:
No action is required.
Reason:
The option you have requested is not valid.
Action:
Correct the control card.
Reason:
An OPEN failed for the data set dsname. The IMOD was not loaded.
Action:
Determine the reason for the failure from the accompanying messages.
Reason:
An error occurred while allocating a data set.
Action:
Analyze the data returned by SVC 99. Information on SVC 99 can be found in the IBM manual System Macros and Facilities Volume 1, GC28‑1150.
Reason:
During ILOG switch processing, the ILOG you requested could not be put in UPDATE mode. This is probably because another task has update access.
Action:
Do not permit other tasks to have update access to ILOG data sets.
Reason:
The CA‑GSS PARMLIB file could not be opened. CA‑GSS terminates.
Action:
Provide a PARMLIB file and restart CA‑GSS. For more information on the PARMLIB file, refer to the Installation Guide.
Reason:
CA-GSS is processing the PARMLIB file.
Action:
No action is required.
Reason:
The verb parmlib_verb in the CA‑GSS PARMLIB is invalid.
Action:
Correct the invalid verb in the CA‑GSS PARMLIB file. For more information on PARMLIB parameters, refer to the Installation Guide.
Reason:
The subsystem ID parmlib_ssid is invalid.
Action:
Correct the subsystem name in the CA‑GSS PARMLIB file. For more information on PARMLIB parameters, refer to the Installation Guide.
Reason:
The PARMLIB statement previously displayed has unnecessary text.
Action:
Shorten the text that is too long. If you want to include comments in the PARMLIB file, separate them from the last operand with a slash and asterisk (/*).
Reason:
The PARMLIB parameter parmlib_parm is required but you did not provide it.
Action:
Specify a value for parmlib_parm in the CA‑GSS PARMLIB file. For more information on PARMLIB parameters, refer to the Installation Guide.
Reason:
CA-GSS initialization has failed. Previously issued messages indicate the reason.
Action:
Correct the indicated errors and restart CA‑GSS.
Reason:
The PARMLIB option parmlib_option in the PARMLIB file is invalid.
Action:
Correct the invalid option in the CA‑GSS PARMLIB file. For more information on PARMLIB parameters, refer to the Installation Guide.
Reason:
The PARMLIB value parmlib_value is invalid.
Action:
Correct the parameter value in the CA‑GSS PARMLIB file.
Reason:
You have specified too many operator commands in the CA‑GSS PARMLIB file.
Action:
Reduce the number of operator commands in the PARMLIB file.
Reason:
The IMOD imodname was requested for execution, but it was not found in memory.
Action:
Make sure that the IMODs you want to execute are available and loaded.
Reason:
The IMOD imodname was requested for execution, but it was not active.
Action:
Activate the IMOD or load it again.
Reason:
The IMOD imodname has abended. The name of the REXX program (pgmname) and nesting level (level) are displayed. This message indicates that a diagnostic dump was produced, according to the parameters specified in the CA‑GSS PARMLIB file.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
This message contains two lines. The IMOD imodname and REXX program pgmname have altered memory through the MEMORY( ) function. Also displayed are the ASID asid, storage protect key pk, and storage location address.
Action:
No action is required.
Reason:
An entry in the CA‑GSS PARMLIB file does not contain all of the required information.
Action:
Correct the entry and restart CA‑GSS. Refer to the Installation Guide for more information on the PARMLIB file.
Reason:
WTO entries (including control information) in the CA‑GSS PARMLIB file exceed the 4K maximum limit.
Action:
Reduce the number of WTO entries. For more information on the PARMLIB file, refer to the Installation Guide.
Reason:
A multi-line WTO has been queued for processing for four minutes, but the last line of the WTO has not been produced by MVS. The WTO will be considered complete and processed as is.
Action:
No action is required.
Reason:
The CA‑GSS CSECT csect has abended with the error code errcd. This message is accompanied by messages SRV260‑SRV266.
Action:
Record the information provided in the accompanying messages. For assistance, contact CA Support at http://ca.com/support.
Reason:
Following the abend of the CA‑GSS CSECT named in message SRV259, the PSW xxxxxxxx xxxxxxxx and program entry point yyyyyyyy are displayed.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
Following the abend of the CA‑GSS CSECT named in message SRV259, the register number regnum and registers (reg1 to reg4) are displayed. This message appears four times to cover all 16 registers.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
Accompanies message SRV259. Following the abend of the CA‑GSS CSECT csect, a retry routine at location address will receive control.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
Following the abend of the CA‑GSS CSECT named in message SRV259, no retry routine was available, or all retries were exhausted. CA‑GSS terminates.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
Following the abend of the CA‑GSS CSECT named in message SRV259, the ECSA common block was found to be corrupted. CA‑GSS terminates.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
Following the abend of the CA‑GSS CSECT named in message SRV259, the ECSA common block was found to be corrupted. CA‑GSS terminates.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
CA-GSS terminated during abend processing for the CA‑GSS CSECT named in message SRV259.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
These messages contain information to aid CA Support in debugging.
Action:
To suppress these messages, add the statement PRINT TRACE OFF to your CA‑GSS PARMLIB file. For more information on the PARMLIB file, refer to the Installation Guide.
Reason:
An error occurred while attempting to dynamically allocate subsystem ID ssid. CA‑GSS terminates.
Action:
Pre-allocate ar CA‑GSS subsystem.
Reason:
The load module modulename has been loaded into memory at address. It occupies nnnn bytes of storage.
Action:
No action is required.
Reason:
The load module modulename could not be loaded into memory. LOAD returned the return code rtc and reason rsncd.
Action:
Analyze the return code and reason to determine the problem. rtc is the abend code and rsncd is the associated reason code, as explained in the IBM manual System Codes.
Reason:
The load module modulename was loaded into memory. However, APF authorization has been lost. CA‑GSS continues execution, but abends will occur if authorized services are required.
Action:
Make sure that all required modules are APF authorized.
Reason:
This message accompanies other messages and identifies the IMOD and the statement number.
Action:
No action is required.
Reason:
An external function call has been made for IMOD imodname, but it could not be found. The IMOD ID imodid, calling program pgmname, and statement number nnnnn are displayed.
Action:
No action is required.
Reason:
An external function call has been made for IMOD imodname, but it is not flagged as callable. The IMOD ID imodid, calling program pgmname, and statement number nnnnn are displayed.
Action:
Add a #CALLABLE directive to the IMOD.
Reason:
An external function call has been made, but it will cause the maximum nesting level to be exceeded.
Displays the IMOD ID.
Identifies the calling program.
Displays the statement number.
Action:
Reduce the level of subroutine nesting.
Reason:
An execution time REXX error has occurred. The IMOD name, the EXEC name, and the REXX error message are displayed.
Action:
Correct the error based upon information from the message.
Reason:
Following completion of a REXX program, a result was returned. This message displays the IMOD name, EXEC name, and the data returned.
Action:
No action is required. To suppress this message, add the statement PRINT RESULT OFF to the CA‑GSS PARMLIB file. For more information on the PARMLIB file, refer to the Installation Guide.
Reason:
During initialization, the IMOD imodname was found to be loaded already. It is not replaced.
Action:
Eliminate duplicate IMODs.
Reason:
Due to a dynamic reload request, the IMOD imodname is being replaced by a copy from the library libname.
Action:
No action is required.
Reason:
A message line (WTO, command, or external program request) could not be processed because of a lack of storage.
Action:
Check for other error conditions and increase the amount of virtual storage available to CA‑GSS.
Reason:
An IMOD file is being processed at initialization. The ddname and version of the IMOD file are displayed.
Action:
No action is required.
Reason:
An external function call has been made for an IMOD that has been flagged as not active.
Displays the IMOD ID.
Identifies the calling program.
Displays the statement number.
Action:
Activate the IMOD.
Reason:
The IMOD imodname has been deleted from storage at address. Typically, this indicates that the entry has been replaced with a more current copy, and unneeded storage is being released.
Action:
No action is required.
Reason:
The IMOD imodname at location address could not be deleted because the code to be replaced is still being executed. CA‑GSS will automatically try to delete the IMOD when its use count reaches zero.
Action:
No action is required.
Reason:
The maximum number of occurrences allowed for a CA‑GSS installation parameter was exceeded.
Action:
Delete the excess initialization parameters from the CA‑GSS RUNPARM member. (This member is pointed to by the CA‑GSS PARMLIB DD statement.)
Reason:
You have specified an invalid ILOG file number.
Action:
Specify an ILOG file number from 0 through 99, inclusive.
Reason:
You have specified an invalid ILOG subfile number.
Action:
Specify an ILOG subfile number from 0 through 9, inclusive.
Reason:
You have specified an invalid data set name for an ILOG file.
Action:
Specify a valid data set name.
Reason:
The ILOG file and subfile you are attempting to define duplicate one already defined.
Action:
Define a unique ILOG file and subfile.
Reason:
Dynamic allocation failed for the ILOG file and subfile that you are trying to define.
Action:
Correct your definition; or, make sure that the data set exists, is cataloged, is on a mounted volume, and is accessible to ISERVE before retrying the failed operation.
Reason:
During error recovery processing, it was determined that the error occurred while imodname was executing stmtnum.
Action:
Recovery continues. Obtain a copy of the indicated IMOD’s listing, showing the indicated statement. For assistance, contact CA Support at http://ca.com/support.
Reason:
During abend termination or during a restart following abend termination, ISERVE determined that cross-memory requestors are waiting for IMOD completion. These users are now being notified of the abend termination. ascb, tcb, and ecb indicate the addresses of the control blocks used for notification.
Action:
No action is required.
Reason:
During the execution of the IMOD caller, at statement stmtnum, an external subroutine call was made to imodname. However, the requested IMOD was unavailable.
Action:
Review the affected IMOD’s subroutine logic and the availability of the called IMOD.
Reason:
ISERVE has issued a LOAD SVC for its REXX compiler (SRVCOMP). However, the fetched module’s version does not match the ISERVE version.
Action:
Make sure that all CA‑GSS components are being fetched from the same library and that the library was properly constructed by the installation process.
Reason:
During initialization of ilog, subfile, it was discovered that portions of the file are now inaccessible due to a decrease in the value specified by the PAGES initialization parameter. The affected ILOG file is reinitialized, using the new PAGES value.
Action:
No action is required.
Reason:
The ISERVE log (ISRVLOG) has been closed and the associated SYSOUT data set spun off. A new SYSOUT data set has been allocated to ddname filename. All future log information is recorded on this data set.
Action:
No action is required.
Reason:
While accessing an ILOG (Data In Virtual) file, an error was encountered. nn is the ILOG number and m is the subfile number. service refers to the Data In Virtual request that failed, and return and reason are the codes returned by the failing service.
Action:
No action is required.
Reason:
There is not enough virtual storage to map the file with ILOG number nn and subfile number m.
Action:
Do one of the following:
Reason:
The named load module has been successfully loaded by CA‑GSS/ISERVE and is available for appropriate use. length is the length of the module, in hexadecimal format.
Action:
No action is required.
Reason:
At startup, while ISERVE was loading IMODs from an ISET, it encountered an IMOD with the same name as an internal IMOD. Loading of this IMOD is suppressed.
Action:
Make sure that the names of your IMODs do not duplicate those of internal IMODs.
Reason:
The indicated IMOD, internal to SRVSYS, has been replaced with an IMOD of the same name.
Action:
Verify that this replacement was intentional.
Reason:
A file has been allocated by the IMOD task identified by taskid. ddname is the assigned DDNAME and dsname identifies the data set. disp indicates how the file was allocated: SHR, OLD, NEW, or MOD. FREE=CLOSE indicates that the data set will be de-allocated immediately upon its being closed.
Action:
No action is required.
Reason:
The file assigned to ddname has been de-allocated. taskid identifies the IMOD task that deallocated the file.
Action:
No action is required.
Reason:
As the result of a GLOBVAL initialization parameter, an initial value has been assigned to a global variable.
Action:
No action is required.
Reason:
The parameter list passed to the SRVIMOD program is not valid.
Action:
Verify the construction of the parameter list, reassemble and reexecute your program.
Reason:
RACROUTE has failed a request for userid. taskid identifies the IMOD task in control at the time. rc1 is the return code from RACROUTE. rc2 and rc3 are the return codes from the first 8 bytes of the RACROUT parameter list.
Action:
Verify that no breach of security occurred on your system. The indicated IMOD task will continue under the authority of the default user ID.
Reason:
A new ACEE (if SECURITY RACF was specified in the initialization parameters) or pseudo ACEE (if SECURITY NONE was specified) has been obtained for userid. This control block now resides at address. The taskid identifies the IMOD task in control when the block was obtained. In the message text, block will indicate either ACEE or Pseudo ACEE.
Action:
No action is required.
Reason:
No valid user ID was associated with the IMOD task identified by taskid. Therefore, this IMOD task will process under the authority of the default user ID, as specified in the initialization parameters. In the message text, block will either be ACEE, if SECURITY RACF was specified in the initialization parameters; or Pseudo ACEE, if SECURITY NONE was specified.
Action:
Make sure that all tasks that request execution of IMODs are assigned valid user IDs.
Reason:
The specified IMOD, called as an external subroutine, has completed.
Action:
If you do not need this information for debugging, use the PRINT SUBCALL OFF initialization parameter or TRACE SUBCALL OFF operator command.
Reason:
A GLOBVAL initialization statement has attempted to assign a value to name. However, name is not a valid global variable.
Action:
Make sure that you are specifying a correct global variable name.
Reason:
The IMOD task identified by imodid is waiting on a system enqueue.
Action:
No action is required.
Reason:
The number specified for pages on the preceding ILOG control statement is invalid.
Action:
Specify a valid number for pages.
Reason:
The resource identified by enqname is required for processing to continue. This message will be deleted when the resource becomes available.
Action:
Make sure that the resource is not being held unnecessarily.
Reason:
The GSSLOAD load module has successfully initialized the Global SubSystem areas in ECSA.
Action:
No action is required.
Reason:
The GSSLOAD load module was unsuccessful in freeing an ECSA area that is no longer needed.
Displays the failure code returned by FREEMAIN.
Displays the subpool number of the storage.
Indicates the length to be freed.
Displays the virtual address of the storage.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The GSSLOAD load module has successfully freed unneeded ECSA storage.
Identifies the type of control block being released and is only of interest to CA personnel.
Displays the virtual address of the storage.
Displays the subpool number of the storage.
Indicates the length to be freed.
Action:
No action is required.
Reason:
The GSSLOAD load module was unsuccessful in obtaining ECSA storage for a control block. If this is a LOAD operation, the Global SubSystem will not be usable. If this is a RELOAD operation, the previously initialized Global SubSystem may still be usable.
Displays the failure code returned by GETMAIN.
Displays the subpool number of the storage request.
Displays the length of storage requested.
Action:
Determine why GSSLOAD was unable to obtain the requested storage and fix the problem. Execute the GSSLOAD program, specifying a PARM of RELOAD.
Reason:
The GSSLOAD load module was unsuccessful in loading the named control block. This message will be preceded by a message that will identify the problem encountered. The name of the control block is of interest only to CA personnel.
Action:
Proceed as directed by previously issued error messages.
Reason:
The GSSLOAD load module has placed the indicated executable code or control block in ECSA.
Displays the name of the routine or control block.
Displays the identifier assigned to the storage.
Displays the address of the entry point.
Displays the length of the ECSA area used.
Action:
No action is required.
Reason:
In response to a TSO user’s request to execute an IMOD in test mode, the IMOD Test Facility is routing the request to the appropriate GoalNet node.
Action:
No action is required.
Reason:
In response to a TSO user’s request to execute an IMOD in test mode, the IMOD Test Facility is passing control to the IMOD to be tested.
Action:
No action is required.
Reason:
Following execution in test mode, an IMOD has completed and has returned control to the IMOD Test Facility, which will report the results to the requesting TSO user.
Action:
No action is required.
Reason:
If you are running under a security system (RACF or SAF-compatible), ISERVE will execute the initialization IMODs (those IMODs automatically scheduled during ISERVE initialization) under the authority of userid.
Action:
No action is required.
Reason:
A logon request has been successfully processed by the SECURITY() function. IMOD task taskid is now executing under the authority of userid.
Action:
No action is required.
Reason:
During execution of the SRVCCAT or SRVDCAT TSO command processor, a dynamic concatenation or deconcatenation error occurred.
Displays the error value returned by SVC99.
Displays the information value returned by SVC 99.
Action:
Determine the appropriate action by examining the error and information codes.
Reason:
This message is issued from SRVCCAT and SRVDCAT. Depending upon the format, either parameter number n, as specified with the command, is invalid; or you have specified more parameters than are permitted.
Action:
Correct the error in the parameter list and retry the command.
Reason:
This message is issued from SRVMAINT when an enqueue for a needed IMOD cannot immediately be satisfied. This may be caused by another job running SRVMAINT simultaneously, or by a TSO user who is editing the named IMOD. The enqueue qname is IPGMGREX and the rname is P.name.dsname where name is right-padded with blanks to 16 characters and dsname is right-padded with blanks to 44 characters. This message will automatically be deleted when the IMOD becomes available.
Action:
Determine who holds the enqueue and have them release it, cancel the SRVMAINT job that requires the IMOD, or allow the SRVMAINT job to wait until the IMOD becomes available.
Reason:
The data set specified by the PARMLIB DD statement cannot be processed. In the message, value is the attribute that is causing the problem.
Action:
Reconstruct the PARMLIB data set ensuring that all data set attributes conform to those defined in the installation manual.
Reason:
Either the member specified in the EXEC card PARM field or a member specified on an INCLUDE statement could not be found in the PARMLIB data set.
Action:
Ensure that the member name is spelled correctly and that it exists in the PARMLIB data set.
Reason:
Although the PARMLIB DD statement points to a sequential file, you attempted to specify a member, either in the EXEC card PARM field or by coding an INCLUDE statement.
Action:
Either remove the member specification or change the PARMLIB DD statement to specify a PDS. Note that a specification of xxx.yyy.xxx(member) is for a sequential file, NOT a PDS.
Reason:
An INCLUDE statement specifies a member that is in the nesting sequence already being processed.
Action:
Remove the reference to the already-processed member.
Reason:
The member specified in the EXEC card PARM statement or in an INCLUDE statement cannot be used because it is invalid.
Action:
Examine the member name and correct it.
Reason:
The messages that follow will pertain to parameter statements taken from the named member.
Action:
No action is required.
Reason:
The member named in an INCLUDE statement has been completely processed and additional parameters will be taken from the member that was suspended to perform the INCLUDE. The messages that follow will pertain to parameter statements taken from the named member.
Action:
No action is required.
Reason:
The PARMLIB DD statement is coded as DD DUMMY. This is not permitted.
Action:
Either change the PARMLIB DD statement to specify a data set or delete the DD statement.
Reason:
A module produced by the IMOD Packaging Facility does not contain an IMODNAME CSECT. Execution is not possible.
Action:
Repackage the IMODs, ensuring that an IMODNAME CSECT is produced and link-edited.
Reason:
The IMOD Packaging Facility permits the inclusion of initialization parameters in the load module. The messages that follow will pertain to parameter statements taken from the link-edited parameters.
Action:
No action is required.
Reason:
While processing initialization parameters, it was determined that the parameter just listed in the log was not intended for use by this copy of CA‑GSS/ISERVE. The reason is because the value specified for xxxxx did not match the corresponding value as defined on this system for this ISERVE. Processing continues with the next parameter.
Action:
No action is required.
Reason:
During start-up CA-GSS discovered that it was running from a non-APF authorized library (LINKLIST or STEPLIB) and it terminated with User abend U0071.
Action:
Make sure CA-GSS's load library is correctly APF-authorized.
Reason:
CA-GSS was unable to load necessary routines into ECSA. GSSMAIN terminates.
Action:
Make sure that the GSSLOAD load module is in an APF-authorized LINKLIB accessible to GSSMAIN. Make sure that ECSA space is available.
Reason:
GSSMAIN is already executing in another address space. This copy of GSSMAIN terminates.
Action:
Determine which address space is already executing GSSMAIN and stop it if appropriate. Execute SRVSYS to start a secondary ISERVE.
Reason:
GSSMAIN is serializing use of ECSA data area with other callers of the GSSLOAD load module. This message is nonrollable until the enqueue is obtained.
Action:
If this message is not deleted within a few minutes, determine who holds the enqueue on qname: GOALSS, rname: SSCVT. If the enqueue-holding address space is not responsive, it should be canceled and restarted.
Reason:
GSSMAIN was not able to access CA‑GSS services. GSSMAIN terminates.
Action:
For assistance, contact CA Support at http://ca.com/support. It may be useful to execute the GSSLOAD utility, specifying the RELOAD parameter before attempting to restart GSSMAIN.
Reason:
GSSMAIN was not able to access CA‑GSS services. GSSMAIN terminates.
Action:
For assistance, contact CA Support at http://ca.com/support. It may be useful to execute the GSSLOAD utility, specifying the RELOAD parameter before attempting to restart GSSMAIN.
Reason:
A previously executed GSSMAIN obtained a system linkage index (LX) of lxnum. Since system LXs cannot be freed, this copy of CA‑GSS has reclaimed it and will reuse it.
Action:
No action is required.
Reason:
GSSMAIN was unable to obtain a system linkage index (LX). The MVS LXRES routine returned the value code. GSSMAIN terminates.
Action:
Determine why the LXRES service failed and correct the problem.
Reason:
The system linkage index (LX) lxnum has been assigned for the use of CA‑GSS.
Action:
No action is required.
Reason:
The system AXSET service returned the nonzero completion code: code. GSSMAIN terminates.
Action:
Determine why the AXSET service failed and correct the condition.
Reason:
The system ETCRE service returned the nonzero completion code: code. GSSMAIN terminates.
Action:
Determine why the ETCRE service failed and correct the condition.
Reason:
The system ETCON service returned the nonzero completion code: code. GSSMAIN terminates.
Action:
Determine why the ETCON service failed and correct the condition.
Reason:
An abend occurred during execution of the named system service. GSSMAIN terminates.
Action:
Determine what problem exists with the named service and correct it before restarting GSSMAIN.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |