Reason:
RHDCUXFT was invoked by a task that is not associated with a logical terminal. This can occur if RHDCUXFT was invoked by a #ATTACH, by a #SETIME, or by a queue that was defined to invoke the program when the queue threshold is reached. RHDCUXFT should be invoked only by a #RETURN with the NXTTASK option specified to execute RHDCUXFT (with NOINPUT). The #RETURN must be issued from a task that was originally invoked from a UCF terminal.
Module:
RHDCUXFT
Severity:
5
Reason:
RHDCUXFT was invoked by a task that is not associated with a physical terminal. This condition can occur only if a DCMT VARY LTERM DISCONNECT command is issued in an untimely fashion.
Module:
RHDCUXFT
Severity:
3
Reason:
The task code that invokes RHDCUXFT was invoked either externally by a non-UCF terminal or internally by a program attached to a non-UCF terminal. The functions of RHDCUXFT are to pass data from the back end to the front end and to break the UCF connection. If the program is invoked by a terminal owned by the back-end system, there is no connection to break.
Module:
RHDCUXFT
Severity:
5
Reason:
RHDCUXFT obtained the storage with the STGID 'PDAT' and found that the first four bytes did not contain a valid record descriptor word (RDW). Specifically, the first two bytes were not in the range X'0004' through X'7FFF'. This condition is most often the result of a programming error.
Module:
RHDCUXFT
Severity:
3
Reason:
RHDCUXFT obtained the storage with the STGID 'PDAT' and found that the second two bytes of the record descriptor word (RDW) did not contain X'0000'. This condition is most often the result of a programming error.
Module:
RHDCUXFT
Severity:
3
Reason:
This message is issued by the ARCHIVE JOURNAL utility. The CV number of the Disk Journal is reported followed by the Archive Journal message text, as follows:
This message is issued after offloading and condensing a journal, and the number of journal blocks still being used is higher than the specified percentage. It is intended as a warning, so that someone can be notified and corrective action taken.
Normally this situation occurs when a long running transaction is not committing its updates on a regular basis. IDMS has to keep the before image of each uncommitted record update. When the program fails to commit the space required to keep these images continues to grow. If the situation is not addressed it is possible that all journals will fill and CV will come to a stop.
The archive journal job will wait for a reply to acknowledge that the message was noticed. Any value is an acceptable reply to the message and should be entered as soon as the message is noticed, to allow the Archive Journal job to complete.
Module:
IDMSUAJN
Severity:
0
Reason:
An invalid request was made to the LE/370 nucleus module. Storage corruption is the most likely cause.
Module:
RHDCLE37
Severity:
5
Reason:
CA IDMS could not load CEEPIPI, the LE (Language Environment) application program interface module. Ensure that the LE loadlib in which this module resides is accessible to CA IDMS. Note: on MVS, the link list is not searched when loading from CDMSLIB. Therefore, if loading is done from CDMSLIB, include the LE load library (LE-prefix.SCEERUN) in CDMSLIB.
Module:
RHDCLE37, RHDCLESM
Severity:
5
Reason:
The LE/370 pre-initialization function <function-code> completed with a nonzero <return-code>.
Action:
Check the LE/370 Programming Guide for a list of these codes.
Module:
RHDCLE37
Severity:
3
Reason:
The LE/370 runtime terminated the enclave of program <program-name> abnormally. In the log, look for the most recent user mode registers.
Action:
Check the LE/370 Programming Guide for interpretation of these values. Check the IDMS log for LE/370 messages that might clarify the abnormal enclave termination.
Check the CA IDMS log for LE/370 runtime messages that might clarify the abnormal enclave termination.
Module:
RHDCLE37
Severity:
3
Reason:
A program was enabled for a use in a multiple-program enclave, but the program was reentered after issuing a DC RETURN. To correct this problem either:
Module:
RHDCLE37
Severity:
3
Reason:
A program needs LE preinitialization services and is running on a system which supports 31-bit addressing, but the program is linked with AMODE(24). This may be invalid depending on LE and DC options in effect and LE maintenance level. If the task is allowed to continue later task abends or other problems might be encountered. It is recommended that all DC programs that use LE preinitialization services be linked with AMODE(31).
The default severity for this message is severity 5 (task abend with no snap). The default destination is the DC log file. The defaults can be modified at a particular site to write more or less diagnostic information. For example, changing the severity to 3 will result in a task abend with a task snap. If the severity is set to 0 and the destination is set to NULL, then the DC system will not produce any message.
Module:
RHDCLE37
Severity:
5
Reason:
The LE run-time environment has put out a message on behalf of an online application program. The message text is written to the CA IDMS/DC/UCF log file.
The message text may indicate an error or it may be a the result of a normal high level language verb. For example, a DISPLAY verb issued by an online COBOL program will be written to the log in the form of a DC128010 message.
Module:
RHDCLE37
Severity:
0
Reason:
This is an informational message indicating that the IDMSINFO address space is starting.
Module:
IDMSINFO
Severity:
3
Reason:
This is an informational message indicating that the IDMSINFO address space is active and ready for work.
Module:
IDMSINFO
Severity:
3
Reason:
This is an informational message indicating that the IDMSINFO address space has enabled the log operator interface. You can now issue the STOP and MODIFY commands.
Module:
IDMSINFO
Severity:
3
Reason:
This is an informational message indicating that the IDMSINFO address space has processed a STOP command and is shutting down.
Module:
IDMSINFO
Severity:
3
Reason:
This is an informational message indicating that the IDMSINFO address space completed shutdown processing and is about to end.
Module:
IDMSINFO
Severity:
3
Reason:
This is an informational message indicating that startup processing has changed the IDMSINFO address space to be non-swappable.
Module:
IDMSINFO
Severity:
3
Reason:
This is an informational message indicating whether the LX Reuse Facility is enabled in the operating system or not.
Module:
IDMSINFO
Severity:
3
Reason:
The IDMSINFO program must be authorized and loaded from an authorized library in order to function correctly. Startup processing has detected the program is not authorized and will shut down.
Module:
IDMSINFO
Severity:
3
Reason:
Only one instance of the IDMSINFO address space is permitted to run at one time on the same system. Startup processing has detected another IDMSINFO address space and will shut down.
Module:
IDMSINFO
Severity:
3
Reason:
An unsupported MODIFY console command was issued or an unsupported keyword was specified. The command was ignored.
Module:
IDMSINFO
Severity:
3
Reason:
The load of mod-name failed. The R15 return code and the abend code returned by the LOAD macro are displayed.
Module:
IDMSINFO
Severity:
3
Reason:
The named program issued the specified function or macro call and the function returned an unexpected return code in R15. The return code and a possible R0 reason code are displayed in hex and should be used to aid problem determination.
Modules:
PMRTDATA, PMRTDATD, PMRTBATD, IDMSINFO, IDMSINFA
Severity:
3
Reason:
The IDMSLPAR storage block was not found or is not initialized correctly. This may indicate that CAIRIM was not run for the IDMS product or for the correct version of IDMS.
Modules:
PMRTDATA, PMRTDATD, PMRTBATD, IDMSINFO, IDMSINFA
Severity:
3
Reason:
This is an error message indicating that the IDMSINFO address space is not active.
Modules:
PMRTDATA, PMRTDATD
Severity:
3
Reason:
This is an error message indicating that the PMRTDATA or PMRTDATD stub routine ran into an internal error condition.
Please contact Customer Support.
Modules:
PMRTDATA, PMRTDATD
Severity:
3
Reason:
A #GETSTG request for the specified size failed due to insufficient storage in a DC storage pool.
Module:
PMRTDATD
Severity:
3
Reason:
A request to cancel a task on a remote central version has failed because of insufficient authorization in the external security system. The JES log can contain additional messages from external security with detailed information.
Module:
PMRTDATA, PMRTDATD
Severity:
0
Reason:
A requested function of the external monitor is not supported by the currently used version of the IDMSINFO address space. A newer version of the IDMSINFO address space is required.
Module:
PMRTDATA, PMRTDATD
Severity:
0
Reason:
An attempt has been made to use remote (external) monitoring on an operating system on which it is not supported.
Module:
PMRTDATV
Severity:
3
Reason:
This is probably caused by an internal programming error in the application. A function was called which requires the address of a result buffer, but the address was not passed.
Please contact Technical Support.
Module:
IDMSINFA
Severity:
0
Reason:
There is no more room in the result buffer for new data. This may be an error in the calling program that does not provide a large enough storage buffer.
Please contact Technical Support.
Module:
IDMSINFA
Severity:
0
Reason:
The calling program provided a result buffer which was too small to initialize. Each request requires some overhead storage in addition to the space needed to return data, and the size was smaller than the overhead.
This is probably caused by an internal programming error in the application. Please contact Technical Support.
Module:
IDMSINFA
Severity:
0
Reason:
A function call was made which requires an initialized result buffer and the storage was not initialized.
This is probably caused by an internal programming error in the application. Please contact Technical Support.
Module:
IDMSINFA
Severity:
0
Reason:
This is an error message indicating that the PC # specified for the PC Call was not defined.
This is an internal error. If you receive this error, please contact Technical Support.
Module:
PMRTBATD
Severity:
0
Reason:
This is an error message indicating that PMRTBATD did not find a Jobname, ASCB, or ASID defined for the targeted CV.
Module:
PMRTBATD
Severity:
0
Reason:
This is an error message indicating that the ASCB and ASID that were input to PMRTBATD did not point to the same CV.
Module:
PMRTBATD
Severity:
0
Reason:
This error message indicates that Fetch Protect was enabled on the target CV and execution has been terminated.
Module:
PMRTBATD
Severity:
0
Reason:
This error message indicates that the job name specified during the indicated function call did not look like a CV.
Module:
PMRTBATD
Severity:
0
Reason:
This error message indicates that the passed ASCB address does not appear to point to a valid ASCB.
Module:
PMRTBATD
Severity:
0
Reason:
This error message indicates that PMRTBATD found the targeted CV to be swappable which is not supported.
Module:
PMRTBATD
Severity:
0
Reason:
This error message indicates that the indicated job name did not appear to be running when checked by IDMSMCVS.
Module:
PMRTBATD
Severity:
0
Reason:
This error message indicates that an abend occurred and was recovered by PMRTBATD.
Module:
PMRTBATD
Severity:
0
Reason:
The ASID that was passed does not map to a valid ASCB. The target CV may no longer be running.
Module:
PMRTBATD
Severity:
0
Reason:
The user has attempted to cancel a task on a remote central version that either does not exist or cannot be canceled. When a task issues a request for service, it gives control to the system module that services the request. For example, when a program within a user task issues a database DML statement, it gives control to IDMSDBMS. The user task cannot be canceled while system software is in control; the user task can be canceled after the system software returns control to the task. Ensure that the task is still active and retry the cancel task request.
Module:
IDMSUPDS
Severity:
0
Reason:
The user has attempted to cancel an MSTR or DBRC task on a remote central version, however this task may not be canceled.
Module:
IDMSUPDS
Severity:
0
Reason:
The user has attempted to cancel a driver task on a remote central version, however this task may not be canceled.
Module:
IDMSUPDS
Severity:
0
Reason:
The user has attempted to cancel a task on a remote central version, however this task is already terminating.
Module:
IDMSUPDS
Severity:
0
Reason:
When trying to perform the cancel task operation, the system failed to acquire a cross-memory lock on a remote central version address space. Retry the cancel task request.
Module:
IDMSUPDS
Severity:
0
Reason:
This message currently is not displayed by CA ADS.
Module:
ADSOGNP1
Severity:
3
Reason:
A premap process or a map must be defined for the dialog before the dialog can be compiled. Use the appropriate CA ADS dialog compiler screen to add either definition to the dialog.
Module:
ADSOGNP1
Severity:
0
Reason:
This is a confirming message; no action is required. The dialog has been successfully added to the dictionary.
Module:
ADSOGNP1
Severity:
0
Reason:
This is a confirming message; no action is required. The dialog has been successfully modified in the dictionary.
Module:
ADSOGNP1
Severity:
0
Reason:
An error occurred while the CA ADS dialog compiler was storing a record in the ADSG Queue Storage area. Register 4 will contain one of the following return codes:
Module:
ADSOGNP1
Severity:
3
Reason:
An error occurred while the CA ADS dialog compiler was deleting the ADSOPSRC scratch area before attempting to process a quit, suspend, or end of compile. Register 2 contains one of the following error codes:
Module:
ADSOGNP1
Severity:
3
Reason:
This is a confirming message; no action is required. The dialog load module was successfully deleted from the dictionary.
Module:
ADSOGNP1
Severity:
0
Reason:
The user has attempted to suspend a CA ADS dialog compiler session. An error occurred when the dialog attempted to acquire storage for a queue record. The attempt to suspend the dialog will abort. Register 4 contains the return code. For an explanation of GETSTG return codes, see the CA IDMS DML Reference Guide for Assembler.
Module:
ADSOGNP1
Severity:
3
Reason:
The dialog name and version number specified on the CA ADS dialog compiler Dialog Definition screen identifies a dialog that already exists in the load area. Check the spelling of the dialog name. OLQ can be used to determine whether a valid LOADHDR-156 record with the delete flag set on exists in the load area with this dialog name.
Module:
ADSOGNP1
Severity:
0
Reason:
The CA ADS dialog compiler tried to delete a nonexistent dialog.
Module:
ADSOGNP1
Severity:
0
Reason:
This message currently is not displayed by CA ADS.
Module:
ADSOGNP1
Severity:
3
Reason:
The CA ADS dialog compiler tried to compile a dialog that had responses but no maps. Perform one of the following activities before compiling the dialog:
Module:
ADSOGNP1
Severity:
0
Reason:
The CA ADS dialog compiler tried to initialize the dialog compiler block (DGB) for the first time or during a recovery, and the online control block (OCB) was not found in the common system area (CSA).
Action:
Include the ADSO statement in the system generation program. Generate the system.
Module:
ADSOGNP1
Severity:
3
Reason:
The CA ADS dialog compiler tried to acquire storage to initialize the generator storage area (GSA). Register 5 contains the return code. See the CA IDMS DML Reference Guide for Assembler for an explanation of GETSTG return codes.
Module:
ADSOGNP1
Severity:
3
Reason:
Another entity in the data dictionary uses this name. The PROG-01 record associated with this name indicates that the named entity is not a CA ADS dialog. Verify the spelling of the dialog name.
Module:
ADSOGNP1
Severity:
0
Reason:
The dialog compiler tried to acquire storage to initialize the compiler map request block (MRB). Register 5 contains the return code. For an explanation of GETSTG return codes, see the CA IDMS DML Reference Guide for Assembler.
Module:
ADSOGNP1
Severity:
3
Reason:
A symbol table was not created for the dialog even though the user enabled the symbol table option in the dialog compiler session. The probable cause is that no processes exist for the dialog; a debugger session for a dialog without processes does not require a symbol table.
Module:
ADSOGNP1
Severity:
0
Reason:
The user has selected the option to create a symbol table for a dialog during the dialog compiler session. An error has occurred because the dialog, which includes executable code, has already been compiled. Contact Technical Support for assistance.
Module:
ADSOGNP1
Severity:
0
Reason:
The CA ADS dialog compiler is being used under the transfer control facility. An error has occurred because the control block (UCE) for the transfer control facility cannot be found. One of the following conditions has probably occurred:
This is a system internal error in either the dialog compiler or the Transfer Control Facility. Print the dump and contact Technical Support.
Module:
ADSOGNDG
Severity:
3
Reason:
The CA ADS dialog compiler issued a GETSTG request while executing under the transfer control facility. The GETSTG request failed to acquire the IDD Input Area, which is needed to process either a display record or an update process request. Use the print log utility (online PLOG or RHDCPRLG) to examine the return code in User Register 5. For more information on the return code value, see the discussion of the #GETSTG macro in the CA IDMS DML Reference Guide for Assembler.
Module:
ADSOGNP1
Severity:
3
Reason:
The DC/UCF system could not find the logical terminal element (LTE) for the dialog compiler session. The LTE supplies the default dictionary name and node, if any, for a terminal. This is system internal error. Print the dump and contact Technical Support.
Module:
ADSOGNP1
A #GETDEF macro has been issued to access the LTE.
Severity:
3
Reason:
The default dictionary node and name, if any, for the terminal cannot be retrieved. Check the return code in user register 3 and contact Technical Support.
Module:
ADSOGNP1
Severity:
3
Reason:
More than one function was selected. Select only one function at a time.
Module:
ADSOGNP1
Severity:
0
Reason:
The PRINT function is invalid from the New Copy/Work Record Specification screen.
Module:
ADSOGNP1
Severity:
0
Reason:
The UPDATE Process is invalid from the DIALOG screen.
Module:
ADSOGNP1
Severity:
0
Reason:
The UPDATE process is invalid from the New Copy/Work Record Specification screen.
Module:
ADSOGNP1
Severity:
0
Reason:
The DIALOG function is invalid from the DIALOG Screen.
Module:
ADSOGNP1
Severity:
0
Reason:
The DISPLAY function is invalid from the New Copy/Work Record Specification screen.
Module:
ADSOGNP1
Severity:
0
Reason:
The user can update a map only from the Dialog Definition screen.
Module:
ADSOGNP1
Severity:
0
Reason:
The user has pressed a function key that is not valid for CA ADS.
Module:
ADSOGNP1
Severity:
0
Reason:
Paging forward is not allowed from the present screen.
Module:
ADSOGNP1
Severity:
0
Reason:
Paging backward is not allowed from the present screen.
Module:
ADSOGNP1
Severity:
0
Reason:
The DISPLAY MAP activity can display a map only after the map has been defined to the dialog. No map has been defined to the current dialog.
Module:
ADSOGNP1
Severity:
0
Reason:
The user cannot alternate between STEP and FAST modes when the CA ADS dialog compiler session is in DISPLAY mode.
Module:
ADSOGNP1
Severity:
0
Reason:
The user has pressed a program function (PF) key that is not valid for CA ADS.
Module:
ADSOGNP1
Severity:
0
Reason:
The user has pressed a program function (PF) key during a CA ADS session; however, the program function table used to define the meaning of each ADS PF key was never included in the DC/UCF SYSGEN. Contact your DCA; this may have been an oversight during the installation process.
Module:
ADSOGNP1
Severity:
0
Reason:
A dialog cannot be compiled when the CA ADS dialog compiler is in DISPLAY mode. Switch to UPDATE mode to compile dialogs.
Module:
ADSOGNP1
Severity:
0
Reason:
The user has selected DIALOG OPTIONS as the next activity, but the currently displayed screen is the Dialog Options screen. The user should select a next activity that will cause a different screen to be displayed.
Module:
ADSOGNP1
Severity:
0
Reason:
The DISPLAY MAP function is not supported for batch maps.
Module:
ADSOGNP1
Severity:
0
Reason:
A DISPLAY RECORD request was made, but no record name was entered. Enter the record name and try again.
Module:
ADSOGNP1
Severity:
0
Reason:
The CA ADS dialog compiler tried to delete a record from the scratch area ADSOGWKA because the scratch threshold has been exceeded. Register 2 contains one of the following error codes:
Module:
ADSOGNP1
Severity:
3
Reason:
The CA ADS dialog compiler tried to write the Generator Work Area (GWA) or the Parser Work Area (PWA) to scratch after the storage threshold was exceeded. Register 2 contains one of the following error codes:
Module:
ADSOGNP1
Severity:
3
Reason:
The CA ADS dialog compiler failed to acquire storage for the Generator Work Area (GWA) or Parser Work Area (PWA) across a converse. Register 2 contains the return code. For more information about the GETSTG return codes, see the CA IDMS DML Reference Guide for Assembler.
Module:
ADSOGNP1
Severity:
3
Reason:
The CA ADS dialog compiler failed to obtain a scratch record for the Generator Work Area (GWA) or Parser Work Area (PWA). Register 2 contains one of the following error codes:
Module:
ADSOGNP1
Severity:
3
Reason:
The CA ADS dialog compiler was not able to convert the address in register 0 to a word consisting of a (high-order) one-byte relative block number followed by a (low-order) three-byte offset. This is a probable system internal error. Print the dump and contact Technical Support.
Module:
ADSOGNP1
Severity:
3
Reason:
An error occurred during input (mapin) of a CA ADS dialog compiler screen. Register 2 contains one of the following codes:
Module:
ADSOGNDG
Severity:
3
Reason:
An error occurred when the CA ADS dialog compiler attempted to display (mapout) a dialog definition screen. Register 3 contains one of the following error codes:
Module:
ADSOGNDG
Severity:
3
Reason:
A user is unauthorized to perform the requested ADD, MODIFY, or DELETE action. User authorization is enabled in the data dictionary by using the INCLUDE USER clause in the DDDL ADD PROGRAM statement for the dialog.
The dialog compiler verifies user authorization by checking the USERPROG-135 junction record between the PROG-051 and USER-047 records.
Module:
ADSOGNDG
Severity:
0
Reason:
The CA ADS dialog compiler tried to acquire storage for the fixed dialog block (FDB). Register 3 contains the return code. For more information about the GETSTG return codes, see the CA IDMS DML Reference Guide for Assembler.
Module:
ADSOGNDG
Severity:
3
Reason:
The CA ADS dialog compiler session cannot be suspended because the dialog being defined has not passed program registration. The user can terminate this session in one of the following ways:
Perform one of the following activities to register a dialog:
To turn off program registration, include the AUTHORIZATION IS OFF clause in a SET OPTIONS FOR DICTIONARY/SESSION command.
Module:
ADSOGNDG
Severity:
0
Reason:
The user must specify a dialog name that begins with analphabetic or national (@, #, and $) character. A dialog name cannot contain blanks.
Module:
ADSOGNDG
Severity:
0
Reason:
The specified dialog name and version number do not identify an existing PROG-051 record for a dialog in the data dictionary. Thus, an action code of DEL or MOD cannot be specified. Ensure that the dialog name has been spelled correctly.
Module:
ADSOGNDG
Severity:
0
Reason:
The user cannot perform an ADD, MODIFY, or DELETE action while the CA ADS dialog compiler is in DISPLAY mode. Switch to UPDATE mode to perform any of these actions.
Module:
ADSOGNDG
Severity:
0
Reason:
Security has been enabled in the data dictionary for CA ADS. One or both of the following conditions is true:
Security for CA ADS is enabled by using the SECURITY FOR ADS clause of the DDDL SET OPTIONS command. Users are granted security authority by using the INCLUDE AUTHORITY clause of the DDDL ADD/MOD USER command.
Module:
ADSOGNDG
Severity:
0
Reason:
The specified name and version number identify an entity that is not a CA ADS dialog. Check the spelling of the dialog name.
Module:
ADSOGNDG
Severity:
0
Reason:
The specified name and version number identify a dialog that already exists in the data dictionary. Specify a different name or version number to add a new dialog.
Module:
ADSOGNDG
Severity:
0
Reason:
The ACTION code must be ADD, MOD (modify), or DEL (delete).Enter the correct ACTION code.
Module:
ADSOGNDG
Severity:
0
Reason:
The dialog is not authorized to use the specified subschema. Subschema registration is enabled when the AUTHORIZATION IS ON clause is specified in the ADD SUBSCHEMA statement of the subschema compiler. Any dialog that uses this subschema must be documented by an IDD PROGRAM statement that specifies an INCLUDE SUBSCHEMA clause.
Module:
ADSOGNDG
Severity:
0
Reason:
An invalid mode was specified for the MODE option. Only DISPLAY or UPDATE mode are valid. Specify either mode by overwriting the DISPLAY/UPDATE field.
Module:
ADSOGNDG
Severity:
0
Reason:
An invalid mode was specified for the MODE option. Only FAST or STEP mode is valid.
Perform one of the following activities to specify a valid mode:
Module:
ADSOGNDG
Severity:
0
Reason:
One of the following values must be specified for the MAINLINE option:
Module:
ADSOGNDG
Severity:
0
Reason:
The specified dialog does not exist in the data dictionary and cannot be displayed. Verify the spelling of the dialog name.
Module:
ADSOGNDG
Severity:
0
Reason:
The user has not selected a NEXT FUNCTION activity. The CA ADS dialog compiler cannot determine the definition screen to be displayed next because no work or new copy records exist and no premap or response process has been defined to the dialog.
Module:
ADSOGNDG
Severity:
0
Reason:
Supply the name and version number of an existing subschema on the Dialog Definition screen.
Module:
ADSOGNDG
Severity:
0
Reason:
This message currently is not displayed by CA ADS.
Module:
ADSOGNDG
Severity:
0
Reason:
The schema name specified in the Dialog Definition screen does not identify an existing schema. Verify the spelling of the schema name. Also verify that the correct dictionary and node name (if any) have been supplied.
Module:
ADSOGNDG
Severity:
0
Reason:
The version number specified for the schema is incorrect.
Module:
ADSOGNDG
Severity:
0
Reason:
The subschema specified does not exist in the schema. Check the spelling of the subschema name. Use the subschema compiler and enter the DISPLAY SUB <subschema-name> to find out in which schema the subschema belongs.
Module:
ADSOGNDG
Severity:
0
Reason:
The name (and version number) of an existing map must be specified for a dialog before premap and/or response processes can be added to the dialog.
Module:
ADSOGNDG
Severity:
0
Reason:
The specified map name and version number do not identify a map in the data dictionary. Check the spelling of the map name.
Module:
ADSOGNDG
Severity:
0
Reason:
The version number specified for the map is incorrect.
Module:
ADSOGNDG
Severity:
0
Reason:
The CA ADS dialog compiler displays this message to prompt the user to proceed with the dialog compiler session.
Module:
ADSOGNDG
Severity:
0
Reason:
This is a confirming message; no action is required. The CA ADS dialog compiler did not detect any errors in data supplied to the dialog compiler.
Module:
ADSOGNDG
Severity:
0
Reason:
The user is resuming a suspended CA ADS dialog compiler session. The dialog compiler retrieves the suspended dialog definition from a queue record rather than from the data dictionary.
Module:
ADSOGNDG
Reason:
The specified dialog name and version number identify an entity that is not a dialog. Check the spelling of the dialog name. If the entity should be a dialog, print a copy of the load module and check the load area for possible corruption. If record and process names can be found within the load module, contact Technical Support.
The header for a dialog contains the literal value "FDB*."
Module:
ADSOGNDG
Severity:
0
Reason:
The dialog name loaded does not match the Dialog Generation Block (DGB) name. Check the load area for possible corruption. If the area is not corrupted, this error message probably identifies a system internal error. Print the dump and contact Technical Support.
Module:
ADSOGNDG
Severity:
3
Reason:
One of the following conditions applies to the loaded dialog:
Check the load area for possible corruption. If the area is not corrupted, this error message probably identifies a system internal error. Print the dump and contact Technical Support.
Module:
ADSOGNDG
Severity:
3
Reason:
The dialog named could not be loaded. Register 3 contains one of the following error codes:
Module:
ADSOGNDG
Severity:
3
Reason:
A map name must be supplied when a map version number is specified.
Module:
ADSOGNDG
Severity:
0
Reason:
The current dialog definition is valid; however, the dialog cannot access database records. Database calls are allowed only if schema and subschema names are specified. This message typically is received when the user is prototyping a CA ADS dialog.
Module:
ADSOGNDG
Severity:
0
Reason:
The CA ADS dialog compiler did not create the PROG-051 program record in the dictionary. The dialog name specified is currently in use by a non-ADS entity. If this is an ADD function, choose another name for your dialog. If it is a DEL or MOD function, check the spelling of the dialog name and the specified version number. If the specified name and version number should identify a CA ADS dialog, use OLQ to check the PROG-051 record for the dialog.
Module:
ADSOGNDG
Severity:
0
Reason:
An invalid autostatus was specified. Enter one of the following valid values:
Module:
ADSOGNDG
Severity:
0
Reason:
The specified subschema name identifies more than one subschema. Name the schema to which the necessary subschema belongs.
Module:
ADSOGNDG
Severity:
0
Reason:
Use the subschema compiler to recompile the subschema. This procedure should eliminate the problem.
The subschema error flag (ERR026) was set to indicate an error in the subschema.
The following conditions are true:
Module:
ADSOGNDG
Severity:
0
Reason:
The subschema named in the Dialog Definition screen does not exist in the dictionary.
Verify the spelling of the subschema by using the subschema compiler.
Module:
ADSOGNDG
Severity:
0
Reason:
It is probable that one of the following situations exists:
The dialog compiler will not allow an unusable map to be associated with a dialog. Use the CA IDMS Mapping Facility to compile the map.
Module:
ADSOGNDG
Severity:
0
Reason:
The specified status definition record name does not exist in the data dictionary. Check the spelling of the record name and verify the version number.
Module:
ADSOGNDG
Severity:
0
Reason:
The status definition record exists, but the version specified does not exist in the data dictionary. Supply the correct version number.
Module:
ADSOGNDG
Severity:
0
Reason:
The specified status definition record contains data fields. Modify the record to include only level-88 fields.
Module:
ADSOGNDG
Severity:
0
Reason:
The status definition record specified is not owned by IDD and does not belong to the specified subschema.
Module:
ADSOGNDG
Severity:
0
Reason:
The name specified for the status definition record (SDR) is the name of a map, subschema, or work record used by the dialog. The SDR cannot be any of these record types because an SDR is not allowed to have a buffer defined for it. The layout of the SDR must follow the rules specified in the CA ADS Reference Guide.
Module:
ADSOGNDG
Severity:
0
Reason:
The CA ADS dialog compiler is being used under the transfer control facility. An error has occurred because the control block (UCE) for the transfer control facility cannot be found. One of the following conditions has probably occurred:
This is a system internal error in either the dialog compiler or the Transfer Control Facility. Print the dump and contact Technical Support.
Module:
ADSOGNDG
Severity:
3
Reason:
The dictionary or node specified on the Dialog Definition screen cannot be found. The CA ADS dialog compiler session cannot continue until these specifications are corrected.
The CA ADS dialog compiler uses the dictionary name and node supplied on the Dialog Definition screen to set the appropriate Logical Terminal Control Block (LTERM) fields.
Module:
ADSOGNDG
Severity:
0
Reason:
The dialog compiler will attempt to update the Logical Terminal Control Block (LTERM) with the dictionary and node names supplied on the CA ADS dialog compiler Dialog Definition Screen. This message indicates that the LTERM cannot be found. This is a serious internal error. Print the dump and contact Technical Support.
Module:
ADSOGNDG
Severity:
3
Reason:
The dialog compiler could not update the Logical Terminal Control Block (LTERM) with the dictionary or node name supplied on the CA ADS dialog compiler Dialog Definition screen. An unexpected return code was passed back from the DC/UCF system into register 3. This is a system internal error. Print the dump and contact Technical Support.
Module:
ADSOGNDG
Severity:
3
Reason:
A dialog can be associated with an online map or a batch map, but not with both.
Module:
ADSOGNDG
Severity:
0
Reason:
The online map name specified has been defined using the Mapping Facility as a batch map. If this map should be an online map, redefine it using the Mapping Facility.
Module:
ADSOGNDG
Severity:
0
Reason:
The batch map specified in either the batch input map field or the batch output map field has been defined using the Mapping Facility as an online map. If this map is intended to be a batch map, redefine the map using the Mapping Facility.
Module:
ADSOGNDG
Severity:
0
Reason:
This is a warning-level message. The CA ADS dialog compiler tried to get a queue record. A record defined to both this dialog's map and subschema is defined with a different version in the map from the version in the schema. The record description will be copied from the schema.
Module:
ADSOGNDG
Severity:
0
Reason:
The CA ADS dialog compiler tried to get a queue record from the ADSG Queue Storage area. Register 2 contains one of the following error codes:
Module:
ADSOGNDG
Severity:
3
Reason:
The CA ADS dialog compiler tried to get storage for the queue record from the DC/UCF storage pool and failed. Register 2 contains one of the following error codes:
Module:
ADSOGNDG
Severity:
3
Reason:
The CA ADS dialog compiler tried to transfer data from the physical terminal to the program and failed. Register 2 contains one of the following error codes:
Module:
ADSOGNRP
Severity:
3
Reason:
The CA ADS dialog compiler tried to transfer data from the program to the physical terminal and failed. Register 2 contains one of the following error codes:
Module:
ADSOGNRP
Severity:
3
Reason:
The premap process has not been defined to the dialog. This is a warning message only.
Module:
ADSOGNRP
Severity:
0
Reason:
This is a confirming message; no action is required. The premap or response process has been compiled successfully; there are no syntax errors.
Module:
ADSOGNRP
Severity:
0
Reason:
The dialog is not associated with an online map or a batch input map. Associate the dialog with one of these before attempting to define response processes.
Module:
ADSOGNRP
Severity:
0
Reason:
The only valid values that the user can key for the DELETE option on the Response or Premap Process Definition screens are YES and Y. The user cancels a YES or Y specification by nulling the value with the ERASE EOF key.
Module:
ADSOGNRP
Severity:
0
Reason:
The DELETE action only can be used to delete a premap process that already is defined to the dialog.
Module:
ADSOGNRP
Severity:
0
Reason:
This is a confirming message; no action is required. The response or premap process has been deleted successfully.
Module:
ADSOGNRP
Severity:
0
Reason:
The control key specified for a response process is not valid.
Module:
ADSOGNRP
Severity:
0
Reason:
A control key, a response field value, or the default response designation must be supplied.
Module:
ADSOGNRP
Severity:
0
Reason:
The version number specified for the process is incorrect. Access IDD and use the DISPLAY MODULE <process-name> AS SYNTAX statement to find the version number for the specified process.
Module:
ADSOGNRP
Severity:
0
Reason:
The CA ADS dialog compiler attempted to compile the specified process, but the process was not found in the dictionary.
Module:
ADSOGNRP
Severity:
0
Reason:
The CA ADS dialog compiler attempted to compile the process source code and failed. Select DISPLAY or PRINT as the next activity to view errors encountered in the process source code. Access IDD to correct the process source code.
Module:
ADSOGNRP
Severity:
0
Reason:
The CA ADS dialog compiler displays this message to prompt the user to proceed with the dialog compiler session.
Module:
ADSOGNRP
Severity:
0
Reason:
Two responses within a dialog cannot be associated with the same control key.
Module:
ADSOGNRP
Severity:
0
Reason:
A response defined to a dialog must be associated with a response field value that is unique within the dialog.
Module:
ADSOGNRP
Severity:
0
Reason:
The specified response process does not exist. Access IDD and use the DISPLAY MODULE <process-name> AS SYNTAX statement to check the spelling of the response process name.
Module:
ADSOGNRP
Severity:
0
Reason:
The CA ADS dialog compiler cannot display any response processes since no responses have been defined to the dialog.
Module:
ADSOGNRP
Severity:
0
Reason:
The CA ADS dialog compiler could not pass control from ADSOGEN1 to ADSOGEN2. Register 2 contains the error code 04, which indicates that one of the following situations caused the error:
Module:
ADSOGNRP
Severity:
3
Reason:
The MODULE-067 record associated with the named process has been found in the dictionary; however it has been defined as something other than a process. Check the spelling of the process name and the validity of the specified version number.
Module:
ADSOGNRP
Severity:
0
Reason:
An invalid mode was specified for the MODE option. Only FAST or STEP mode is valid.
Perform either of the following procedures to specify a valid mode:
Module:
ADSOGNRP
Severity:
0
Reason:
The only acceptable entries in the EXECUTE ON EDIT ERROR field on the Response Process Definition screen are the following: Y, YES, N, and NO. Change the current contents of the field to one of these acceptable values.
Module:
ADSOGNRP
Severity:
0
Reason:
The following control keys are invalid when the dialog has a nonpageable map defined to it:
If the map should be nonpageable, select another unique control key to define to this process. If the map should be pageable, use the CA IDMS Mapping Facility to define the map as a pageable map and to recompile the map.
Module:
ADSOGNRP
Severity:
0
Reason:
A response process with the same name already exists for dialog. This situation is valid as long as the control key and response field value are unique.
Module:
ADSOGNRP
Severity:
0
Reason:
This is a confirming message; no action is required. The response process is a duplicate of another response process within the dialog and therefore does not need to be recompiled.
Module:
ADSOGNRP
Severity:
0
Reason:
A batch control event can be associated with only one response process within a dialog.
Module:
ADSOGNRP
Severity:
0
Reason:
Another response process has already been designated as the dialog's default response process.
Module:
ADSOGNRP
Severity:
0
Reason:
An invalid batch control event was specified. Valid batch control events are:
Module:
ADSOGNRP
Severity:
0
Reason:
An invalid choice was made for the default response setting. Enter Y (yes) or N (no).
Module:
ADSOGNRP
Severity:
0
Reason:
As part of the definition of a response process in a batch dialog, one of the following must be provided:
You can specify a batch control event of EOR or IOERR.
Module:
ADSOGNRP
Severity:
0
Reason:
A choice other than SQLERROR, SQLWARNING or NOT FOUND was specified in the SQL WHENEVER clause.
Module:
ADSOGSQL
Severity:
0
Reason:
The CONTINUE or CALL subroutine must be specified as the action taken on an SQL condition.
Module:
ADSOGSQL
Severity:
0
Reason:
While searching for END-EXEC, the end of the input source was reached.
Module:
ADSOGSQL
Severity:
0
Reason:
The HOST VARIABLE name specified is invalid. An attempt to locate the description of this HOST VARIABLE in the dictionary was unsuccessful.
Module:
ADSOGSQL
Severity:
0
Reason:
The SUBROUTINE NAME referenced in an SQL WHENEVER statement has not been defined as a SUBROUTINE.
Module:
ADSOGSQL
Severity:
0
Reason:
The HOST VARIABLE structure is defined to the dictionary as a group and contains another group within its definition.
Module:
ADSOGSQL
Severity:
0
Reason:
An SQL dynamic request that refers to a record with structure resembling an SQLDA record was not found.
Module:
ADSOGSQL
Severity:
0
Reason:
The HOST VARIABLE name parsed is not a properly constructed data-field-name.
Module:
ADSOGSQL
Severity:
0
Reason:
The internal counter of valid syntax lines was zero, so there was nothing to process.
Module:
ADSOGSQL
Severity:
0
Reason:
A negative return code (SQLCODE) was set on return from the database (SQL HANDLER) while attempting to connect to the dictionary.
Module:
ADSOGSQL
Severity:
0
Reason:
One or more of the following required SQL records were not found in the dictionary:
Module:
ADSOGSQL
Severity:
0
Reason:
The database could not process an SQL INSTALL request and issued a negative return code (in SQLCODE field).
Module:
ADSOGSQL
Severity:
0
Reason:
When a cursor is declared, no code is generated, but the environment is saved for a later request to OPEN the cursor. When an attempt was made to restore the environment, this problem occurred.
Module:
ADSOGSQL
Severity:
0
Reason:
An unidentified node was passed to ADSOTSQL from ADSOGSQL.
Module:
ADSOTSQL
Severity:
3
Reason:
A parse tree node contains an invalid branch code and it was detected in ADSOGSQL.
Module:
ADSOGSQL
Severity:
3
Reason:
There is not enough room in the stack to continue processing.
Module:
ADSOGSQL
Severity:
3
Reason:
One or more of the following required SQL records were not found in the dictionary:
Module:
ADSOGSQL
Severity:
0
Reason:
On a return from a successful SQL INSTALL request, the database buffers have incorrect values in them.
Module:
ADSOGSQL
Severity:
3
Reason:
ADSOGSQL received a return code from ADSOGNRS indicating a problem in ADSOGNRS processing.
Module:
ADSOGSQL
Severity:
3
Reason:
While parsing an SQL statement a period immediately followed a HOST VARIABLE name. A qualifier does not immediately follow the period.
Module:
ADSOGSQL
Severity:
0
Reason:
While parsing an SQL statement, the offset of the SQL token in error was returned in the SQLCA record (SQLCSER). This is then converted to LINE and OFFSET by ADSOGSQL and the information is passed along here.
Module:
ADSOGSQL
Severity:
0
Reason:
An SQL FETCH BULK command must receive data into the first field of a record.
Module:
ADSOGSQL
Severity:
0
Reason:
ADSC Compile failed during @SQL Install because there was not enough free space in the DDLDCLOD area to store the RCM. Run CLOD, delete some load modules, or increase the size of the DDLDCLOD area.
Module:
ADSOGSQL
Severity:
3
Reason:
The HOST VARIABLE name specified is invalid. The attempt to locate the description of this HOST VARIABLE in the dictionary found that it is defined in two different records. This HOST VARIABLE name must be qualified by a record name.
Module:
ADSOGSQL
Severity:
0
Reason:
The CA ADS dialog compiler attempted to transfer data from the physical terminal to the program. Register 2 contains one of the following error codes:
Module:
ADSOGNNC
Severity:
3
Reason:
The CA ADS dialog compiler attempted to transfer data from the program to the physical terminal. Register 2 contains one of the following error codes:
Module:
ADSOGNNC
Severity:
3
Reason:
This message currently is not displayed by CA ADS.
Module:
ADSOGNNC
Severity:
0
Reason:
This is a confirming message; no action is required. The new copy or work record was processed successfully.
Module:
ADSOGNNC
Severity:
0
Reason:
This message currently is not displayed by CA ADS.
Module:
ADSOGNNC
Severity:
0
Reason:
This message currently is not displayed by CA ADS.
Module:
ADSOGNNC
Severity:
0
Reason:
A status definition record cannot be a new copy or a work record.
Module:
ADSOGNNC
Severity:
0
Reason:
A new copy or work record cannot be a member of a logical record.
Module:
ADSOGNNC
Severity:
0
Reason:
An invalid mode was specified for the MODE option. Only FAST or STEP mode is valid.
Perform either of the following procedures to specify a valid mode:
Module:
ADSOGNNC
Severity:
0
Reason:
The new copy or work record specified does not exist in the subschema or map or is not IDD-owned.
Module:
ADSOGNNC
Severity:
0
Reason:
The version number specified for a record is incorrect. Access IDD to check the record version number.
Module:
ADSOGNNC
Severity:
0
Reason:
The specified record is not owned by IDD and, thus, is not valid for the dialog.
Module:
ADSOGNNC
Severity:
0
Reason:
This is only a warning message. A record specified as a work record is already defined as a map record. It can be useful to define a record redundantly to a dialog, particularly if the user expects the record to be deleted from the map in the near future.
Module:
ADSOGNNC
Severity:
0
Reason:
The record specified does not belong to a logical record, an autostatus record, a map, or a subschema. It should be specified as a work record.
Module:
ADSOGNNC
Severity:
0
Reason:
The record specified is already defined to the dialog but with a different version number. Duplicate record names with different version numbers are illegal within the same dialog.
Module:
ADSOGNNC
Severity:
0
Reason:
The record already has been defined to the dialog as either a new copy or work record.
Module:
ADSOGNNC
Severity:
0
Reason:
The record, which has been selected as a work record, is a subschema record (it has been defined to the subschema associated with the dialog); as such, it will be bound at runtime. If an IDD-created record has the same name as a subschema-defined record, and if the subschema is associated with the dialog, the subschema-defined record will be used.
Module:
ADSOGNNC
Severity:
0
Reason:
When the CA ADS dialog compiler attempted to display or print one of a dialog's processes, a #GETSTG was initiated to obtain a temporary print buffer. No space was available. Register 3 contains the return code. For more information about the GETSTG return codes, see the CA IDMS DML Reference Guide for Assembler.
A snapshot dump, taken at the time of the error, provides an indication of the load on the system and can help determine the cause of the error. Notify the database administrator of the message and the snapshot dump. Repeat the procedure to display or print the process only with the approval of the database administrator.
Module:
ADSOGNDS
Severity:
3
Reason:
This message is not displayed currently by CA ADS.
Module:
ADSOGNDS
Severity:
3
Reason:
An error occurred during the DISPLAY PROCESS activity. Register 2 contains one of the following return codes:
A snapshot dump is taken at the time of the error to determine the cause of the problem. Notify the database administrator of the problem and of the snapshot dump. Repeat the procedure to display the line only with the approval of the database administrator.
When the DISPLAY PROCESS function was issued, a #LINEOUT macro was issued to display a line of data to the user's terminal. The DC/UCF system returned the error code after issuing the #LINEOUT.
Module:
ADSOGNDS
Severity:
3
Reason:
Syntax errors in the process code cannot be displayed or printed. The scratch record that contains the results of the attempted compile cannot be accessed. Register 2 contains one of the following return codes:
A snapshot dump is taken at the time of the error to determine the cause of the problem. Notify the database administrator of the problem and of the snapshot dump. Repeat the procedure to display or print the process only with the approval of the database administrator.
DC returned a bad return code after issuing a #GETSCR macro.
Module:
ADSOGNDS
Severity:
3
Reason:
An internal error has occurred in one of the print buffers used to display or print a process. A print record must contain one of the following items:
Use the SNAP command to obtain a snapshot dump and notify the database administrator.
Module:
ADSOGNDS
Severity:
3
Reason:
An error was encountered during a DISPLAY MAP activity. Register 2 contains the return code from this error. Use the SNAP command to obtain a snapshot dump.
When the DISPLAY MAP function was requested, the #MREQOUT mapout macro was issued. The DC/UCF system returned a bad return code after issuing the #MREQOUT macro.
Module:
ADSOGNDS
Severity:
3
Reason:
An error was encountered during the PRINT PROCESS activity. The return code from this error is in register 2. Use the SNAP command to obtain a snapshot dump.
When the PRINT PROCESS function was requested, the #PRINT macro was issued to print a line. The DC/UCF system issued a bad return code after issuing the #PRINT macro.
Module:
ADSOGNDS
Severity:
3
Reason:
This message confirms that the PRINT PROCESS function was successfully executed and the process was printed; no corrective action is required. Contact the database administrator to find out where the listing was routed.
Module:
ADSOGNDS
Severity:
0
Reason:
The DISPLAY MAP function was requested, but the mapload module could not be found in the load area. It is possible that one of the following situations caused the error:
Module:
ADSOGNDS
Severity:
0
Reason:
The map associated with the dialog is not valid for the terminal (device) being used to defined the dialog. Therefore, the map cannot be displayed during the current CA ADS dialog compiler session. Perform one of the following steps to view the map:
For more information about valid terminals for maps, see the CA IDMS Mapping Facility Guide.
Module:
ADSOGNDS
Severity:
0
Reason:
An attempt to bind a run unit for the CA ADS subschema (IDMSNWKO) with the default or specified node and dbnames has failed. Check the IDMS status code in the subschema control area (a brief description of this area is formatted at the end of the SYSLST dataset). If the error indicates a condition that your DCA does not consider an onsite problem, contact Technical Support.
Module:
ADSOGNDB
Severity:
0
Reason:
An attempt to bind the specified record failed. Check the IDMS status code in the subschema control area (a brief description of this area will be formatted at the end of the SYSLST dataset.) If the error indicates a condition that your DCA does not consider an onsite problem, contact Technical Support.
Module:
ADSOGNDB
Severity:
0
Reason:
An attempt to ready specified area failed. Check the IDMS status code in the subschema control area; a brief description of this area will be formatted at the end of the SYSLST data set. If the error indicates a condition that your DCA does not consider an onsite problem, contact Technical Support.
Module:
ADSOGNDB
Severity:
0
Reason:
An attempt to FIND or OBTAIN a specified record failed. Check the IDMS status code in the subschema control area; a brief description of this area will be formatted at the end of your SYSLST dataset. If the error indicates a condition your DCA does not consider an onsite problem, contact Technical Support.
Module:
ADSOGNDB
Severity:
0
Reason:
An ACCEPT command failed. The ACCEPT command was supposed to accept the database key of one of the following items:
Check the IDMS status code in the subschema control area (a brief description of this area will be formatted at the end of your SYSLST dataset.) If the error indicates a condition your DCA does not consider an onsite problem, contact Technical Support.
Module:
ADSOGNDB
Severity:
0
Reason:
An attempt to issue a FINISH command for the task has failed. An invalid status was returned from the system module IDMSDBIO. Check the DC/UCF print log for details.
Module:
ADSOGNDB
Severity:
0
Reason:
An attempt to issue a COMMIT ALL to commit the dictionary updates for the application being compiled has failed. Check the IDMS status code in the subschema control area (a brief description of this area will be formatted at the end of your SYSLST dataset.) If the error indicates a condition your DCA does not consider an onsite problem, contact Technical Support.
Module:
ADSOGNDB
Severity:
0
Reason:
The error message number printed with this message cannot be found in the dictionary with the OBTAIN CALC command. The database administrator should be notified; the message area must be reviewed.
Module:
ADSOGNDB
Severity:
0
Reason:
The bind run unit for the IDMSNWKO subschema with the specified node name has failed with an IDMS status code of 1480. This code indicates that the node was not found. Verify that the node name is spelled correctly, and that it is active.
Module:
ADSOGNDB
Severity:
0
Reason:
The bind run unit for the IDMSNWKO subschema with the specified <dictname> has failed with an IDMS status code of 1481. This code indicates that the specified dictionary does not exist. Verify that the dictionary name is spelled correctly.
Module:
ADSOGNDB
Severity:
0
Reason:
This message supplies the status for the error indicated by the immediately preceding message.
Module:
ADSOGNDB
Severity:
3
Reason:
A bad IDMS status code was returned for the indicated command. Contact your DCA to determine the appropriate action to be taken. It may be necessary to print the dump and contact Technical Support.
Module:
ADSOGNDB
Severity:
3
Reason:
A bad IDMS status code was returned for the indicated command. The command applied to the named record or area. Contact your DCA to determine the appropriate action to be taken. It may be necessary to print the dump and contact Technical Support.
Module:
ADSOGNDB
Severity:
3
Reason:
An attempt to acquire storage for building an initialized buffer for the current record failed for either of the following reasons:
Increase the size of the storage pool or repeat the procedure.
Module:
ADSOGNRC
Severity:
3
Reason:
The PICTURE clause for the current field contains an invalid character. The invalid character follows the "V" that indicates a decimal position in the picture. Check the element (field) definition.
The PICTURE clause is saved in the SDR-042 dictionary record for the current field.
Module:
ADSOGNRC
Severity:
3
Reason:
The data type of the current field (element) could not be determined from the SDR-042 dictionary record. Check the element definition.
Module:
ADSOGNRC
Severity:
3
Reason:
Storage needed for a work area could not be acquired for one of the following reasons:
The work area is needed to initialize the value clause for the indicated element (data field). Check the element definition.
The picture for the element (field) is stored in the SDES-044 dictionary record.
Module:
ADSOGNRC
Severity:
3
Reason:
Storage needed for a work area could not be acquired for one of the following reasons:
The work area is needed to initialize the value clause for the indicated element (data field). Check the element definition.
Module:
ADSOGNRC
Severity:
3
Reason:
An invalid record has been encountered. The record is invalid for one of the following reasons:
Module:
ADSOGNRC
Severity:
3
Reason:
There is an error in the PICTURE clause for the current decimal floating point data element. The picture does not have a sign ("+" or "-") in front of the mantissa.
For more information about formatting pictures for floating point data, see the CA IDMS Mapping Facility Guide.
The PICTURE clause is saved in the SDR-042 dictionary record.
Module:
ADSOGNRC
Severity:
3
Reason:
There is an error in the PICTURE clause for the current decimal floating point data element. The picture has an assumed decimal point ("V") rather than an actual decimal point (".").
For more information about pictures for floating point data, see the CA IDMS Mapping Facility Guide.
The PICTURE clause is saved in the SDR-042 dictionary record.
Module:
ADSOGNRC
Severity:
3
Reason:
The PICTURE clause for the current floating point data element specifies an invalid exponent value. The first character of the exponent is not an "E". The following sample valid and invalid picture formats show how an exponent is expressed for a floating point data element:
VALID PICTURE INVALID PICTURE +999.99E+99 +999.99+99
For more information about formatting pictures for floating point data, see the CA IDMS Mapping Facility Guide.
The PICTURE clause is saved in the SDR-042 dictionary record.
Module:
ADSOGNRC
Severity:
3
Reason:
The PICTURE clause for the current floating point data element specifies an invalid exponent value. The exponent must contain four characters that are configured as follows:
For more information about formatting pictures for floating point data, see the CA IDMS Mapping Facility Guide.
The PICTURE clause is saved in the SDR-042 dictionary record.
Module:
ADSOGNRC
Severity:
3
Reason:
The PICTURE clause for the current floating point data element specifies an invalid exponent value
The exponent must contain four characters that are configured as follows:
For information about formatting pictures for floating point data, see the CA IDMS Mapping Facility Guide.
The PICTURE clause is saved in the SDR-042 dictionary record.
Module:
ADSOGNRC
Severity:
3
Reason:
The PICTURE clause for the current floating point data element specifies an invalid exponent value. The exponent must contain four characters that are configured as follows:
For more information about formatting pictures for floating point data, see the CA IDMS Mapping Facility Guide.
The PICTURE clause is saved in the SDR-042 dictionary record.
Module:
ADSOGNRC
Severity:
3
Reason:
There is no mantissa value specified in the PICTURE clause.
The mantissa must be configured as follows:
The mantissa ends and the exponent begins with an "E" character. For example, the mantissa of each of the following picture formats goes up to but does not include the "E":
+999.99E+99 -9.9999999E+99
For more information on formatting pictures for floating point data, see the CA IDMS Mapping Facility Guide.
The PICTURE clause is saved in the SDR-042 dictionary record.
Module:
ADSOGNRC
Severity:
3
Reason:
Multibit binary elements must not be included in an occurring group that has elements of any other data type. For more information about defining records, see the IDD DDDL Reference Guide.
Module:
ADSOGNRC
Severity:
3
Reason:
The named work or map record is flagged in the data dictionary as having a critical error such as record length greater than 32K; an element length that is equal to 0; an element that is redefined by a non-subordinate element, and so forth.
Module:
ADSOGNRC
Severity:
3
Reason:
The named element is in a record that is defined as an element in two different logical records in the dialog subschema. Qualify the element with the name of the logical record.
Module:
ADSOGNRC
Severity:
0
Reason:
This message follows message DC156020 to display the names of the logical records that use the element that is in error.
Module:
ADSOGNRC
Severity:
0
Reason:
The element in error is defined to two records that are elements in a logical record in the dialog subschema. Qualify the element with the correct record name.
Module:
ADSOGNRC
Severity:
0
Reason:
This message follows message DC156022 to display the names of the logical record elements that use the field that is in error.
Module:
ADSOGNRC
Severity:
0
Reason:
The element in error is defined in two records that are elements in the dialog subschema. Qualify the element with the correct record name.
Module:
ADSOGNRC
Severity:
0
Reason:
The element in error is defined in two SQL records that are associated with the dialog. Qualify the element with the correct table name.
Module:
ADSOGNRC
Severity:
0
Reason:
An attempt to acquire storage for the work area for the dialog or application compiler has failed for one of the following reasons:
The size of these work areas is determined by the primary and secondary buffer sizes specified in the ADSO SYSGEN statement.
Module:
ADSOGNRC
Severity:
3
Reason:
The primary and secondary buffer sizes specified in the ADSOSYSGEN statement are not large enough to accommodate the control block needed to compile this dialog. Increase the size of the primary and/or secondary buffer in the ADSO SYSGEN statement.
Module:
ADSOGNRC
Severity:
3
Reason:
The CA ADS dialog or application compiler is attempting to free a control block outside of its work area. This condition indicates a serious internal error. Contact Technical Support.
Module:
ADSOGNRC
Severity:
3
Reason:
The first word encountered in the current process command does not match any of the keywords that are valid as process command initiators. The rest of the command up to and including the period is ignored. Check the spelling of the keyword and refer to the CA ADS Reference Guide for valid initiating keywords.
Module:
ADSOGNPR
Severity:
0
Reason:
The amount of storage acquired by the command parser for its internal use is insufficient. Send the dump to Technical Support.
Module:
ADSOGNPR
Severity:
3
Reason:
The current process does not contain a control command. All processes must have at least one control command or else the dialog will loop or abend when the process is executed at runtime. Check the CA ADS Quick Reference Guide for a list of control commands.
Module:
ADSOGNPR
Severity:
0
Reason:
The current process has a LINK command as its last command. At runtime when a LINK command is executed, control returns to the command immediately following it. The LINK command should not be the last statement.
Module:
ADSOGNPR
Severity:
0
Reason:
The current response process has an area readied for update which is illegal in a dialog that has not selected the Retrieval locks are kept'' option from the ADSC dialog Options and Directives'' screen and its premap process has readied all areas for retrieval. At runtime the ready of this update area would abend with DC173015 DIALOG ABORTED DUE TO VIOLATION OF NO RETRIEVAL LOCKING RULE.
Severity:
0
Module:
ADSOGNPR
Reason:
An attempt to delete all the scratch records in the ADSOPSRC scratch area has failed. An I/O error has occurred. Repeat the procedure.
Module:
ADSOGNPR
Severity:
0
Reason:
The current process contains a CALL subroutine command. An error has occurred because the subroutine is not defined in the process. Perform one or more of the following steps to correct the problem:
Module:
ADSOGNPR
Severity:
0
Reason:
An attempt to acquire storage for internal use has failed for one of the following reasons:
Increase the size of the storage pool or repeat the procedure.
Module:
ADSOGNPR
Severity:
3
Reason:
An internally generated ABORT command was executed because the current process had no logical end; that is, execution continued beyond the end of the process. All processes must be logically terminated by a control command. Check the process logic.
Module:
ADSOGNPR
Severity:
0
Reason:
A declaration module can contain only WHENEVER and DECLARE CURSOR SQL commands. Since the module is never executed, functional ADS commands such as MOVE and DISPLAY are not allowed. Remove the functional commands and reserve the module for declarative SQL commands only.
Module:
ADSOGNPR
Severity:
0
Reason:
The amount of storage acquired by the command parser for internal use is insufficient. This error can occur when the parser encounters the following:
Rewrite the statements to reduce complexity and/or the level of nesting. To increase parse stack size, contact Technical Support.
Module:
ADSOGNPR
Severity:
3
Reason:
The amount of storage acquired by the command parser for internal use is insufficient. This error can occur when the parser encounters the following:
Rewrite the statements to reduce complexity and/or the level of nesting. To increase parse stack size, contact Technical Support.
Module:
ADSOGNPR
Severity:
3
Reason:
An attempt to acquire storage for the master function table failed for either of the following reasons:
Increase the size of the storage pool or repeat the procedure. The return code from the #GETSTG is in Register 4.
Module:
ADSOGNPR
Severity:
3
Reason:
The master function table has been properly loaded from the load area, but there are no entries in it. Contact the DBA to determine if there is a problem with the installation of the table. If no problems are found, contact Technical Support.
Module:
ADSOGNPR
Severity:
3
Reason:
An attempt to acquire storage for the load module and function address table failed for either of the following reasons:
Increase the size of the storage pool or repeat the procedure. The return code from the #GETSTG is in Register 4.
Module:
ADSOGNPR
Severity:
3
Reason:
More than 10 parse errors occurred in the current card image line. A maximum of 10 parse errors can be displayed per line. Correct the parse errors indicated for each line.
Module:
ADSOGNPR
Severity:
0
Reason:
An attempt to load a function load module has failed. Any function name found in the master function table is assumed to have a valid function program name in the master function table entry. Notify the DBA of the problem. If no problem is found, contact Technical Support. The return code from the #LOAD is in Register 4.
Module:
ADSOGNPR
Severity:
3
Reason:
The parsed function name was found in the master function table with a valid program name that was successfully acquired by a #LOAD. An error occurred because the function name was not found in the function load module. Notify the DBA of the problem. If no problem is found, contact Technical Support.
Module:
ADSOGNPR
Severity:
3
Reason:
The function load module table is full. This is probably an internal error. Contact Technical Support.
There is no valid reason why the function load module table should ever become full; the function load module table is allocated to have an entry for each entry in the master function table.
Module:
ADSOGNPR
Severity:
3
Reason:
An internal error occurred in the process command parser. The error occurred while the parser was adding an entry to the print buffer for the process. This is a system internal error. Contact Technical Support.
Module:
ADSOGNPR
Severity:
3
Reason:
An attempt to acquire storage for the process print buffer failed for either of the following reasons:
Increase the size of the storage pool or repeat the procedure.
Module:
ADSOGNPR
Severity:
3
Reason:
An I/O error occurred while the process parser was writing a process print buffer as a scratch record. Repeat the procedure.
Module:
ADSOGNPR
Severity:
3
Reason:
An internal error occurred in the process command parser. The error occurred while the parser was adding an entry to the print buffer for the process. This is a system internal error. Contact Technical Support.
Module:
ADSOGNPR
Severity:
3
Reason:
The current line contains an EJECT directive and process source code. The EJECT directive must appear alone on the line. Rearrange the process source code.
Module:
ADSOGNLX
Severity:
0
Reason:
The current line contains a SPACE directive and process source code. The SPACE directive must be specified alone on a line. Rearrange the process source code.
Module:
ADSOGNLX
Severity:
0
Reason:
The current literal string is longer than the maximum length allowed. Check syntax for the current process command for a maximum string length. No literal string in a process can be longer than 256 characters.
Module:
ADSOGNLX
Severity:
0
Reason:
The current literal string is shorter than the minimum literal string allowed for the process command. Check the syntax for the process command for literal length rules.
Module:
ADSOGNLX
Severity:
0
Reason:
This message applies to batch compiler (ADSOBGEN) commands. The sequence number on the current line is smaller than the sequence number on the previous line. Sequence checking occurs if the ISEQ directive is included in statements submitted to the batch recompiler. To resolve this problem, either remove the ISEQ directive from the input or rearrange the input.
Module:
ADSOGNLX
Severity:
3
Reason:
The database key of the TEXT-088 record that contains the current INCLUDE command changed while the included module was being compiled. Repeat the procedure.
Module:
ADSOGNLX
Severity:
3
Reason:
The internal control block cannot be found. The internal control block indicates which included module is to be restored after a nested included module has been compiled.
Module:
ADSOGNLX
Severity:
3
Reason:
The binary constant that has been flagged contains a value other than a 1 or a 0. The correct syntax for a binary constant is B'0101', where the following rules apply:
Module:
ADSOGNLX
Severity:
3
Reason:
A G-literal contains non-DBCS characters. G-literals should start with a shiftout (SO) character and end with a shiftin (SI) character. DBCS characters are allowed only between the SO and the SI. Remove the non-DBCS characters.
Module:
ADSOGNLX
Severity:
0
Reason:
The amount of storage acquired by the command parser for internal use is insufficient. This error can occur when the parser encounters the following:
Rewrite the statements to reduce complexity and/or the level of nesting. To increase parse stack size, contact Technical Support.
Module:
ADSOGNLX
Severity:
3
Reason:
The variable specified as the db-key, sort field, or sequence number is not valid.
Module:
ADSOGDAB
Severity:
0
Reason:
All database commands must end with a period.
Module:
ADSOGDAB
Severity:
0
Reason:
A database command was incomplete; therefore the end-of-file was encountered before the end of statement.
Module:
ADSOGDAB
Severity:
0
Reason:
The database command did not specify a record name. The specified record name must identify an existing record.
Module:
ADSOGDAB
Severity:
0
Reason:
The database command did not specify a set or area name. The specified name must identify an existing set or area.
Module:
ADSOGDAB
Severity:
0
Reason:
The keyword WITHIN was expected but not found in a database command. For example, WITHIN is required in the following command:
FIND OWNER WITHIN <set-name>
Module:
ADSOGDAB
Severity:
0
Reason:
The database command did not specify a set name. The specified name must identify an existing set.
Module:
ADSOGDAB
Severity:
0
Reason:
The keyword USING was expected but not found in a database command. For example, USING is required in the following command:
FIND <record-name> WITHIN <set-name> USING <sort-field-name-v>
Module:
ADSOGDAB
Severity:
0
Reason:
The keyword TO was not found in the CONNECT database command. The correct form of the command is as follows:
CONNECT <record-name> TO <set-name>
Module:
ADSOGDAB
Severity:
0
Reason:
The keyword MEMBERS was expected but not found in the ERASE database command. Syntax for the ERASE command is located in the CA ADS Quick Reference Guide.
Module:
ADSOGDAB
Severity:
0
Reason:
The READY command contains an invalid keyword. One of the following valid keywords must be used:
Module:
ADSOGDAB
Severity:
0
Reason:
The keyword FROM was expected but not found in a database command. For example, FROM is required in the following command:
ACCEPT DB-KEY <db-key-v> FROM <record-name> CURRENCY
Module:
ADSOGDAB
Severity:
0
Reason:
A sequence number was not found after the minus (-) sign. The sequence number must follow the minus sign and can be from 1 through 16 digits in length.
Module:
ADSOGDAB
Severity:
0
Reason:
The keyword CURRENCY was expected but not found in the ACCEPT command. Syntax for the ACCEPT command is located in the CA ADS Quick Reference Guide.
Module:
ADSOGDAB
Severity:
0
Reason:
The area, set, or record name was not specified in the DB-KEY command. The specified name must identify an existing area, set, or record.
Module:
ADSOGDAB
Severity:
0
Reason:
The keyword IDMS-STATISTICS was not found in the ACCEPT STATISTICS command. This keyword cannot be abbreviated.
Module:
ADSOGDAB
Severity:
0
Reason:
The keyword CURRENT was not found in the KEEP command. Refer to the CA ADS Reference Guide for an explanation of KEEP command syntax.
Module:
ADSOGDAB
Severity:
0
Reason:
The logical record condition expression is missing or does not match the logical record conditional expression syntax as defined in the CA ADS Reference Guide.
Module:
ADSOGDAB
Severity:
0
Reason:
Either the keyword ERROR CODES or the left parenthesis of the code list was not found in the ALLOWING ERROR CODES clause.
Module:
ADSOGDAB
Severity:
0
Reason:
Either code or the right parenthesis of the code list was not found in the ALLOWING ERROR CODES clause.
Module:
ADSOGDAB
Severity:
0
Reason:
The status code following the keyword THRU was not found in the ALLOWING ERROR CODES clause.
Module:
ADSOGDAB
Severity:
0
Reason:
The keyword PROCEDURE was expected, but not found, in a database command. For example, PROCEDURE is required in the following command:
BIND PROCEDURE FOR <proc-name-vq> TO <proc-location-v> <error-expression>.
Module:
ADSOGDAB
Severity:
0
Reason:
The data name specified for the procedure name or procedure location in the BIND PROCEDURE command is not a valid left-hand dataname.
Module:
ADSOGDAB
Severity:
0
Reason:
A bad node was passed to the ADSOGDAB program from the higher level program ADSOGNPR. This is a system internal error. Print the dump and contact Technical Support.
Module:
ADSOGDAB
Severity:
3
Reason:
The ADSOGDAB program followed an invalid branch that was not executable. This is a system internal error. Print the dump and contact Technical Support.
Module:
ADSOGDAB
Severity:
3
Reason:
The amount of storage acquired by the command parser for internal use is insufficient. This error can occur when the parser encounters the following:
Rewrite the statements to reduce complexity or the level of nesting. To increase parse stack size, contact Technical Support.
Module:
ADSOGDAB
Severity:
3
Reason:
The ready mode for the area requested in this command conflicts with the ready mode specified when the subschema was defined.
Module:
ADSOGDAB
Severity:
0
Reason:
The specified record is not a logical record. This dialog can access only logical records because the associated subschema was defined with the USAGE IS LR (logical record) clause.
Module:
ADSOGDAB
Severity:
0
Reason:
When no specific area is specified, it is assumed that all areas are to be readied. However, one or more of the areas in the subschema conflict with the ready mode requested.
Module:
ADSOGDAB
Severity:
0
Reason:
The record name specified in the WITHIN clause of the FIND command does not exist in the dictionary for the given area. Check for misspelling.
Module:
ADSOGDAB
Severity:
0
Reason:
The set or area name specified in the WITHIN clause of a FIND command does not exist in the dictionary. Check for misspelling.
Module:
ADSOGDAB
Severity:
0
Reason:
The record name could not be validated. An invalid return code was returned by the ADSOGNPR program. This is a system internal error. Print the dump and contact Technical Support.
Module:
ADSOGDAB
Severity:
3
Reason:
The record specified in the database command does not exist in the data dictionary. Check for a misspelled record name.
Module:
ADSOGDAB
Severity:
0
Reason:
The record specified in the database command must comply with both of the following rules:
Module:
ADSOGDAB
Severity:
0
Reason:
The specified operation for the set cannot be performed. The operation conflicts with the operations that are allowed for the set in the subschema definition.
Module:
ADSOGDAB
Severity:
0
Reason:
The specified set does not belong to the subschema specified for the dialog. Check for a misspelled set name.
Module:
ADSOGDAB
Severity:
0
Reason:
The specified record does not exist in the dictionary in the given set. Check for misspelling.
Module:
ADSOGDAB
Severity:
0
Reason:
Indexed or sorted retrieval cannot be performed for this set. The set name is not defined as an indexed or sorted set in the dictionary.
Module:
ADSOGDAB
Severity:
0
Reason:
The specified area does not exist for the dialog. Check for misspelling.
Module:
ADSOGDAB
Severity:
0
Reason:
The set name could not be validated because the ADSOGNDB program returned an invalid error code. This is a system internal error. Print the dump and contact Technical Support.
Module:
ADSOGDAB
Severity:
3
Reason:
An operation requested for a record cannot be performed. The operation conflicts with the operations allowed for the record in the subschema definition.
Module:
ADSOGDAB
Severity:
0
Reason:
The variable that contains the db-key was not a full word binary number. All database keys are full word binary numbers.
Module:
ADSOGDAB
Severity:
0
Reason:
The variable in the FIND command that contains the sequence data field was not numeric. A numeric data field is required since the FIND command requests a specific occurrence of the record within the set.
Module:
ADSOGDAB
Severity:
0
Reason:
The length of the SORT-key must not exceed 256 bytes.
Module:
ADSOGDAB
Severity:
0
Reason:
A record cannot participate in more than one logical record used by the dialog.
Module:
ADSOGDAB
Severity:
0
Reason:
The variable for the area, set, or record name does not exist in the dictionary.
Module:
ADSOGDAB
Severity:
0
Reason:
An invalid function for the logical record was requested. The following functions are valid for logical records:
Module:
ADSOGDAB
Severity:
0
Reason:
The specified record name identifies a logical record; however, logical record processing is not allowed for the subschema specified for the dialog.
Module:
ADSOGDAB
Severity:
0
Reason:
Database commands within a dialog are invalid unless a subschema name has been specified.
Module:
ADSOGDAB
Severity:
0
Reason:
The quoted string that represents the status code in the ALLOWING ERROR CODE clause contains nonnumeric characters.
Module:
ADSOGDAB
Severity:
0
Reason:
An error code found in the ALLOWING ERROR CODES clause does not match any level-88 error codes in the autostatus record.
Module:
ADSOGDAB
Severity:
0
Reason:
The record element name could not be validated and an invalid code was returned by ADSOGNRC. This is a system internal error. Print the dump and contact Technical Support.
Module:
ADSOGDAB
Severity:
3
Reason:
The name found in the ALLOWING ERROR CODES clause does not match any level-88 names in the status definition record.
Module:
ADSOGDAB
Severity:
0
Reason:
The ALLOWING ERROR CODES clause is valid only if AUTOSTATUS is set to YES in the dialog definition.
Module:
ADSOGDAB
Severity:
0
Reason:
The literal string for a command must conform to the rules:
If these conditions are true for the given string, contact Technical Support.
Module:
ADSOGDAB
Severity:
0
Reason:
The parsed data field name does not exist in the data dictionary. The data field name also does not exist as a valid function invocation name since there is not master function table in the load area. Either of the following problems can cause this error:
Module:
ADSOGMIS
Severity:
0
Reason:
The parsed data field name does not exist in the data dictionary. The data field name also does not exist as a valid function invocation name since there is not master function table in the load area. Either of the following problems can cause this error:
Module:
ADSOGMIS
Severity:
0
Reason:
The procedure name specified in the BIND PROCEDURE command must be an EBCDIC or GROUP data type field.
Module:
ADSOGDAB
Severity:
0
Reason:
An incorrect control command was entered. Supply either of the following valid keywords:
Module:
ADSOGCTL
Severity:
0
Reason:
No literals were found after the TEXT IS clause. The TEXT IS clause is ignored unless the clause includes a text string.
Module:
ADSOGCTL
Severity:
0
Reason:
The variable specified as the message code is not a valid number or a valid variable data field. Valid numbers have a minimum and maximum length of six digits.
Module:
ADSOGCTL
Severity:
0
Reason:
The parameter list must begin with a left parenthesis. The CA ADS dialog compiler assumes that a left parenthesis is located at the beginning of the parameter list. The dialog cannot be compiled until the parameter list begins with a left parenthesis.
Module:
ADSOGCTL
Severity:
0
Reason:
The parameter list must end with a right parenthesis. The CA ADS dialog compiler assumes a right parenthesis is located at the beginning of the parameter list. The dialog cannot be compiled successfully until a right parenthesis ends the parameter list.
Module:
ADSOGCTL
Severity:
0
Reason:
The variable specified as a dialog name in the LINK TO command was missing or was not found in the dictionary as a dialog. Check for misspelling or correct the dialog name.
Module:
ADSOGCTL
Severity:
0
Reason:
The variable specified as the program name in the LINK TO command was missing or was not found in the dictionary as a program. Check for misspelling and/or correct the program name.
Module:
ADSOGCTL
Severity:
0
Reason:
The left parenthesis following the USING keyword in the LINK TO command was not found. The process will not compile successfully until the record list is enclosed in parentheses.
Module:
ADSOGCTL
Severity:
0
Reason:
The right parenthesis following the USING clause in the LINK TO command was not found. The process will not compile successfully until the record list is enclosed in parentheses.
Module:
ADSOGCTL
Severity:
0
Reason:
The NEXT clause cannot be evaluated successfully. The parameter that specifies the dialog name is invalid for either of the following reasons:
Specify a dialog name in quotes, or code a valid field name. A field name cannot be longer than eight characters.
Module:
ADSOGCTL
Severity:
0
Reason:
The destination specified following the RETURN command either was invalid or was not found in the dictionary.
Module:
ADSOGCTL
Severity:
0
Reason:
The variable that specifies the data name (as a replacement parameter) either was missing or was not known to any record of the dialog.
Module:
ADSOGCTL
Severity:
0
Reason:
In parsing the WRITE TRANSACTION command, the keyword TO was found, but the keyword SUSPENSE did not follow it. Therefore, the parser ignored the TO keyword and continued to parse the command. The dialog cannot be recompiled until this error is corrected.
Module:
ADSOGCTL
Severity:
0
Reason:
When linking to a dialog, the only records that can be passed in the USING record list are SUBSCHEMA-CONTROL or MAP-CONTROL. Alternative spellings are SUBSCHEMA_CONTROL or MAP_CONTROL. Correct the spelling or remove the invalid record from the list.
Module:
ADSOGCTL
Severity:
0
Reason:
A control command was incomplete (possibly due to a missing period); therefore the end-of-file was encountered before the end of the statement.
Module:
ADSOGCTL
Severity:
0
Reason:
An unrecognizable keyword was found during parsing of the command.
Module:
ADSOGCTL
Severity:
0
Reason:
The LINK command contains an invalid keyword. Check the control commands in the CA ADS Reference Guide.
Module:
ADSOGCTL
Severity:
0
Reason:
The LEAVE command contains an invalid keyword. Check the control commands in the CA ADS Reference Guide.
Module:
ADSOGCTL
Severity:
0
Reason:
The variable specified as the dialog name in the INVOKE command was missing or was not found in the dictionary as a dialog.
Module:
ADSOGCTL
Severity:
0
Reason:
The keyword following the dialog name in an INVOKE command was unrecognizable.
Module:
ADSOGCTL
Severity:
0
Reason:
The RETURN command contains an invalid keyword. Check the control commands in the CA ADS Reference Guide.
Module:
ADSOGCTL
Severity:
0
Reason:
The dialog name was missing, or the variable that specifies the dialog name in the TRANSFER command was not found in the dictionary. The CA ADS dialog compiler aborted.
Module:
ADSOGCTL
Severity:
0
Reason:
The keyword that follows the dialog name in the TRANSFER command is unrecognizable.
Module:
ADSOGCTL
Severity:
0
Reason:
An unsupported control command was entered; the CA ADS dialog compiler aborted.
Module:
ADSOGCTL
Severity:
3
Reason:
The program took a wrong branch while the CA ADS dialog compiler parsed the control command. This is an internal error.
Module:
ADSOGCTL
Severity:
3
Reason:
An internal error occurred when the parse stack overflowed in the CA ADS dialog compiler. Obtain more storage for the stack.
Module:
ADSOGCTL
Severity:
3
Reason:
The record name specified was not known to the dialog. Check for misspelling. Also verify that the record has been defined either to the dialog or to the associated map.
Module:
ADSOGCTL
Severity:
0
Reason:
The RETURN destination has already been specified; the second reference is ignored.
Module:
ADSOGCTL
Severity:
0
Reason:
An error was detected while the CA ADS dialog compiler was building the DISPLAY command element (CME). The MESSAGE parameter already was specified for the command. The remainder of the statement is flushed. The GCM (header portion of the CME) is built.
Module:
ADSOGCTL
Severity:
0
Reason:
There is an error in a DISPLAY command with a MESSAGE CODE clause. The replacement parameter specified in the PARMS clause is invalid. The replacement parameter must be specified in either of the following forms:
A group-level data field cannot be used as a replacement parameter.
Module:
ADSOGDIS
Severity:
0
Reason:
An error occurred while the CA ADS dialog compiler was building a command element (CME). The replacement parameter data length exceeded the maximum length of 256 bytes. The statement is flushed. The GCM (header portion of the CME) is built. Correct the data length.
Module:
ADSOGCTL
Severity:
0
Reason:
An error occurred while the CA ADS dialog compiler was building a command element (CME). No replacement parameters were specified. The statement is flushed. The GCM (header portion of the CME) is built. Enter valid parameters.
Module:
ADSOGCTL
Severity:
0
Reason:
An error occurred while the CA ADS dialog compiler was building a command element (CME). There can be up to nine replacement parameters.
Module:
ADSOGCTL
Severity:
0
Reason:
A valid dialog/program name must begin with an alphabetic character or with one of the following characters: @, #, $. Any other character in the first position of the dialog/program name results in an error.
Module:
ADSOGCTL
Severity:
0
Reason:
The MAP-CONTROL is valid in the LINK TO command only if the invoking dialog contains a map. Remove the MAP-CONTROL or associate a map with the dialog.
Module:
ADSOGCTL
Severity:
0
Reason:
The SUBSCHEMA-CONTROL is valid in the LINK TO command only if the invoking dialog contains a subschema.
Module:
ADSOGCTL
Severity:
0
Reason:
The variable that specifies the dialog/program name in the LINK TO command either was not in EBCDIC characters or was not the correct length (eight bytes).
Module:
ADSOGCTL
Severity:
0
Reason:
Nonnumeric data was entered for the MESSAGE CODE in the command. Enter numeric data for the MESSAGE CODE.
Module:
ADSOGCTL
Severity:
0
Reason:
The DISPLAY command is invalid in a mapless dialog. A map must be associated with this dialog before the command can be parsed without errors.
Module:
ADSOGCTL
Severity:
0
Reason:
An error occurred when a dialog name, message parameter, or message text was being added to the literal pool. This is an internal error. Contact Technical Support.
Module:
ADSOGCTL
Severity:
0
Reason:
The ABORT command was specified incorrectly. Check the syntax for the ABORT command and correct any errors. For more information about the syntax rules, see the CA ADS Reference Guide.
Module:
ADSOGCTL
Severity:
0
Reason:
The CONTINUE parameter cannot be used with the ERASE option.
Module:
ADSOGCTL
Severity:
0
Reason:
The MESSAGE parameter cannot be used with the ERASE option.
Module:
ADSOGCTL
Severity:
0
Reason:
The map-control record cannot be passed to the user program in a LINK command. Mapping services are not available for batch dialogs.
Module:
ADSOGCTL
Severity:
0
Reason:
The WRITE TRANSACTION command without the CONTINUE or RETURN option will cause an implicit READ to occur. Therefore, any dialog issuing such a command must have an input map associated with it. If no input map is desired, then all WRITE TRANSACTION commands must have either the CONTINUE or RETURN option included.
Module:
ADSOGCTL
Severity:
0
Reason:
CA ADS/Batch will allow any IBM operating system supported return code. The supported return codes are from 0 through 4095 and are usually multiples of 4 - for example, 0, 4, 8, 12, 16, and so on.
Module:
ADSOGCTL
Severity:
0
Reason:
Statement or expanded restatement of condition. The LU-NAME parameter must be either a literal string or a variable field with a maximum of eight bytes.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. The MODE-NAME parameter must be either a literal string or a variable field with a maximum length of eight bytes.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. The only valid SECURITY parameters are: NONE, SAME, or PGM.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. SECURITY PGM must be followed by USER-ID user-id and then PASSWORD password.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. Either the USER-ID or PASSWORD parameter is invalid. USER-ID must be either a literal or variable field with a maximum length of 32 bytes. PASSWORD must be either a literal string or a variable field with a maximum length of eight bytes.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. The only valid SYNC-LEVEL parameters are NONE or CONFIRM.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. There is a syntax error in the LOCAL VERSION clause. It must read: LOCAL VERSION local-version-vq.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. The local version parameter may be either a literal string or a variable field with a maximum of 32 bytes.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. There is a syntax error in the REMOTE VERSION clause. It must read: REMOTE VERSION remote-version-v.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. The REMOTE VERSION parameter must be a variable field with a minimum length of 32 bytes.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. The CA ADS compiler was expecting a period to mark the statement end but none was found.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. The CA ADS compiler found end-of-file before it found the expected end of the statement.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. The LU-NAME parameter is required but it was not provided. Provide an LU-NAME parameter.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. The TPN parameter must be either a literal string or a variable field with a maximum length of 8 bytes.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. The TPN parameter is required. Since one was not provided, please provide one.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. The CONTROL SESSION statement contains invalid syntax. It must begin: CONTROL SESSION.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. The SEND-DATA command must have a record or field name provided as its argument. Provide a record or field name.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. An invalid option has been specified on the PREPARE-TO-RECEIVE command. For more information about the allowable options, see the CA ADS Reference Guide.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. An invalid option has been specified on the DEALLOCATE command. For more information about the valid options, see the CA ADS Reference Guide.
Module:
ADSOGPPC
Severity:
0
Reason:
A SEND dataname command is coded with a data name that is not defined in any of the records associated with the dialog; or the element has a picture that is not valid for a field used in an OSCaR command. Correct the spelling of the data name, add the missing record to the dialog, or move the data to a field that has an acceptable picture clause in its definition.
Module:
ADSOGPPC
Severity:
0
Reason:
A RECEIVE dataname command is coded with a data name that is not defined in any of the records associated with the dialog; or the element has a picture that is not valid for a field used in an OSCaR command. Correct the spelling of the data name, add the missing record to the dialog, or move the data to a field that has an acceptable picture clause in its definition.
Module:
ADSOGPPC
Severity:
0
Reason:
An OPEN command was coded with a TRANSACTION parameter followed by a data name that is not in any of the records associated with the dialog. Correct the spelling of the data name, or add the missing record to the dialog.
Module:
ADSOGPPC
Severity:
0
Reason:
An OPEN command was coded with a SECURITY parameter followed by a data name that is not in any of the records associated with the dialog. Correct the spelling of the data name, or add the missing record to the dialog.
Module:
ADSOGPPC
Severity:
0
Reason:
An OPEN command was coded with a PASSWORD parameter followed by a data name that is not in any of the records associated with the dialog. Correct the spelling of the data name, or add the missing record to the dialog.
Module:
ADSOGPPC
Severity:
0
Reason:
When keyword LU-NAME is coded in an OPEN command it must be followed by keyword TRANSACTION.
Module:
ADSOGPPC
Severity:
0
Reason:
Keyword CONVERSATION must follow every OPEN and CLOSE command.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. The end of the process file was encountered before the end of the current statement. For more information about the correct syntax, see the CA ADS Reference Guide.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. The indicated variable field is of either an invalid data type or length. For more information about the limitations for this parameter, see the CA ADS Reference Guide.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. The name does not follow the proper conventions. A name must begin with @, $, #, or an alphabetic character.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. The length of the user-supplied literal is invalid. For more information about this parameter, see the CA ADS Reference Guide.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. The input node in the parse tree is in error. This is a system internal error. Contact Technical Support.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. The terminal node is in error. This is a system internal error. Contact Technical Support.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. The CA ADS compile has run out of room on its internal stack. This is a system internal error. Contact Technical Support.
Module:
ADSOGPPC
Severity:
0
Reason:
Statement or expanded restatement of condition. The option of LOCAL VERSION and REMOTE VERSION may be used only with the FORMAT option. They may not be selected when NOFORMAT is being used.
Module:
ADSOGPPC
Severity:
0
Reason:
An APPC command such as ALLOCATE, CONFIRM, SEND-ERROR was encountered in a dialog that has a previous OSCaR command such as OPEN or CLOSE. APPC and OSCaR commands are mutually exclusive within a single dialog.
Module:
ADSOGPPC
Severity:
0
Reason:
An OSCaR command such as OPEN, SEND, CLOSE or RECEIVE was encountered in a dialog that has a previous APPC command such as ALLOCATE or SEND-DATA. APPC and OSCaR commands are mutually exclusive within a single dialog.
Module:
ADSOGPPC
Severity:
0
Reason:
A logical record was specified as the operand of a SEND-DATA or RECEIVE-AND-WAIT command. Only individual records or data fields are valid as Send/Receive operands. Create a work record which can hold all of the fields in the logical record that you want to Send or Receive. Move the data from the logical record to the work record and specify the name of the work record on the SEND-DATA or RECEIVE-AND-WAIT command.
Module:
ADSOGFD1
Severity:
0
Reason:
The record specified as the operand of a SEND-DATA or RECEIVE-AND-WAIT command is not valid for these commands for one of the following reasons:
Modify or restructure the specified record to conform to the restrictions given above.
If the invalid fields are ones which do not actually need to be sent or received, create a work record which can accommodate all of the fields in the specified record except for the invalid ones. Move the valid fields from the specified record to the corresponding fields in the work record and specify the work record on the SEND-DATA or RECEIVE-AND-WAIT command.
If the problem is invalid data types, one can move the invalid fields to work fields with valid types in a work record (with CA ADS performing the necessary type conversions) and specify the work record on the SEND-DATA or RECEIVE-AND-WAIT command.
Module:
ADSOGFD1
Severity:
0
Reason:
The GRD and/or GRE address(es) passed to ADSOGFD1 are0 or do not point to a valid GRD or GRE. A snap dump of the task appears with this message. This is an internal logic error. Contact Technical Support.
Module:
ADSOGFD1
Severity:
3
Reason:
The individual or group field specified as the operand of a SEND-DATA or RECEIVE-AND-WAIT command is not valid for these commands for one of the following reasons:
Modify or restructure the individual or group field to conform to the restrictions given above. Alternatively, if the problem is with data types, one can move the invalid fields to work fields with valid types (with CA ADS performing the necessary type conversions) and Send or Receive the work fields.
Module:
ADSOGFD1
Severity:
0
Reason:
The total size of the FDE structure for the record or group specified on a SEND-DATA or RECEIVE-AND-WAIT command would exceed 32767 which is the maximum allowable size. Break the record or group into pieces and Send or Receive the pieces separately.
Module:
ADSOGFD1
Severity:
0
Reason:
An error has been found in one of the following operands:
The operand (variable or parameter) was either missing or invalid.
Module:
ADSOGASG
Severity:
0
Reason:
Either of the following situations caused this error:
Module:
ADSOGASG
Severity:
0
Reason:
All arithmetic/assignment commands must end with a period.
Module:
ADSOGASG
Severity:
0
Reason:
The expression in the COMPUTE command is invalid or missing. The expression must be one of the following:
Module:
ADSOGASG
Severity:
0
Reason:
The assignment statement was not complete; therefore, the end-of-file was encountered before the end of the statement.
Module:
ADSOGASG
Severity:
0
Reason:
A bad node was passed to the ADSOGASG program from the called program. This is a system internal error.
Module:
ADSOGASG
Severity:
3
Reason:
This message exists in the program but is not referenced by it.
Module:
ADSOGASG
Severity:
3
Reason:
The internal parse stack has overflowed. This is an internal error. To acquire storage for the stack, contact Technical Support.
Module:
ADSOGASG
Severity:
3
Reason:
During an attempt to build the expression description element (XDE), the CA ADS dialog compiler encountered an invalid data type or data size in the arithmetic/assignment command.
Module:
ADSOGASG
Severity:
0
Reason:
The CA ADS dialog compiler could not acquire storage to build an XDE stack for a third assignment command variable. Register 5 contains the return code. For more information about GETSTG return codes, see the CA IDMS DML Reference Guide for Assembler.
Module:
ADSOGASG
Severity:
3
Reason:
An error occurred while the CA ADS compiler was acquiring storage for an extra expression description element (XDE). The XDE is needed to complete an XDE stack for a COBOL-compatible edited move. Register 4 contains the return code. For more information about GETSTG return codes, see the CA IDMS DML Reference Guide for Assembler.
Print the snap dump and contact Technical Support if the return code does not suggest an easy solution to the problem.
Module:
ADSOGASG
Severity:
3
Reason:
A high return code was received from the routine that adds literals to the litpool and applies to the mask literal created by RHDCEVAL for a COBOL-compatible edited move. This is a system internal error. Contact Technical Support.
Module:
ADSOGASG
Severity:
0
Reason:
Two or more data elements referenced in an XDE stack for a COBOL-compatible edited move cannot be compared, moved, or converted. This is an internal error. Print the snap dump before calling Technical Support.
Module:
ADSOGASG
Severity:
3
Reason:
Data conversion from EBCDIC to numeric was required to evaluate an expression; however, the data element to be converted in the XDE stack for a COBOL-compatible edited move did not contain a number. This is an internal error. Print the snap dump. Contact Technical Support.
Module:
ADSOGASG
Severity:
3
Reason:
The target field on an assignment or arithmetic command is not large enough to hold the result of a COBOL-compatible edited move. This is an internal error. Print the snap dump. Contact Technical Support.
Module:
ADSOGASG
Severity:
3
Reason:
The value used as a subscript for a subscripted field is invalid for either of the following reasons:
The subscript value was not sufficiently validated by the process or by automatic editing prior to using it as a subscript for the field. Correct the dialog and/or map so that adequate subscript validation is performed.
Module:
ADSOGASG
Severity:
3
Reason:
Automatic data conversion has failed. The source field does not contain a valid date in a COBOL-compatible edited move. This is an internal error. Print the snap dump. Contact Technical Support.
Module:
ADSOGASG
Severity:
3
Reason:
This message is issued when a COBOL-edited move fails. One of the data exceptions defined in IBM/360 or IBM/370 system documentation has occurred during the evaluation of an expression. This is an internal error. Print the snap dump. Contact Technical Support.
Module:
ADSOGASG
Severity:
3
Reason:
One of the data exceptions defined in IBM/360 or IBM/370system documentation has occurred during the evaluation of an expression of a COBOL-compatible edited move. This is an internal error. Print the snap dump. Contact Technical Support.
Module:
ADSOGASG
Severity:
3
Reason:
A decimal overflow exception defined in IBM/360 or IBM/370system documentation has occurred during the evaluation of an expression of a COBOL-compatible edited move. This is an internal error. Print the dump before calling for assistance from Technical Support.
Module:
ADSOGASG
Severity:
3
Reason:
A divide exception defined in IBM/360 or IBM/370 system documentation has occurred during the evaluation of an expression of a COBOL-compatible edited move. The divisor is zero. This is an internal error. Print the dump. Contact Technical Support.
Module:
ADSOGASG
Severity:
3
Reason:
A decimal overflow exception defined in IBM/360 or IBM/370 system documentation has occurred during the evaluation of an expression of a COBOL-compatible edited move. This is an internal error. Print the dump. Contact Technical Support.
Module:
ADSOGASG
Severity:
3
Reason:
A divide exception defined in IBM/360 or IBM/370 system documentation has occurred during the evaluation of an expression of a COBOL-compatible edited move. The divisor is zero. This is an internal error. Print the dump. Contact Technical Support.
Module:
ADSOGASG
Severity:
3
Reason:
RHDCEVAL does not support the requested operation in the evaluation of an expression in a COBOL-compatible edited move. This is an internal error. Print the dump. Contact Technical Support.
Module:
ADSOGASG
Severity:
3
Reason:
A floating point divide exception defined in IBM/360 or IBM/370 system documentation has occurred during the evaluation of an expression of a COBOL-compatible edited move. This is an internal error. Print the dump. Contact Technical Support.
Module:
ADSOGASG
Severity:
3
Reason:
An exponent overflow exception defined in the IBM/360 or the IBM/370 system documentation occurred during the evaluation of an expression in a COBOL-compatible edited move. This is an internal error. Print the dump. Contact Technical Support.
Module:
ADSOGASG
Severity:
3
Reason:
An exponent underflow exception defined in the IBM/360 or the IBM/370 system documentation occurred during the evaluation of an expression in a COBOL-compatible edited move. This is an internal error. Print the dump. Contact Technical Support.
Module:
ADSOGASG
Severity:
3
Reason:
A significance exception defined in the IBM/360 or the IBM/370 system documentation occurred during the evaluation of an expression in a COBOL-compatible edited move. This is an internal error. Print the dump. Contact Technical Support.
Module:
ADSOGASG
Severity:
3
Reason:
RHDCEVAL could not properly interpret the XDE stack. This is probably an internal error. Print the snap dump. Contact Technical Support.
Module:
ADSOGASG
Severity:
3
Reason:
The length of the current multi-bit binary (USAGE BIT) field is found to be in an assignment command and has a length greater than 32 bits or 4 bytes. A maximum of four bytes is supported.
Severity:
0
Module:
ADSOGASG
Reason:
An error occurred while the CA ADS compiler was acquiring storage for an expression description element (XDE). The XDE is needed to complete the XDE stack for a COBOL-compatible edited move. Register 4 contains the return code. See the CA IDMS DML Reference Guide for Assembler for an explanation of GETSTG return codes.
Print the snap dump and contact Technical Support if the return code does not suggest an easy solution to the problem.
Module:
ADSOGASG
Severity:
3
Reason:
The MODIFY MAP command contains a syntax error in either of the following specifications:
Correct the syntax and recompile the process. For more information about syntax rules, see the CA ADS Reference Guide.
Module:
ADSOGMAP
Severity:
0
Reason:
The statement terminator was not found for either the MODIFYMAP or MAP ATTRIBUTE statement. Correct the syntax and recompile the process. For more information about syntax rules, see the CA ADS Reference Guide.
Module:
ADSOGMAP
Severity:
0
Reason:
The MAP ATTRIBUTE command or the MAP MODIFY command was the last recognized command in the process. The command was not terminated with a period. For more information about syntax rules, see the CA ADS Reference Guide.
Module:
ADSOGMAP
Severity:
0
Reason:
The map field name specified in a MODIFY MAP command does not identify a field on the map that is defined to this dialog. Check the spelling of the map field name by using the online mapping facility. For more information, see the CA IDMS Mapping Facility Guide and the CA ADS Reference Guide.
Module:
ADSOGMAP
Severity:
0
Reason:
The map-field-name is a required parameter for certain uses of the MODIFY MAP command
For example, an explicit map-field-name is required for the CURSOR AT clause when that clause does not specify coordinates to identify a map field. Correct the syntax and recompile the process. For more information about MODIFY MAP syntax, see the CA ADS Reference Guide.
Module:
ADSOGMAP
Severity:
0
Reason:
The keyword FIELDS is a required keyword in certain forms of the MODIFY MAP command. For example, FIELDS is required in the following command:
MODIFY MAP FOR ALL CORRECT FIELDS
Correct the syntax and recompile the process. For more information about MODIFY MAP syntax, see the CA ADS Reference Guide.
Module:
ADSOGMAP
Severity:
0
Reason:
The keyword DATA is required in certain uses of the MODIFYMAP command. For example, DATA is required in the following command:
MODIFY MAP OUT DATA IS YES
Correct the syntax and recompile the process. For more information about MODIFY MAP syntax, see the CA ADS Reference Guide.
Module:
ADSOGMAP
Severity:
0
Reason:
One of the following parameters must be specified for an OUTPUT DATA clause in a MODIFY MAP command:
Correct the syntax and recompile the process. For more information about MODIFY MAP syntax, see the CA ADS Reference Guide.
Module:
ADSOGMAP
Severity:
0
Reason:
Either YES or NO must be specified for the INPUT DATA clause of a MODIFY MAP command. Correct the syntax and recompile the process. For more information about MODIFY MAP syntax, see the CA ADS Reference Guide.
Module:
ADSOGMAP
Severity:
0
Reason:
The keyword JUSTIFY is required in certain forms of the MODIFY MAP command. For example, JUSTIFY is required in the following command:
MODIFY MAP RIGHT JUSTIFY
Correct the syntax and recompile the process. For more information about MODIFY MAP syntax, see the CA ADS Reference Guide.
Module:
ADSOGMAP
Severity:
0
Reason:
Either CORRECT or ERROR must be specified for the EDIT IS clause of a MODIFY MAP command. Correct the syntax and recompile the process. For more information about MODIFY MAP syntax, see the CA ADS Reference Guide.
Module:
ADSOGMAP
Severity:
0
Reason:
An invalid keyword was parsed in the CLOSE MAP command. Correct the syntax and recompile the process. Syntax for the CLOSE command is provided in the &UIDDBT..
Module:
ADSOGMAP
Severity:
0
Reason:
The keyword MESSAGE is required in certain forms of the MODIFY MAP command. For example, MESSAGE is required in the following command:
MODIFY MAP ERROR MESSAGE IS SUPPRESS
Correct the syntax and recompile the process. For more information about MODIFY MAP syntax, see the CA ADS Reference Guide.
Module:
ADSOGMAP
Severity:
0
Reason:
Either ACTIVE or SUPPRESS must be specified for the ERROR MESSAGE clause of a MODIFY MAP command. Correct the syntax and recompile the process. For more information about MODIFY MAP syntax, see the CA ADS Reference Guide.
Module:
ADSOGMAP
Severity:
0
Reason:
The node branch value passed to ADSOGMAP module is beyond the range of the node tree in this module. This is an internal error and probably masks another problem. Print the snap dump and contact the database administrator.
Module:
ADSOGMAP
Severity:
3
Reason:
The internal branch code in one of the nodes has a value that exceeds the values in the branch table in the ADSOGMAP module. This may mask a more serious problem. Print the snap dump and contact the database administrator.
Module:
ADSOGMAP
Severity:
3
Reason:
When the CA ADS dialog compiler compiles a process, it issues many #ACALL macros that cause registers to be saved in an internal stack area in the parser work space area (PSA). The capacity of the internal area has been exceeded during the execution of the ADSOGMAP module. This space is used up rapidly by process code with complex conditions and deeply embedded conditional statements. Print the snap dump and contact the database administrator.
Module:
ADSOGMAP
Severity:
3
Reason:
More than one FOR clause was found in the same MODIFY MAP command. Check for typographical errors. For more information about MODIFY MAP command syntax, see the CA ADS Reference Guide. Correct the syntax and recompile the process.
Module
ADSOGMAP
Severity:
0
Reason:
More than one ATTRIBUTE clause was found in the same MODIFY MAP command. Check for typographical errors. For more information about MODIFY MAP command syntax, see the CA ADS Reference Guide. Correct the syntax and recompile the process.
Module:
ADSOGMAP
Severity:
0
Reason:
More than one CURSOR clause was found in the MODIFY MAP command. For more information about MODIFY MAP command syntax, see the CA ADS Reference Guide. Correct the syntax and recompile the process.
Module:
ADSOGMAP
Severity:
0
Reason:
More than one WCC clause was found in the MODIFY MAP command. For more information about MODIFY MAP command syntax, see the CA ADS Reference Guide. Correct the syntax and recompile the process.
Module:
ADSOGMAP
Severity:
0
Reason:
The keyword WCC was found twice in the MODIFY MAP command. For more information about MODIFY MAP command syntax, see the CA ADS Reference Guide. Correct the syntax and recompile the process.
Module:
ADSOGMAP
Severity:
0
Reason:
Parameters in the MODIFY MAP command conflict with the WCC specification
Correct the syntax and recompile the process. For more information about MODIFY MAP syntax, see the CA ADS Reference Guide.
Module:
ADSOGMAP
Severity:
0
Reason:
The INPUT keyword was found twice in the MODIFY MAP command. Correct the syntax and recompile the process. For more information about MODIFY MAP command syntax, see the CA ADS Reference Guide.
Module:
ADSOGMAP
Severity:
0
Reason:
Parameters in the MODIFY MAP command conflict with the INPUT specification
Correct and recompile the process. For more information about MODIFY MAP syntax, see the CA ADS Reference Guide.
Module:
ADSOGMAP
Severity:
0
Reason:
The EDIT keyword was found twice in the MODIFY MAP command. For more information about MODIFY MAP command syntax, see the CA ADS Reference Guide. Check for typographical errors. Correct the syntax and recompile the process.
Module:
ADSOGMAP
Severity:
0
Reason:
Parameters in the MODIFY MAP command conflict with the EDIT specification
Correct and recompile the process
For more information about MODIFY MAP syntax, see the CA ADS Reference Guide.
Module:
ADSOGMAP
Severity:
0
Reason:
The OUTPUT keyword was found twice in the MODIFY MAP command. For more information about MODIFY MAP command syntax, see the CA ADS Reference Guide. Correct the syntax and recompile the process.
Module:
ADSOGMAP
Severity:
0
Reason:
Parameters in the MODIFY MAP command conflict with the OUTPUT specification
Correct and recompile the process. For more information about MODIFY MAP syntax, see the CA ADS Reference Guide.
Module:
ADSOGMAP
Severity:
0
Reason:
The ATTRIBUTE parameter was found twice in the MODIFY MAP command. For more information about MODIFY MAP command syntax, see the CA ADS Reference Guide. Correct the syntax and recompile the process.
Module:
ADSOGMAP
Severity:
0
Reason:
Parameters in the MODIFY MAP command conflict with the ATTRIBUTE specification
Correct and recompile the process. For more information about MODIFY MAP syntax, see the CA ADS Reference Guide.
Module:
ADSOGMAP
Severity:
0
Reason:
The PAD/NOPAD keyword was found twice in the MODIFY MAP command. For more information about MODIFY MAP command syntax, see the CA ADS Reference Guide. Correct the syntax and recompile the process.
Module:
ADSOGMAP
Severity:
0
Reason:
Parameters in the MODIFY MAP command conflict with the PAD/NOPAD specification
Correct and recompile the process. For more information about MODIFY MAP syntax, see the CA ADS Reference Guide.
Module:
ADSOGMAP
Severity:
0
Reason:
The REQUIRED/OPTIONAL keyword was found twice in the MODIFY MAP command. For more information about MODIFY MAP command syntax, see the CA ADS Reference Guide. Correct the syntax and recompile the process.
Module:
ADSOGMAP
Severity:
0
Reason:
Parameters in the MODIFY MAP command conflict with the REQUIRED/OPTIONAL specification. Correct and recompile the process. For more information about MODIFY MAP syntax rules, see the CA ADS Reference Guide.
Module:
ADSOGMAP
Severity:
0
Reason:
The BACKSCAN/NOBACKSCAN keyword was found twice in the MODIFY MAP command. For more information about MODIFY MAP command syntax, see the CA ADS Reference Guide. Correct the syntax and recompile the process.
Module:
ADSOGMAP
Severity:
0
Reason:
Parameters in the MODIFY MAP command conflict with the BACKSCAN/NOBACKSCAN specification. Correct and recompile the process. For more information about MODIFY MAP syntax rules, see the CA ADS Reference Guide.
Module:
ADSOGMAP
Severity:
0
Reason:
The CURSOR parameter was in row/column format; however, the row data field was not numeric. Make sure the row/column parameter was not omitted and contains valid numeric characters. Correct the syntax and recompile the process.
Module:
ADSOGMAP
Severity:
0
Reason:
The CURSOR parameter was in row/column format; however, the column data field was not numeric. Make sure the column data field was not omitted and contains valid numeric characters. Correct the syntax and recompile the process.
Module:
ADSOGMAP
Severity:
0
Reason:
The PAD option in the MODIFY MAP command contains an invalid character defined as the pad character. The character must be a legal EBCDIC character. Refer to the CA IDMS Mapping Facility Guide for restrictions on this parameter. Correct the syntax and recompile the process.
Module:
ADSOGMAP
Severity:
0
Reason:
Check for a duplicate or conflicting keyword in a MODIFY MAP statement. Contact Technical Support to report this message.
The #ASET macro of the ADSOGMAP module is missing one or both of the following parameters:
Module:
ADSOGMAP
Severity:
0
Reason:
The ERROR MESSAGE keyword was found twice in the MODIFY MAP command. Refer to the CA ADS Reference Guide for an explanation of MODIFY MAP command syntax. Check for typing errors. Correct the syntax and recompile the process.
Module:
ADSOGMAP
Severity:
0
Reason:
Parameters in the MODIFY MAP command conflict with the ERRORMESSAGE specification. Correct and recompile the process. For more information about MODIFY MAP syntax, see the CA ADS Reference Guide.
Module:
ADSOGMAP
Severity:
0
Reason:
A missing left parenthesis in the record list in the SNAP command caused a syntax error. The record list must be placed within parentheses.
Module:
ADSOGMIS
Severity:
0
Reason:
A missing right parenthesis in the record list in the SNAP command caused a syntax error. The record list must be placed within parentheses.
Module:
ADSOGMIS
Severity:
0
Reason:
The SNAP command specifies a TITLE option. The title text was not given.
Module:
ADSOGMIS
Severity:
0
Reason:
No period character (.) was found to terminate one of the following types of commands:
Module:
ADSOGMIS
Severity:
0
Reason:
The required ID keyword was missing from either an ACCEPT utility command or a scratch/queue management command.
Module:
ADSOGMIS
Severity:
0
Reason:
The required keyword SIZE was not found in an ACCEPT SCREENSIZE utility command.
Module:
ADSOGMIS
Severity:
0
Reason:
The required keyword DIALOG was not found in an ACCEPT HIGHERDIALOG NAME utility command.
Module:
ADSOGMIS
Severity:
0
Reason:
One of the following situations has occurred:
For more information about the syntax rules, see the CA ADS Reference Guide.
Module:
ADSOGMIS
Severity:
0
Reason:
An ACCEPT ERROR utility command must be followed by one of the following keywords: SET, RECORD, or AREA. Check the syntax for the ACCEPT ERROR utility command.
Module:
ADSOGMIS
Severity:
0
Reason:
The expected keyword INTO was not found in one of the following commands:
For more information about the syntax rules, see the CA ADS Reference Guide.
Module:
ADSOGMIS
Severity:
0
Reason:
An error has been found in a scratch/queue command, utility command, or KEEP LONGTERM command. One of the following conditions exists:
Check the spelling of records and record elements; rules are provided in the CA ADS Reference Guide.
Module:
ADSOGMIS
Severity:
0
Reason:
Either of the following parameters must be specified for a KEEP LONGTERM command:
The keywords specify which locks the KEEP LONGTERM command wishes to set, release, or monitor.
Module:
ADSOGMIS
Severity:
0
Reason:
The keyword CURRENT is missing from the NOTIFY option of the KEEP LONGTERM command. Check the syntax of the KEEP LONGTERM command.
Module:
ADSOGMIS
Severity:
0
Reason:
A record/set/area name is missing from the NOTIFY, SHARE, and EXCLUSIVE clauses in the KEEP LONGTERM command.
Module:
ADSOGMIS
Severity:
0
Reason:
The required keywords, SHARE or EXCLUSIVE, are missing from the UPGRADE option in the KEEP LONGTERM command.
Module:
ADSOGMIS
Severity:
0
Reason:
RECORD is the required keyword following RETURN in the following commands: PUT SCRATCH, DELETE SCRATCH, and PUT QUEUE.
Module:
ADSOGMIS
Severity:
0
Reason:
LENGTH is the required keyword following RETURN or MAX in the GET SCRATCH command and the GET QUEUE command.
Module:
ADSOGMIS
Severity:
0
Reason:
The expected keyword FROM was not found in one of the following commands:
FROM is mandatory for PUT SCRATCH and PUT QUEUE. FROM is required only for a WRITE PRINTER command that does not specify SCREEN CONTENTS.
Module:
ADSOGMIS
Severity:
0
Reason:
A KEEP LONGTERM, scratch/queue management, or utility command was the last process command and did not end with a period; or the command was expecting an additional parameter and the end of the process was encountered instead.
Module:
ADSOGMIS
Severity:
0
Reason:
The INIT REC utility command is missing either the keyword ALL or the left parenthesis indicating beginning of the record list.
Module:
ADSOGMIS
Severity:
0
Reason:
The closing right parenthesis for the record list was not found in the INIT REC command.
Module:
ADSOGMIS
Severity:
0
Reason:
The RETURN NOTIFICATION clause is required after the TEST option in the KEEP LONGTERM command.
Module:
ADSOGMIS
Severity:
0
Reason:
The left parenthesis of the error expression in the ALLOWING clause is missing in one of the following commands: KEEP LONGTERM, scratch/queue management, or WRITE PRINTER.
Module:
ADSOGMIS
Severity:
0
Reason:
The closing right parenthesis of the error expression in the ALLOWING clause is missing in one of the following commands: KEEP LONGTERM, scratch/queue management, or WRITE PRINTER.
Module:
ADSOGMIS
Severity:
0
Reason:
The ALLOWING clause in a KEEPLONGTERM, WRITE PRINTER, or scratch/queue management command contains an invalid entry. The keyword THRU/THROUGH must be followed by an error code enclosed in quotes.
Module:
ADSOGMIS
Severity:
0
Reason:
TEXT or CODE is required with the message parameter.
Module:
ADSOGMIS
Severity:
0
Reason:
The SNAP command is the last command in the process. It is not terminated by a period.
Module:
ADSOGMIS
Severity:
0
Reason:
The parser called ADSOGMIS with an invalid command type. This is an internal error. Contact Technical Support.
Module:
ADSOGMIS
Severity:
3
Reason:
The branch code specified in the parse tree in ADSOGMIS is out of range or not in use. This is an internal error. Contact Technical Support.
Module:
ADSOGMIS
Severity:
3
Reason:
A parse stack overflow was about to occur during the parsing of one of the following commands: scratch/queue management, KEEP LONGTERM, or utility. Contact Technical Support to increase the parse stack size.
Module:
ADSOGMIS
Severity:
3
Reason:
Two record lists are specified in the SNAP command; that is, two RECORDS keywords precede the left parenthesis.
Module:
ADSOGMIS
Severity:
0
Reason:
The record specified in the SNAP command is not a work record, subschema record, or map record, and therefore is not known to this dialog. Only records named as work records, subschema records, or map records may be specified.
Module:
ADSOGMIS
Severity:
0
Reason:
The SNAP command contains an invalid keyword. Check the syntax for the SNAP command.
Module:
ADSOGMIS
Severity:
0
Reason:
The SNAP command must specify the following: ALL or any combination of control blocks; RECORDS clause; or TITLE.
Module:
ADSOGMIS
Severity:
0
Reason:
The name specified in the NOTIFY CURRENT or SHARE/EXCLUSIVE option of a KEEP LONGTERM command is not a valid record, set, or area name for the subschema associated with the dialog.
Module:
ADSOGMIS
Severity:
0
Reason:
The name specified in the NOTIFY CURRENT or SHARE/EXCLUSIVE option of the KEEP LONGTERM command is a valid record name but does not participate in the subschema associated with the dialog. The name must be a subschema record name.
Module:
ADSOGMIS
Severity:
0
Reason:
An internal error occurred in the record name validation routine during the parsing of the KEEP LONGTERM command.
Module:
ADSOGMIS
Severity:
0
Reason:
The record name specified in the NOTIFY CURRENT or SHARE/EXCLUSIVE option of a KEEP LONGTERM command is not a valid record name or it specifies a logical record that already participates in another logical record used by the dialog. A record may participate in at most one logical record per dialog.
Module:
ADSOGMIS
Severity:
0
Reason:
The record specified in the NOTIFY CURRENT or SHARE/EXCLUSIVE option of a KEEP LONGTERM command is a logical record
Specify a subschema record rather than a logical record.
Module:
ADSOGMIS
Severity:
0
Reason:
The set name specified in the NOTIFY CURRENT or SHARE/EXCLUSIVE option of the KEEP LONGTERM command is not in the subschema.
Module:
ADSOGMIS
Severity:
0
Reason:
This is an internal error. Contact Technical Support.
Module:
ADSOGMIS
Severity:
0
Reason:
This is an internal error. Contact Technical Support.
Module:
ADSOGMIS
Severity:
0
Reason:
The area name specified in the NOTIFY CURRENT or SHARE/EXCLUSIVE option of the KEEP LONGTERM is not in a subschema associated with a dialog.
Module:
ADSOGMIS
Severity:
0
Reason:
A return code that is greater than 12 or that is not a multiple of 4 was received from a call to ADSOGNDB with function 7. This is an internal error. Contact Technical Support.
Module:
ADSOGMIS
Severity:
0
Reason:
The retention clause of the PUT QUEUE command specifies a period greater than 255. The maximum queue retention period is 255.
Module:
ADSOGMIS
Severity:
0
Reason:
FROM/INTO locations in the PUT QUEUE, PUT SCRATCH, and WRITE PRINTER commands are not in the same record. INTO/TO locations in the GET QUEUE and GET SCRATCH commands are not in the same record.
Module:
ADSOGMIS
Severity:
0
Reason:
The data type of the variable is not one of the following: halfword binary, fullword binary, signed packed decimal, unsigned packed decimal, signed/unsigned zoned decimal, display/short/long floating point. This applies to the retention clause in the PUT QUEUE command and the length clause in the PUT SCRATCH, GET SCRATCH, and PUT QUEUE commands.
Module:
ADSOGMIS
Severity:
0
Reason:
The data type of variable is not 'group' or EBCDIC. This applies to variable names for scratch id and queue id clauses in the scratch/queue management commands and to variables in printer destination clauses in the WRITE PRINTER command.
Module:
ADSOGMIS
Severity:
0
Reason:
The LENGTH parameter in the WRITE PRINTER command is larger than 32767. The maximum length is 32767.
Module:
ADSOGMIS
Severity:
0
Reason:
The COPIES parameter in the WRITE PRINTER command is out of range. It must be a number between 1 and 255, inclusive.
Module:
ADSOGMIS
Severity:
0
Reason:
The REPORT ID parameter in the WRITE PRINTER command is an invalid number. It must be a number between 1 and 255, inclusive.
Module:
ADSOGMIS
Severity:
0
Reason:
The CLASS parameter in the WRITE PRINTER command is an invalid number. It must be a number from 1 to 255 inclusive.
Module:
ADSOGMIS
Severity:
0
Reason:
The INIT REC command specifies either ALL or a record list, but not both.
Module:
ADSOGMIS
Severity:
0
Reason:
An error code specified within quotes in an ALLOWING clause in the KEEP LONGTERM, WRITE PRINTER, or scratch/queue management command is in error. All of the characters enclosed in quotes in the error code must be decimal digits.
Module:
ADSOGMIS
Severity:
0
Reason:
A status field variable in an error expression in the ALLOWING clause in a KEEP LONGTERM, WRITE PRINTER, or scratch/queue management command is in error. All status field variables must be level-88 variables defined in the status definition record for the dialog.
Module:
ADSOGMIS
Severity:
0
Reason:
A status field variable in an error expression in the ALLOWING clause in the KEEP LONGTERM, WRITE PRINTER, or scratch/queue management commands is in error. All status field variables must be level-88 variables defined in the status definition record for the dialog.
Module:
ADSOGMIS
Severity:
0
Reason:
A status field variable in an error expression in an ALLOWING clause in the KEEP LONGTERM, WRITE PRINTER, or scratch/queue management command is in error. All status field variables must be level-88 variables defined in the status definition record for the dialog.
Module:
ADSOGMIS
Severity:
0
Reason:
An error in the ALLOWING clause has been specified in a KEEP LONGTERM, WRITE PRINTER, or scratch/queue management command, but AUTOSTATUS is NO for the dialog. Error expressions in these commands are allowed only if AUTOSTATUS is YES for the dialog.
Module:
ADSOGMIS
Severity:
0
Reason:
A high return code was received from the routine that adds literals to the litpool. This applies to the TITLE literal in the SNAP command; the ERROR CODE literal in the ALLOWING clause in the KEEP LONGTERM, WRITE PRINTER, and the scratch/queue management commands; the set name literal in the KEEP LONGTERM command; the AREA ID in the scratch management commands; the queue id in the queue management commands; DESTINATION literal in the WRITE PRINTER command; and the longterm id in the KEEP LONGTERM command.
Module:
ADSOGMIS
Severity:
0
Reason:
The data field name parsed does not exist in the data dictionary, nor does it exist as a valid function invocation name since there is no master function table in the load area. Likely problems are that the data field was misspelled or that the master function table is not named RHDCEVBF with a version number of 1 in the load area.
Module:
ADSOGDAB
Severity:
0
Reason:
The data field name parsed does not exist in the data dictionary, nor does it exist as a valid function invocation name in the master function table in the load area. Likely problems are that the data field or function name was misspelled or that the master function table has not been properly updated after adding a function to it.
Module:
ADSOGDAB
Severity:
0
Reason:
The required parameter LOG or OPERATOR is missing from the WRITE command.
Module:
ADSOGMIS
Severity:
0
Reason:
The record named has no elements defined or is a reserved record such as ADSO-STAT-DEF-REC.
Module:
ADSOGMIS
Severity:
0
Reason:
A variable data field or literal name of length greater than eight characters for a scratch area ID or sixteen characters for a queue ID has been specified. The statement has been flushed.
Module:
ADSOGMIS
Reason:
An invalid record name was found after the IN or OF keyword. A valid record name contains 1 to 32 alphanumeric characters. Make sure that the data field is in the correct record.
Module:
ADSOGEXP
Severity:
0
Reason:
The right parenthesis to terminate the subscript value list was not found. A subscripted data field must end with a closing parenthesis. Parentheses are required around the subscript value list.
Module:
ADSOGEXP
Severity:
0
Reason:
An expression beginning with + or an expression containing a + immediately following another binary operator (+,-,*,/) was found. The + sign is a unary operator and, therefore, must be followed by an integer or decimal number, a data field name, or a parenthetical expression.
Module:
ADSOGEXP
Severity:
0
Reason:
The subscript value list for a subscripted data field name contains an invalid entry; for example, a subscript that is an expression with a missing operand or operator.
Module:
ADSOGEXP
Severity:
0
Reason:
The left parenthesis was recognized as the beginning of a nested expression; however, a right parenthesis to terminate the expression was not found.
Module:
ADSOGEXP
Severity:
0
Reason:
The left parenthesis was recognized as the beginning of a nested expression; however, no expression was found after the parenthesis.
Module:
ADSOGEXP
Severity:
0
Reason:
A valid operand, that is, an expression, data fieldname, or number was recognized preceding a + or - sign. However, an invalid operand was found following it.
Module:
ADSOGEXP
Severity:
0
Reason:
A valid operand, that is, an expression, data fieldname, or number was recognized preceding a * or / sign. However, an invalid operand was found following it.
Module:
ADSOGEXP
Severity:
0
Reason:
The left parenthesis was not found. The keyword LENGTH must be followed by the map field name in parentheses. The keyword LENGTH is reserved and is used to represent the number of characters entered in a map field.
Module:
ADSOGEXP
Severity:
0
Reason:
The name specified by the LENGTH parameter does not name a map field in the dialog's map. Check for misspelling.
Module:
ADSOGEXP
Severity:
0
Reason:
The right parenthesis was not found. The keyword LENGTH must be followed by a map field name in parentheses. The keyword LENGTH is reserved and is used to represent the number of characters in a map field.
Module:
ADSOGEXP
Severity:
0
Reason:
Two levels of qualification for a data field are not acceptable unless the second qualifier is the clause OF LR for logical record processing.
Module:
ADSOGEXP
Severity:
0
Reason:
The figurative constant ALL must be followed by a 1-to 255-character quoted string or one of the following keywords: SPACES, ZERO(S), ZEROES, HIGH-VALUES, LOW-VALUES, or QUOTES.
Module:
ADSOGEXP
Severity:
0
Reason:
The right parenthesis that terminates the function value list was not found. Parentheses are required around the function value list. The last argument in the list must end with a right parenthesis.
Module:
ADSOGEXP
Severity:
0
Reason:
The function value list for a function data field name contains an invalid entry. An example of an invalid entry in a function is an expression that is missing an operator or operand.
Module:
ADSOGEXP
Severity:
0
Reason:
The subexpression code passed to the expression parser is invalid. This is an internal error. Contact Technical Support.
Module:
ADSOGEXP
Severity:
3
Reason:
The branch code specified in the expression parse tree was not used. This is an internal error. Contact Technical Support.
Module:
ADSOGEXP
Severity:
3
Reason:
If processing were not terminated, a parse stack overflow would have occurred during the parsing of a data field name or expression. Reduce the number of nested expressions. Contact Technical Support to increase the size of the parse stack.
Module:
ADSOGEXP
Severity:
3
Reason:
One of the following conditions exists:
Module:
ADSOGEXP
Severity:
0
Reason:
The record element is not in a record known to the dialog as a map record, subschema record, or work record. Check the spelling of the record element; make sure that the necessary record is known to the dialog.
Module:
ADSOGEXP
Severity:
0
Reason:
An internal routine (to validate data field names) passed an invalid return code to the expression parser. This is an internal error. Contact Technical Support.
Module:
ADSOGEXP
Severity:
3
Reason:
An expression may have a maximum total of fifty operands and operators. Reduce the number of operations performed within the current expression.
Module:
ADSOGEXP
Severity:
0
Reason:
An attempt was made to use more subscripts for a data field than the number of subscripts defined for the data field in the dictionary. Reduce the number of subscripts to the number defined.
Module:
ADSOGEXP
Severity:
0
Reason:
The right parenthesis terminating the subscript list for a subscripted data field was recognized before all of the subscripts required for the data field were recognized. Check the data field definition and increase the number of subscripts accordingly.
Module:
ADSOGEXP
Severity:
0
Reason:
The data field name exists in more than one record known to the dialog. A record qualifier must be specified to uniquely identify the desired data field.
Module:
ADSOGEXP
Severity:
0
Reason:
A '(' subscript delimiter was found after a record element (data field name) for which a subscript is not expected. A subscript can only be specified for a field which has been defined as a multiply-occurring field. Check the field definition for the record element that precedes the '('.
Module:
ADSOGEXP
Severity:
0
Reason:
A unary (+,-) or binary (+,-,*,/) operation may be performed on a data field that is one of the following data types: group, display floating point, bit and doubleword binary or on a figurative constant with the exception of ZERO(S) and ZEROES.
Module:
ADSOGEXP
Severity:
0
Reason:
A Boolean operation (AND/OR/NOT) may be performed only on two data fields that are bit data types.
Module:
ADSOGEXP
Severity:
0
Reason:
A MATCHES or CONTAINS operation can be performed only on operands of either of the following data types:
The length of the first operand of a CONTAINS operation must be greater than or equal to the length of the second operand.
Module:
ADSOGEXP
Severity:
0
Reason:
The dictionary definition of the data field specifies that it is a subscripted field. The left parenthesis was not found after the data field name to initiate the subscript list.
Module:
ADSOGEXP
Severity:
0
Reason:
The DIVIDE (/) operation must have a divisor data field with a maximum length of eight bytes.
Module:
ADSOGEXP
Severity:
0
ADSOGEXP
Severity:
0
Reason:
A subscripted data field is defined with an OCCURS DEPENDINGON clause. The control field that contains the maximum subscript value at runtime must be defined in the same record. The control field must be defined as a halfword or fullword binary field. Check the record definition.
Module:
ADSOGEXP
Severity:
0
ADSOGEXP
Severity:
0
Reason:
While attempting to determine the precision of the result of an arithmetic operation, the CA ADS dialog compiler found an XDE with an invalid operation type. This is a system internal error.
Module:
ADSOGEXP
Severity:
3
Reason:
An error occurred when the CA ADS dialog compiler attempted to add the dope vector for a subscripted data field to the literal pool. Reduce the complexity of expressions (that is, the number of nested parenthetical expressions). Alternatively, contact Technical Support to increase the size of the parse stack.
Module:
ADSOGEXP
Severity:
3
Reason:
The internal control blocks (GRE) built to represent a subscripted data field are in error. This is an internal error. Contact Technical Support.
Module:
ADSOGEXP
Severity:
3
Reason:
The data field name was qualified by the name of a logical record name. However, the same data field name exists in more than one participating record within the logical record. Change the record qualifier to be the participating record name rather than the logical record name.
Module:
ADSOGEXP
Severity:
0
Reason:
The data field name was qualified with a logical record name; however, one of the participating records in the logical record is already known to participate in a different logical record associated with the dialog. A participating record may exist only within one logical record in a dialog.
Module:
ADSOGEXP
Severity:
0
Reason:
The data field name parsed does not exist in the data dictionary, nor does it exist as a valid function name since there is no master function table in the load area. Likely problems are that the data field was misspelled or that the master function table is not named RHDCEVBF with a version of 1 in the load area.
Module:
ADSOGEXP
Severity:
0
Reason:
The data field name parsed does not exist in the data dictionary, nor does it exist as a valid function name in the master function table in the load area. Likely problems are that the data field or function name was misspelled or that the master function table has not been properly updated after adding a function.
Module:
ADSOGEXP
Severity:
0
Reason:
The function name field is missing one or more mandatory parameters. For more information about the parameter requirements for this function, see the CA ADS Reference Guide. If an optional parameter is omitted from a function call, an @ character must be included as a placeholder for the parameter (unless the omitted parameter is at the end of the list).
Module:
ADSOGEXP
Severity:
0
Reason:
During an attempt to convert a function parameter data type to one that can be processed by the function code, an error was found. Only predetermined data types can be used for each function parameter and these are documented in the CA ADS Reference Guide. Change the parameter to one supported by the function and recompile the process.
Module:
ADSOGEXP
Severity:
0
Reason:
The size limit for the IRA (Intermediate Result Area) has been exceeded (65,536). The size field is a halfword. IRAs are required to execute COMPUTE statements and BUILT-IN Functions. This error normally occurs as the result of nested Built-in functions using large elements as operands. Reduce the length of the elements or use fewer Built-in functions in the command.
Module:
ADSOGEXP
Severity:
0
Additional information Added by PTF ADS370/100 FN: TC11037 Modified by PTF ADS370/487 FN: TF24010 - 64K changed to 32K Modified by PTF ADS370/545 FN: TF24105 - 32K limit changed back to 64K but without DC106003 abends
Reason:
A level-88 name may not be specified as an operand for an arithmetic operation (+,-,*,/).
Module:
ADSOGEXP
Severity:
0
Reason:
A keyword defined for a logical record path may not be specified as an operand for an arithmetic operation (+, -, *, /).
Module:
ADSOGEXP
Severity:
0
Reason:
The OFLR qualifier may be specified only for a data field that is used in a conditional expression in a WHERE clause in a logical record database command.
Module:
ADSOGEXP
Severity:
0
Reason:
The CA ADS dialog compiler failed to add a literal or a number to the literal pool. This is a system internal error.
Module:
ADSOGEXP
Severity:
0
Reason:
The CA ADS dialog compiler cannot handle a nesting level more than 32 deep for any built-in function. For example, the following expression causes an error when "...." represents more than 26 levels of embedded nesting:
SUB(SUB(SUB(SUB(SUB...SUB(string,1),....,2),3),4),5),6), where
Consider subdividing the expression.
Module:
ADSOGEXP
Severity:
0
Reason:
A built-in function cannot be specified as the target field of an arithmetic or assignment command. It is also illegal to use a built-in function anywhere that the function would be considered a target. For example, a built-in function could not be used in the parameter list of a DISPLAY MESSAGE CODE PARMS command, which is used to replace variable parameters in the message field. If a function value should be part of a DISPLAY MESSAGE CODE PARMS expression, move the function value to an intermediate field first; then use the intermediate field data name as part of the expression.
Module:
ADSOGEXP
Severity:
0
Reason:
When addressing a subscripted bit field, all occurring groups in which that field is contained must have an element size that is less than or equal to 32767 bits.
Module:
ADSOGEXP
Severity:
0
Reason:
An error was encountered when attempting to generate code to address a subscripted bit field. When a reference to a subscripted bit field is encountered, all higher level occurring groups that contain that field are examined. For each such occurring group, the offset of that group within its containing group must be less than or equal to 32767 bits.
Module:
ADSOGEXP
Severity:
0
Reason:
One of the literal subscripts used to index a data field was outside the range of valid values for the corresponding dimension.
Module:
ADSOGEXP
Severity:
0
Reason:
ADS does not support the use of arrays with more than 15 dimensions. Reduce the number of dimensions of the indicated data field in the dictionary.
Module:
ADSOGEXP
Severity:
0
Reason:
The dialog compiler attempted to locate a literal value being used as a subscript in the literal pool and failed. This is an internal system error. Contact Technical Support.
Module:
ADSOGEXP
Severity:
0
Reason:
An APPC command such as ALLOCATE, CONFIRM, SEND-ERROR, was encountered in a dialog that has a previous OSCaR command such as OPEN or CLOSE. APPC and OSCaR commands are mutually exclusive within a single dialog.
Module:
ADSOGEXP
Severity:
0
Reason:
The value entered after the @ reserved character is not a valid address. A valid address can contain only the following characters:
Module:
DBUGGEXP
Severity:
0
Reason:
The data field name exists more than one time within a single record known to the dialog. This field cannot be accessed because ADSC cannot determine which occurrence of the field is being requested, and optional apar bit 256 is on.
Module:
ADSOGEXP
Severity:
0
Reason:
The token flagged is expected to be a symbol within the current program; however, the token format does not comply with rules for specifying a program symbol. For more information about the rules for specifying user symbols, see the CA IDMS Online Debugger Guide.
Module:
DBUGGEXP
Severity:
0
Reason:
The token flagged is expected to be a qualifier for the previous symbol; however, the token that follows the IN or OF keyword is not a name with a length from 1 through 32 characters.
Module:
DBUGGEXP
Severity:
0
Reason:
The token flagged is expected to be an occurrence count for previous symbol; however, the token that follows the occurrence keyword is not a one-, two-, or three-digit number.
Module:
DBUGGEXP
Severity:
0
Reason:
The requested load address cannot be resolved because there is no program currently defined to the debugger.
Module:
DBUGGEXP
Severity:
0
Reason:
The keyword cannot be specified unless the current program has a symbol table.
Module:
DBUGGEXP
Severity:
0
Reason:
An address cannot have the high order bit set.
Module:
DBUGGEXP
Severity:
0
Reason:
The % keyword can be specified a maximum of 255 times in an expression.
Module:
DBUGGEXP
Severity:
0
Reason:
One of the following errors has occurred:
Module:
ADSOGCND
Severity:
0
Reason:
A left parenthesis was recognized to indicate the beginning of a nested condition. A valid condition following the left parenthesis was not found.
Module:
ADSOGCND
Severity:
0
Reason:
The left parenthesis and a valid condition were found. The right parenthesis required to terminate a nested condition was not found.
Module:
ADSOGCND
Severity:
0
Reason:
A valid expression was recognized followed by a valid relational operator (EQ, =, IS, LT, GT, NE, LE, GE, MATCHES, CONTAINS), but no valid expression was found following the relational operator.
Module:
ADSOGCND
Severity:
0
Reason:
One of the following errors occurred:
Module:
ADSOGCND
Severity:
0
Reason:
The keyword(s) CURSOR (NOT) (AT) were recognized in a conditional expression, but no valid map field name was found. The CURSOR AT condition requires the name of the map field to be checked for placement of the cursor.
Module:
ADSOGCND
Severity:
0
Reason:
A relational expression beginning with the keyword SET was recognized; however, either no set name follows, or the name that follows is an invalid set name for the dialog's subschema. The SET EMPTY and SET MEMBER conditions both require the specification of a set name.
Module:
ADSOGCND
Severity:
0
Reason:
The keyword SET and a valid set name were recognized in a conditional expression, but the keywords (IS) (NOT) EMPTY or MEMBER were not found. One of these two options must be specified for the SET MEMBERSHIP status condition.
Module:
ADSOGCND
Severity:
0
Reason:
A valid map field status condition was recognized in a conditional expression, but the keyword to indicate the particular status to check was missing. One of the following keywords must be specified: CHANGED, TRUNCATED, ERASED, or (IN) ERROR.
Module:
ADSOGCND
Severity:
0
Reason:
The keyword FIELD or DFLD was recognized in a conditional expression initiating a single map field status condition; however, no valid map field name was found following it. A single map field name must be specified as the one whose status is to be checked.
Module:
ADSOGCND
Severity:
0
Reason:
The keywords ALL/ANY/NONE/SOME OF were recognized in a conditional expression initiating a map field status condition. However, either no parenthesized list of map field names was found, or one or more fields in the list were not valid map field names.
Module:
ADSOGCND
Severity:
0
Reason:
The FOR clause after a status-code-name must be followed by the name of a record in the dialog's subschema. Check the subschema for valid record names.
Module:
ADSOGCND
Severity:
0
Reason:
The subexpression code passed to the expression parser was invalid.
Module:
ADSOGCND
Severity:
3
Reason:
The branch code specified in the expression parse tree was not used.
Module:
ADSOGCND
Severity:
3
Reason:
The internal stack used by the condition parser overflowed due to one of the following: a conditional expression had too many levels of nesting; or there were too many levels of nested IF, WHILE, and ON commands. Reduce the complexity of the condition, or reduce the number of nested IF, WHILE, and ON commands.
Module:
ADSOGCND
Severity:
3
Reason:
A unary (+, -) or binary (+, -, *, /) operation may not be performed on a group, display floating point, multi-bit binary, or doubleword binary data field, or on a figurative constant with the exception of ZEROS/ZEROES.
Module:
ADSOGCND
Severity:
0
Reason:
A Boolean operation (AND/OR/NOT) may be performed only on two data fields that are bit data types.
Module:
ADSOGCND
Severity:
0
Reason:
One of the following errors has occurred:
Module:
ADSOGCND
Severity:
0
Reason:
The data field name is not in a record known to the dialog as a map record, subschema record, or work record.
Module:
ADSOGCND
Severity:
0
Reason:
The data field name exists in more than one record known to the dialog. A record qualifier must be specified to uniquely identify the desired data field.
Module:
ADSOGCND
Severity:
0
ADSOGCND
Severity:
0
Reason:
The validated data field name program passed an invalid return code to the expression parser.
Module:
ADSOGCND
Severity:
3
Reason:
The #GETSTG macro failed when the CA ADS dialog compiler allocated an internal control block needed to save the parse environment when the parse of an ambiguous condition was initiated.
Module:
ADSOGCND
Severity:
3
Reason:
A condition with more than 30 nested ambiguous conditions to parse was encountered. Reduce the number of nested conditions or rearrange the condition to reduce the number of parse ambiguities. For example, the following are ambiguous parse conditions:
(A + B) > C OR D = E (A + B > C) OR D = E
When the left parenthesis is recognized, look ahead is required for the parser to determine if an arithmetic or relational expression is enclosed by a matching right parenthesis. The first ambiguous condition shown above could be clarified by coding C < (A + B) OR D = E. The second ambiguous condition shown above could be clarified by omitting the unnecessary parentheses.
Module:
ADSOGCND
Severity:
3
Reason:
A conditional expression was found with a keyword from a logical record path definition. Testing a keyword in a condition is valid only in a WHERE clause in a logical database command.
Module:
ADSOGCND
Severity:
0
Reason:
The keyword specified in the WHERE condition for a logical record database command is not valid for the specific database verb (OBTAIN, MODIFY, STORE, ERASE). Check the path definitions in the subschema for valid keywords for each verb.
Module:
ADSOGCND
Severity:
0
Reason:
A MATCHES or CONTAINS operation may be performed only on operands that are EBCDIC (display) or unsigned zoned decimal data types. Additionally, for the CONTAINS operation, the length of the first operand must be greater than or equal to the length of the second operand.
Module:
ADSOGCND
Severity:
0
Reason:
An attempt to add conditional values, KEYWORD names, or setnames to the literal pool failed. This is a system internal error.
Module:
ADSOGCND
Severity:
0
Reason:
A condition may contain a maximum total of 100 operands and operators. This number was exceeded by the indicated condition. Note that a check for a level-88 variable contains multiple operands and operators; the number varies with the number of VALUE clauses on the level-88 variable and with the type of VALUE clause (single value check or range of values).
Module:
ADSOGCND
Severity:
0
Reason:
The $BACKWARD condition is valid only when the dialog has a pageable map. Either recompile the map with the pageable option, or remove this condition from the process.
Module:
ADSOGCND
Severity:
0
Reason:
The $DETAIL condition is valid only when the dialog has a pageable map. Either recompile the map with the pageable option or remove this condition from the process.
Module:
ADSOGCND
Severity:
0
Reason:
At the onset of parsing an ambiguous condition, the contents of the current print buffer were saved in a scratch record. The parser reached a point where it was necessary to back up the process and try a different path. At the time of the backup, the GET SCRATCH command for the saved contents of the print buffer failed.
Module:
ADSOGCND
Severity:
3
Reason:
A conditional expression was found with a keyword from a logical record path definition. Testing a keyword in a condition is valid only in a WHERE clause in a logical record database command.
Module:
ADSOGCND
Severity:
3
Reason:
The $HEADER condition is valid only when the dialog has a pageable map. Either recompile the map with the pageable option or remove this condition from the process.
Module:
ADSOGCND
Severity:
0
Reason:
The $FULLPAGE condition is valid only when the dialog has a pageable map. Either recompile the map with the pageable option or remove this condition from the process.
Module:
ADSOGCND
Severity:
0
Reason:
The $END-OF-DATA condition is valid only when the dialog has a pageable map. Either recompile the map with the pageable option or remove this condition from the process.
Module:
ADSOGCND
Severity:
0
Reason:
The $FORWARD condition is valid only when the dialog has a pageable map. Either recompile the map with the pageable option or remove this condition from the process.
Module:
ADSOGCND
Severity:
0
Reason:
The $DETAIL-NOT-FOUND condition is valid only when the dialog is associated with a pageable map. Either recompile the map with the pageable option or remove this condition from the process.
Module:
ADSOGCND
Severity:
0
Reason:
The $MAXIMUM-DETAILS-PUT condition is valid only when the dialog is associated with a pageable map. Either recompile the map with the pageable option or remove this condition from the process.
Module:
ADSOGCND
Severity:
0
Reason:
The data field name parsed does not exist in the data dictionary, nor does it exist as a valid function invocation name since there is no master function table in the load area. Likely problems are that the data field was misspelled or that the master function table is not named RHDCEVBF with a version number of 1 in the load area.
Module:
ADSOGEXP
Severity:
0
Reason:
The data field name parsed does not exist in the data dictionary, nor does it exist as a valid function invocation name in the master function table in the load area. Likely problems are that the data field or function name was misspelled or that the master function table has not been properly updated after adding a function to it.
Module:
ADSOGEXP
Severity:
0
Reason:
An unrecoverable error was encountered during conditional statement optimization process.
Module:
ADSOGCND
Severity:
3
Reason:
The $PAGE-READY condition is valid only when the dialog has a pageable map. Either recompile the map with the pageable option or remove this condition from the process.
Module:
ADSOGCND
Severity:
0
Reason:
An IF or WHILE command was encountered that is too large to be optimized. Use the SYMBOL TABLE = YES option to compile the dialog, or replace the command with several smaller conditional statements.
Module:
ADSPGCND
Severity:
0
Reason:
An IF or WHILE command was encountered that is too large to be optimized. A #GETSTG request for two times the length of the unoptimized XDE stack failed. Use the SYMBOL TABLE = YES option to compile the dialog, or replace the command with several smaller conditional statements, or increase the size of the storage pool.
Module:
ADSOGCND
Severity:
0
Reason:
An IF or WHILE command was optimized and its optimized XDE stack is larger than its unoptimized XDE stack. This could be an internal error. Use the SYMBOL TABLE = YES option to compile the dialog, or replace the command with several smaller conditional statements, and/or contact Technical Support.
Module:
ADSOGCND
Severity:
0
Reason:
A level 88 condition, whether or not used with a subscript, cannot be used to test the value of an occurring field. A comparison condition must be used in this case.
Module:
ADSOGCND
Severity:
0
Reason:
The data field name exists more than one time within a single record known to the dialog. This field cannot be accessed because ADSC cannot determine which occurrence of the field is being requested, and optional apar bit 256 is on.
Module:
ADSOGCND
Severity:
0
Reason:
The keyword OF or IN was found after a map field name, but a valid record name was not found as a qualifier.
Module:
ADSOGMFD
Severity:
0
Reason:
A subscripted map field was recognized and a left parenthesis was found to initiate the subscript value list; however, a right parenthesis was not found to end the list.
Module:
ADSOGMFD
Severity:
0
Reason:
One of the subscripts specified in the subscript list of a subscripted mapfield is an invalid data name or an invalid arithmetic expression; that is, the number of operators and operands conflict.
Module:
ADSOGMFD
Severity:
0
Reason:
A left parenthesis was recognized to initiate a map field list; however, a right parenthesis was not found to terminate the list, or one of the members of the list is not a map field for this dialog.
Module:
ADSOGMFD
Severity:
0
Reason:
The subexpression code passed to the expression parser was invalid.
Module:
ADSOGMFD
Severity:
3
Reason:
The branch code specified in the expression parse tree was not used.
Module:
ADSOGMFD
Severity:
3
Reason:
The internal stack used by the parser overflowed. Some possible reasons for the overflow are: a map field name has a subscript that is a complex nested arithmetic expression; a map field is contained in a map field status condition that is included in a complex nested condition; or there are too many levels of nested IF, WHILE, and ON commands. Check these nest levels and reduce the amount of nesting.
Module:
ADSOGMFD
Severity:
3
Reason:
One of the following errors has occurred: the data field name was qualified by a record name that is not known to this dialog; the dialog has no map, work, or subschema records associated with it, so any data field name is unacceptable; or the data field name is not in a record known to this dialog. Check the dialog and its map and subschema for the work, map, and subschema records, respectively.
Module:
ADSOGMFD
Severity:
0
Reason:
The data field name is not in a record known to the dialog as a map record, subschema record, or work record.
Module:
ADSOGMFD
Severity:
0
Reason:
The validated data field name program passed an invalid return code to the expression parser.
Module:
ADSOGMFD
Severity:
3
Reason:
During an attempt to parse a subscript expression in the subscript value list of a map field, it became necessary to parse another map field. Such nesting is invalid; for example, LENGTH (MFLD - 1 (LENGTH (MFLD - 2))) is invalid.
Module:
ADSOGMFD
Severity:
0
Reason:
The data field name exists in more than one record known to the dialog. A record qualifier must be specified to uniquely identify the desired data field.
Module:
ADSOGMFD
Severity:
0
Reason:
The parser expected a map field name at the indicated position, but the data field specified there does not participate as a data field in the dialog's map. Map field names are expected in the following places: as a parameter to the LENGTH function; in the cursor position condition; in the map field status conditions; and in MAP commands. This message will be displayed for a map field specified in a MODIFY MAP command when that field is associated with an OUTPUT map.
Module:
ADSOGMFD
Severity:
0
Reason:
A left parenthesis was recognized following a map field name, but the map field was not an occurring field.
Module:
ADSOGMFD
Severity:
0
Reason:
The field work area (FWA) used to build internal control blocks for map field subscripts and map field lists is full. Reduce the number of OCCURS levels, that is, the number of subscripts, for the map field. This error should rarely occur, since map fields are currently restricted to one OCCURS level (that is, one subscript) by the mapping facility.
Module:
ADSOGMFD
Severity:
0
Reason:
A right parenthesis was recognized indicating the termination of the subscript value list for a subscripted map field; however, the number of subscripts parsed is less than the number of subscripts expected. Check the OCCURS level for the map field.
Module:
ADSOGMFD
Severity:
0
Reason:
The right parenthesis was recognized indicating the termination of the subscript value list for a subscripted map field; however, the number of subscripts parsed is greater than the number of subscripts expected. Check the OCCURS level for the map field.
Module:
ADSOGMFD
Severity:
0
Reason:
One of the subscripts in a subscript value list for a subscripted map field is invalid, that is, the subscript is not a numeric constant, data field name, or an arithmetic expression.
Module:
ADSOGMFD
Severity:
0
Reason:
The field work area (FWA) used to build internal control blocks for lists of map field names for MAP commands and map field status conditions is full. Reduce the number of map fields specified in the list, or reduce the complexity of any map field subscripts that are not nonnumeric constants (that is, subscripts that are arithmetic expressions).
Module:
ADSOGMFD
Severity:
0
Reason:
A numeric constant was recognized as a subscript for a subscripted map field; however, the constant is larger than the maximum subscript value allowed.
Module:
ADSOGMFD
Severity:
0
Reason:
A numeric constant was recognized as a subscript for a subscripted map field and stored as a signed packed decimal number in the literal pool. Later, during processing, it could not be found in the literal pool.
Module:
ADSOGMFD
Severity:
0
Reason:
A map field name was recognized that has a nonzero OCCURS level; however, the left parenthesis was not found to initiate a subscript value list.
Module:
ADSOGMFD
Severity:
0
Reason:
A #GETSTG macro for the FWA (see messages 166067 and166071) has failed.
Include here a description of what causes a #GETSTG macro failure.
Module:
ADSOGMFD
Severity:
3
Reason:
A map field name with a numeric constant subscript was recognized; however, that particular occurrence of the data field participates in the dialog's map.
Module:
ADSOGMFD
Severity:
0
Reason:
An attempt to add one of the following to the literal pool failed: map index list (MIL); XDE stack for a subscript descriptor element (SDE); a subscripted field element (SFE); and a primary map index list (PMIL).
Module:
ADSOGMFD
Severity:
0
Reason:
The data field name parsed does not exist in the data dictionary, nor does it exist as a valid function invocation name since there is no master function table in the load area. Likely problems are that the data field was misspelled or that the master function table is not named RHDCEVBF with a version number of 1 in the load area.
Module:
ADSOGMFD
Severity:
0
Reason:
The data field name parsed does not exist in the data dictionary, nor does it exist as a valid function invocation name in the master function table in the load area. Likely problems are that the data field or function name was misspelled or that the master function table has not been properly updated after adding a function to it.
Module:
ADSOGMFD
Severity:
0
Reason:
The map field list on a MODIFY MAP FOR ... command must have at least one DFLD.
Module:
ADSOGMFD
Severity:
0
Reason:
The CA ADS dialog compiler expected a true-false condition as part of the IF or WHILE statement. It was not found, and the statement was flushed. For more information about the correct syntax for these statements, see the CA ADS Reference Guide. Correct the syntax and recompile the process.
Module:
ADSOGFLO
Severity:
0
Reason:
All required keywords in this statement were found. The last required token in this command is a period. Either an optional keyword was misspelled or the statement terminator was left off. Check the syntax for the command in the CA ADS Reference Guide. Correct the syntax and recompile the process.
Module:
ADSOGFLO
Severity:
0
Reason:
The last statement in the process was not completely parsed when the end-of-file marker was encountered. Check for a missing period and for missing keywords. Correct the syntax and recompile the process.
Module:
ADSOGFLO
Severity:
0
Reason:
The CA ADS dialog compiler expected to find a one- to eight-character subroutine name in a CALL or DEFINE SUBROUTINE statement. Check the CA ADS Reference Guide for the correct syntax for these commands. Correct the syntax and recompile the process.
Module:
ADSOGFLO
Severity:
0
Reason:
An unrecognized initiating keyword was found within a conditional command. Note that some commands are valid initiating commands outside a conditional construct but not inside it. Check the spelling and/or abbreviation of the keyword. Refer to the CA ADS Reference Guide for more information about conditional commands.
Module:
ADSOGFLO
Severity:
0
Reason:
The path-status is a 1- to 16-character unquoted string condition name specified by the database administrator in the path selected to service the previous logical record request. It can be either standard path status or a path status defined by the database administrator in the dialog's subschema. Refer to the CA ADS Reference Guide for the standard statuses LR-FOUND, LR-NOT-FOUND, and LR-ERROR. Correct the syntax and recompile the process.
Module:
ADSOGFLO
Severity:
0
Reason:
The only valid keywords in an ON command are the THEN/ELSE clause or the REPEAT clause. Since neither keyword was found, the ON command was ignored. Check for unpaired END statements. Refer to the CA ADS Reference Guide for the correct syntax of the ON command. Correct the syntax and recompile the process.
Module:
ADSOGFLO
Severity:
0
Reason:
The node tree value indicates the command type is out of the range of ADSOGFLO. This is an internal error that may be masking a more serious problem. Print the snap dump accompanying this message.
Module:
ADSOGFLO
Severity:
3
Reason:
The command branch table index from the node tree entry is outside the allowable range of branch tree values. This is an internal error that could be masking a more serious problem. Print the snap dump accompanying this message.
Module:
ADSOGFLO
Severity:
3
Reason:
The internal parse area has overflowed. The CA ADS dialog compiler issued a #ACALL macro. The #ACALL macro saves registers in a stack area in the PSA. Print the snap dump.
Module:
ADSOGFLO
Severity:
3
Reason:
The CA ADS dialog compiler did not find a valid clause (THEN/ELSE or REPEAT) in the stack frame. Print the snap dump.
Module:
ADSOGFLO
Severity:
3
Reason:
The condition being parsed exceeded the number of XDEs allowed by the RHDCEVAL. Rewrite the condition to make it less complex.
Module:
ADSOGFLO
Severity:
0
Reason:
The end-of-file marker was encountered when a THEN clause terminated a process without an END statement. For more information, see the CA ADS Reference Guide. Correct the syntax and recompile the process.
Module:
ADSOGFLO
Severity:
0
Reason:
The EOF was encountered when an ELSE clause terminated a process without an END statement. For more information about the correct syntax, see the CA ADS Reference Guide. Correct the syntax and recompile the process.
Module:
ADSOGFLO
Severity:
0
Reason:
The EOF was encountered when a REPEAT clause terminated the process without an END statement. Refer to the CA ADS Reference Guide for correct syntax and recompile the process.
Module:
ADSOGFLO
Severity:
0
Reason:
The EOF was encountered before the end of a procedural command was scanned. Check for a missing period on the last statement in the process. For more information about correct command syntax, see the CA ADS Reference Guide. Correct the syntax and recompile the process.
Module:
ADSOGFLO
Severity:
0
Reason:
The GOBACK statement precedes the DEFINE command of the subroutine. The GOBACK statement is valid only as the last statement in a subroutine. Check the process text to ensure that the GOBACK statement follows the DEFINE statement in the subroutine and recompile the process.
Module:
ADSOGFLO
Severity:
0
Reason:
The DEFINE statement is not valid as the first statement in a process. The DEFINE statement is the first command in a subroutine. At least one statement must exist in the main process to call the subroutine. Refer to the CA ADS Reference Guide for correct syntax and recompile the process.
Module:
ADSOGFLO
Severity:
0
Reason:
The defined subroutine name was already used to define a previous subroutine within the same process code. The process code should be checked to ensure the validity of both subroutines. Rename one of the subroutines and recompile the process.
Module:
ADSOGFLO
Severity:
0
Reason:
A subroutine was defined within a process but was never referenced with a CALL statement within the main process or from within another subroutine. Delete the subroutine, if possible, or add a CALL statement where needed, and recompile the process.
Module:
ADSOGFLO
Severity:
0
Reason:
The EXIT command can be used only within a WHILE or ON construct before the END statement. Refer to the CA ADS Reference Guide for correct syntax. Correct the syntax and recompile the process.
Module:
ADSOGFLO
Severity:
0
Reason:
The NEXT SENTENCE command is used only within an IF command; otherwise, the CA ADS dialog compiler ignores the NEXT SENTENCE command. For more information, see the CA ADS Reference Guide. Correct the syntax and recompile the process.
Module:
ADSOGFLO
Severity:
0
Reason:
The #GETSTG macro failed when the CA ADS dialog compiler attempted to allocate a parameter buffer. The return code of the abend was unavailable. Check Register 4 in the snap dump. Register 4 contains the length of the buffer that the CA ADS dialog compiler tried to allocate for the task. If the length in Register 4 is reasonable, contact the database administrator to determine whether current overall system storage conditions will allow allocation of more storage for the task. If the length in Register 4 is too high, print the snap dump and contact the database administrator.
Module:
ADSOGFLO
Severity:
3
Reason:
The process contains no control commands. The process must contain at least one control statement. For more information about control commands, see the CA ADS Reference Guide. Correct the syntax and recompile the process.
Module:
ADSOGFLO
Severity:
0
Reason:
The END command must be paired with a DO or REPEAT command. For more information, see the CA ADS Reference Guide. Correct the syntax, check for mismatched END statements, and recompile the process.
Module:
ADSOGFLO
Severity:
0
Reason:
The CA ADS dialog compiler could not add a literal to the literal pool because of an invalid condition. The statement was flushed. Contact the database administrator. Note that as of Release 1.1 no condition causes this error to be displayed.
Module:
ADSOGFLO
Severity:
0
Reason:
The module name parameter in the INCLUDE statement is longer than 32 characters and/or it contains illegal characters. For more information, see the CA ADS Reference Guide.
Module:
ADSOGINC
Severity:
0
Reason:
The node branch value passed to the ADSOGINC module is outside the range of the node tree used by this module. This is an internal error. Print the snap dump.
Module:
ADSOGINC
Severity:
3
Reason:
The node tree for the ADSOGINC module contains a branch value that is outside the range of the branch tree handled by this module. This is an internal error. Print the snap dump.
Module:
ADSOGINC
Severity:
3
Reason:
A #ACALL macro was issued, but there was no space in the PSA stack to save the registers. A snap dump of the task appears with this message. This is an internal error.
Module:
ADSOGINC
Severity:
3
Reason:
The process module named in the INCLUDE statement does not exist in the dictionary as a MODULE-067 record. Make sure that the process name was spelled correctly and that the process was added to the dictionary. The process may have been deleted from the dictionary.
Module:
ADSOGINC
Severity:
0
Reason:
The specific version of the process module specified in the INCLUDE statement does not exist in the dictionary as a MODULE-067 record. A minimum of one MODULE-067 record with the specified process name does exist. Use IDD to determine why the version requested does not exist.
Module:
ADSOGINC
Severity:
0
Reason:
An INCLUDE statement cannot reference the process in which it is nested. Such recursive INCLUDE statements are not allowed. For more information, see the CA ADS Reference Guide.
Module:
ADSOGINC
Severity:
0
Reason:
After processing the TEXT-088 records for an included module, the CA ADS dialog compiler failed to re-obtain the INCLUDE statement from the initiating process module. The db-key for the INCLUDE statement has changed, because the process module was either changed or deleted from the dictionary by another user during compilation. Make sure the module still exists in the data dictionary and recompile it. If the problem persists, print the snap dump and contact the database administrator.
Module:
ADSOGINC
Severity:
3
Reason:
The last recognized keyword in this process module was an INCLUDE statement. The statement was not terminated with a period. Terminate all process statements with a period, scan the last few commands for accuracy, and recompile the process.
Module:
ADSOGINC
Severity:
0
Reason:
When the INCLUDE command is recognized, the CA ADS dialog compiler automatically performs a GETSTG. If the GETSTG fails, contact the database administrator. Wait until storage requirements have been reevaluated before recompiling the process module.
Module:
ADSOGINC
Severity:
3
Reason:
The process module named was found in the dictionary as a MODULE-067 record, but the language type is not defined as PROCESS, as required for an included module name. Either the process was defined incorrectly in the dictionary, or the process name was specified incorrectly in the INCLUDE statement.
Module:
ADSOGINC
Severity:
0
Reason:
None of the allowed keywords was found at this point (marked by a $) in the INCLUDE command, including the period, which is an end of statement marker. All tokens, that is, keywords and their associated parameters, are ignored until after the next period is scanned.
Module:
ADSOGINC
Severity:
0
Reason:
The length of the process version is greater than four characters, less than zero numeric characters, or is nonnumeric. For more information about the correct syntax, see the CA ADS Reference Guide.
Module:
ADSOGINC
Severity:
0
Reason:
When the FDB being generated reached the point at which it was to begin undergoing a conversion to executable code format, the variable that should have contained the address of the half-built FDB was found to contain zeros. This is probably an internal error. Print the snap dump and contact Technical Support.
Module:
ADSOGEXC
Severity:
3
Reason:
During an attempt to allocate some space in the GWA (via the ALCSTG routine), an unrecoverable error was encountered. Either there was not enough storage in the storage pool to satisfy any further requests for space or an internal error has occurred. Begin by taking the problem to your DBA to determine the availability of space in the storage pool. If storage space is not the problem, print the snap dump and contact Technical Support.
Module:
ADSOGEXC
Severity:
3
Reason:
During an attempt to interpret an already-built CME in order to convert the FDB to executable code, the CME class/function values were not found in a prebuilt table. This is probably an internal error. Print the snap dump and contact Technical Support.
Module:
ADSOGEXC
Severity:
3
Reason:
An error occurred during an attempt to acquire storage for the executable code of a fixed dialog block (FDB). Print the snap dump. The storage length requested is in Register 5. Register 3 contains the return code. For more information about GETSTG return codes, see the CA IDMS DML Reference Guide for Assembler.
Module:
ADSOGEXC
Severity:
3
Reason:
While trying to convert an FDB with CMEs to one with executable code, ADSOGEXC found one of the CMEs to have a negative length. This is probably an internal error. Print the snap dump and contact Technical Support.
Module:
ADSOGEXC
Severity:
3
Reason:
While trying to convert an FDB with CMEs to one with executable code, ADSOGEXC encountered an internal error. Print the snap dump and contact Technical Support.
Module:
ADSOGEXC
Severity:
3
Reason:
During an attempt to convert an FDB with CMEs to one with executable code, an error was found while trying to locate the line number table (LNT) for that particular process. This is probably an internal error. Print the snap dump and contact Technical Support.
Module:
ADSOGEXC
Severity:
3
Reason:
While trying to convert an FDB with CMEs to one with executable code, ADSOGEXC could not find the line number table associated with a particular process. This is probably an internal error. Print the snap dump and contact Technical Support.
Module:
ADSOGEXC
Severity:
3
Reason:
During an attempt to convert an FDB with CMEs to one with executable code, a calculation that should have resulted in a positive value did not. This is probably an internal error. Print the snap dump and contact Technical Support.
Module:
ADSOGEXC
Severity:
3
Reason:
During an attempt to convert an FDB with CMEs to one with executable code, the length calculated for the new FDB was negative. This is probably an internal error. Print the snap dump and contact Technical Support.
Module:
ADSOGEXC
Severity:
3
Reason:
During an attempt to convert an FDB with CMEs to one with executable code, no entries were found in the internal offset table. (The internal offset table is used to determine new offsets for true/false and conditional CMEs in order that the correct path of logic is followed at runtime.) This is probably an internal error. Print the snap dump and contact Technical Support.
Module:
ADSOGEXC
Severity:
3
Reason:
During an attempt to convert an FDB with CMEs to one with executable code, the internal CME offset table, which must contain the offset of every CME in the FDB with CMEs, has been found to contain bad information. This is probably an internal error. Print the snap dump. Contact Technical Support.
Module:
ADSOGEXC
Severity:
3
Reason:
During an attempt to convert an FDB with CMEs to one with executable code, the newly built FDB is found to be larger than the storage that was allocated to hold it. This is probably an internal error. Print the snap dump. Contact Technical Support.
Module:
ADSOGEXC
Severity:
3
Reason:
During an attempt to convert an FDB with CMEs to one with executable code, a negative length move was attempted while moving data from the old FDB to the newly built FDB. This is probably an internal error. Print the snap dump and contact Technical Support.
Module:
ADSOGEXC
Severity:
3
Reason:
During an attempt to convert an FDB with CMEs to one with executable code, the pointer to the current process control block was lost. This is probably an internal error. Print the snap dump and contact Technical Support.
Module:
ADSOGEXC
Severity:
3
Reason:
During an attempt to convert an FDB with CMEs to one with executable code, no entries were found in the internal offset table, which should have one entry per CME. This is probably an internal error. Print the snap dump and contact Technical Support.
Module:
ADSOGEXC
Severity:
3
Reason:
During an attempt to convert an FDB with CMEs to one with executable code, a PEXC (process level control block) was found that did not point to a linked list of EXC control blocks. (One control block should exist for each CME in the process.) This is probably an internal error. Print the snap dump and contact Technical Support.
Module:
ADSOGEXC
Severity:
3
Reason:
During an attempt to convert an FDB with CMEs to one with executable code, the pointer to the current process control block was lost. This is probably an internal error. Print the snap dump and contact Technical Support.
Module:
ADSOGEXC
Severity:
3
Reason:
During an attempt to convert an FDB with CMEs to one with executable code, no entries were found in the internal offset table, which should have one entry per CME. This is probably an internal error. Print the snap dump and contact Technical Support.
Module:
ADSOGEXC
Severity:
3
Reason:
During an attempt to convert an FDB with CMEs to one with executable code, the internal CME offset table, which must contain the offset of every CME in the FDB that has CMEs, has been found to contain invalid information. This is probably an internal error. Print the snap dump. Contact Technical Support.
Module:
ADSOGEXC
Severity:
3
Reason:
During the conversion of an FDB from CMEs to executable code, the dialog compiler could not locate the first RSE within the new FDB for a process that has been specified more than once within the dialog. This is an internal error. Print the dump and contact Technical Support.
Module:
ADSOGEXC
Severity:
3
Reason:
An error occurred during an attempt to acquire storage for work areas for use in executable code generation. Print the snap dump. The storage length requested is in Register 6. Register 3 contains one of the following error messages:
Module:
ADSOGEXC
Severity:
3
Reason:
The user has selected more than one dialog from the Dialog Selection screen. Press the ENTER key to reinitialize the Dialog Selection screen. Select the name of a dialog by performing either of the following actions:
Module:
ADSORUN1
Severity:
0
Reason:
A nonzero return code was returned during an attempt to map in the Dialog Selection Screen, probably because of hardware problems or terminal disconnect action. See the #MREQ macro in the CA IDMS DML Reference Guide for Assembler. Print the dump from the DC log. Register 2 (user mode Registers) contains the return code.
Module:
ADSORUN1
Severity:
3
Reason:
The record for the Dialog Selection Screen was previously written to scratch across the pseudoconverse. An attempt to delete the scratch area has resulted in a nonzero return code. See the #DELSCR macro in the CA IDMS DML Reference Guide for Assembler. Print the dump from the log. Register 2 (user mode Registers) contains the return code.
Module:
ADSORUN1
Severity:
3
Reason:
The application's record buffers were previously written to scratch across the pseudoconverse. An attempt to delete the scratch area has resulted in a nonzero return code. See the #DELSCR macro in the CA IDMS DML Reference Guide for Assembler. Print the dump from the DC log. Register 2 (user mode Registers) contains the return code.
Module:
ADSORUN1
Severity:
3
Reason:
A nonzero return code was returned during an attempt to map out the Dialog Selection Screen, probably because of an installation error. ADSOMENU should be found in dictionary's load area. Check to see if load module ADSOMENU is in dictionary load area. If it is not, install it from the distribution library. If it is there, print the dump from the log. Register 2 (user mode Registers) contains the return code.
Module:
ADSORUN1
Severity:
3
Reason:
An attempt to write the menu record to scratch resulted in a nonzero return code. See the #PUTSCR macro in the CA IDMS DML Reference Guide for Assembler. Print the dump from the DC log. Register 2 (user mode Registers) contains the return code.
Module:
ADSORUN1
Severity:
3
Reason:
An attempt to read the menu record to scratch resulted in a nonzero return code. See the #GETSCR macro in the CA IDMS DML Reference Guide for Assembler. Print the dump from the DC log. Register 2 (user mode Registers) contains the return code.
Module:
ADSORUN1
Severity:
3
Reason:
The Task Application Table (TAT) was loaded successfully, but the load module did not contain the identifier TAT* in the first four bytes. A load module with the name $ACF@TAT that was not created by the application compiler was found in the load area. Note that $ACF@TAT is a reserved load module name for the TAT. Delete the load module with that name from the load area. First punch and then rename if necessary.
Module:
ADSORUN1
Severity:
3
Reason:
During set-up for an application that was defined by the CA ADS application compiler, the Application Definition Block (ADB) was loaded successfully, but the load module did not contain the identifier ADB* in the first four bytes. The error probably occurred because a load module with the name of an application is in the load area, but that load module is not defined for an application. Note that application names must be unique. A dialog or a map cannot have the same name. Either rename the application and compile it, or delete the load module with the same name, and then compile the application.
Module:
ADSORUN1
Severity:
3
Reason:
During setup for an application that was defined by the CA ADS application compiler, the task code was found in the TAT, but not in the ADB, which was probably deleted by means of IDD. Note that application maintenance should be handled strictly by using the CA ADS application compiler. Delete the application and redefine it using the CA ADS application compiler.
Module:
ADSORUN1
Severity:
3
Reason:
The user did not have the proper authority to execute an application defined by the CA ADS application compiler. The operator must request the proper security class from the DC administrator.
Module:
ADSORUN1
Severity:
5
Reason:
#LOAD returned an unacceptable return code while attempting to load the TAT. See the #LOAD macro in the CA IDMS DML Reference Guide for Assembler. The error probably resulted because of insufficient storage in the program pool; therefore, increase the size of the program pool.
Module:
ADSORUN1
Severity:
3
Reason:
No useable PDE (Program Definition Element) was found for the ADB to be #LOADed. See the #LOAD macro in the CA IDMS DML Reference Guide for Assembler. The return code was 20. The minor code is displayed in the message text.
Module:
ADSORUN1
Severity:
3
Reason:
The application compiler has a bug because the ADB indicates that the top function for an application compiled by CA ADS is a user program or a system function, which is impossible. Note that the top function for an application must be a dialog or a menu.
Module:
ADSORUN1
Severity:
3
Reason:
The storage for the Online Terminal Block (OTB) was acquired as relocatable storage and was relocated by DC across a pseudoconverse. The relocated storage does not contain the eye catcher OTB* in the first four positions. The address that DC passed back to CA ADS of the relocated storage is probably incorrect. This indicates an error either in the DC storage manager or in the CA ADS runtime system. Contact Technical Support.
Module:
ADSORUN1
Severity:
3
Reason:
The storage for a Variable Dialog Block (VDB) was acquired as relocatable storage and was relocated by DC across a pseudoconverse. The relocated storage does not contain the eye catcher VDB* in the first four positions. The address of the relocated storage that DC passes back to CA ADS is probably incorrect. This indicates an error either in the DC storage manager or in the CA ADS runtime system. Contact Technical Support.
Module:
ADSORUN1
Severity:
3
Reason:
The storage for the Online Terminal Block Extension (OTBX) was acquired as relocatable storage. DC relocated it across a pseudoconverse. The relocated storage does not contain the eye catcher OTX* in the first four positions. The address of the relocated storage that DC passes back to CA ADS is probably incorrect. This indicates an error either in the DC storage manager or in the CA ADS runtime system. Contact Technical Support.
Module:
ADSORUN1
Severity:
3
Reason:
The CA ADS runtime system has determined that it must display the Dialog Selection screen so that the terminal operator can select the dialog to be executed. However, there is no LTE (Logical Terminal Element) associated with the task that invoked the runtime system, and therefore no terminal I/O may be performed.
The probable cause is that the runtime system was invoked by a queue-initiated task code that DC issues when a queue threshold was reached. The task code was neither the name of a dialog nor a task used to invoke an application compiled by CA ADS. The runtime system, not knowing the dialog to be executed, tried to display the Dialog Selection screen, which is not possible.
Queue-initiated task codes used to invoke CA ADS must also be the name of a mainline dialog used to initiate an application or a task code defined with the CA ADS application compiler to invoke an application. Either change the queue-initiated task code, or compile the required dialog or application via ADSC.
Module:
ADSORUN1
Severity:
3
Reason:
The runtime system has determined that one of the parameters (nodename, dbname, or dialog name) entered with the task code was longer than eight characters. Re-enter the task code followed by the correct name(s) for these entities.
Module:
ADSORUN1
Severity:
0
Reason:
An error other than PDE.NOT.FOUND was encountered during #LOAD of an ADB. See the #LOAD macro in the CA IDMS DML Reference Guide for Assembler manual for the meanings of the return codes. The return code is displayed in the message text.
Module:
ADSORUN1
Severity:
3
Reason:
During memory cache initialization, a storage request for DSPE control blocks failed. The database file is not cached. Processing continues.
Module:
RHDCOMVS, RHDCODVS, RHDCOCMS
Severity:
0
Reason:
A DSPSERV CREATE returned a non-zero return code. The database file is not cached. Processing continues.
Module:
RHDCOMVS, RHDCOCMS
Severity:
0
Reason:
In z/OS and z/VM an ALESERV ADD/DELETE failed. In z/VSE, a CADSPACE DELETE call failed. The error is reported. Processing continues.
Module:
RHDCOMVS, RHDCOCMS, RHDCODVS
Severity:
0
Reason:
During dataspace processing a CAISPACE function returned a non-zero return code. The function code and return code are displayed. If it was a Query or Create the database file is not cached. In all cases processing continues. Function codes are:
Return codes are:
Module:
RHDCODVS
Severity:
0
Reason:
During the start-up of a CA IDMS/DC/UCF system or batch job, the system was unable to find LMP keys indicating that this version of IDMS could run on this CPU. The probable cause is that the necessary keys were not properly installed using the CA Common Service program CAIRIM. For more information, see the CA IDMS Installation and Maintenance Guide—z/OS.
Module:
RHDCOXXX
Severity:
0
Reason:
During the start-up of a CA IDMS/DC/UCF system or batch job, the system was unable to find a valid CA Common Services environment for this version of IDMS. The probable cause is that CAIRIM was not run with the proper input parameters for product CA IDMS. Note that it is valid to run an older release of CA IDMS using an SVC from a later release. CAIRIM, however, must be run with the proper VERSION and INIT values for each version of CA IDMS which will run on the CPU. For more information, see the CA IDMS Installation and Maintenance Guide—z/OS.
Module:
RHDCOXXX
Severity:
0
Reason:
The IDMS system issued a GETMAIN request to the operating system for the indicated number of bytes. There was not enough storage available to satisfy the request. Increase the region size or modify the CA IDMS SYSGEN to use less resources.
Module:
RHDCOXXX
Severity:
0
Reason:
During the start-up of a CA IDMS/DC/UCF system or batch job, the specified SVC was older than the preferred one for this version of IDMS. This can lead to improper operation of the IDMS system. Either the wrong SVC was specified or the wrong version of the SVC was loaded. Note that it is valid to run an older release of CA IDMS using an SVC from a later release. The reverse is not acceptable. Consult the CA IDMS Installation and Maintenance Guide for more information.
Module:
RHDCOS00
Severity:
0
Reason:
An attempt to locate the OTB (Online Terminal Block) via #GETSTG failed because the ADSOMAIN was executed directly without first executing the set-up program, ADSORUN1. See the #GETSTG macro in the CA IDMS DML Reference Guide for Assembler. Note that any DC task code set up to invoke ADSOMAIN must be an internal task; a user's DC program should not invoke ADSOMAIN.
Module:
ADSORUN2
Severity:
3
Reason:
The dialog load module, FDB (Fixed Dialog Block), is invalid because the trailing identifier is missing.
Module:
ADSORUN2
Severity:
3
Reason:
The dialog load module, FDB (Fixed Dialog Block), is invalid because the offset pointer to the record (RDE) table is incorrect.
Module:
ADSORUN2
Severity:
3
Reason:
The dialog load module, FDB (Fixed Dialog Block), is invalid because the offset pointer to the premap process (PME) is incorrect.
Module:
ADSORUN2
Severity:
3
Reason:
The dialog load module, FDB (Fixed Dialog Block), is invalid because the offset pointer to the Literal Pool (LITPOOL) is incorrect.
Module:
ADSORUN2
Severity:
3
Reason:
The record for the Dialog Selection Screen map previously was written to scratch across the pseudo converse. An attempt to delete the scratch area resulted in a nonzero return code. See the #DELSCR macro in the CA IDMS DML Reference Guide for Assembler. Print the dump from the DC log.
Module:
ADSORUN2
Severity:
3
Reason:
The application's record buffers previously were written to scratch across the pseudoconverse. An attempt to delete the scratch area resulted in a nonzero return code. See the #DELSCR macro in the CA IDMS DML Reference Guide for Assembler. Print the dump from the DC log.
Module:
ADSORUN2
Severity:
3
Reason:
An attempt to acquire storage from the DC-storage pool failed because the storage pool does not have enough storage. See the #GETSTG macro in the CA IDMS DML Reference Guide for Assembler. Increase the size of the storage pool if the problem continues.
Module:
ADSORUN2
Severity:
3
Reason:
The #LOAD return code indicates why the user's attempt to load the dialog's load module failed. See the #LOAD macro in the CA IDMS DML Reference Guide for Assembler.
Module:
ADSORUN2
Severity:
3
Reason:
The dialog load module, FDB (Fixed Dialog Block), is invalid because the offset pointer to the subschema area name table (SSAN) is incorrect.
Module:
ADSORUN2
Severity:
3
Reason:
The load module is not a dialog load module (FDB) because the first four bytes of identifier FDB* were missing from the load module. Note that only load modules created by the dialog compiler as FDBs can be executed as dialogs by the CA ADS runtime system.
Module:
ADSORUN2
Severity:
0
Reason:
After having issued a link, invokes, or display command, CA ADS reloaded the dialog and found that either its date or time stamp, or both, had changed. Note that the dialog cannot be recompiled while currently active in an application thread.
Module:
ADSORUN2, ADSORUN3
Severity:
0
Reason:
The dialog load module, FDB (Fixed Dialog Block), is invalid because the offset pointer to the first response process (RSE) is incorrect.
Module:
ADSORUN2
Severity:
3
Reason:
The dialog load module, FDB (Fixed Dialog Block), is invalid because the offset pointer to the premap process is null and no mapname was found.
Module:
ADSORUN2
Severity:
3
Reason:
The #MREQ return code indicates why an attempt to map in the dialog's map failed. See the #MREQ macro in the CA IDMS DML Reference Guide for Assembler.
Module:
ADSORUN2
Severity:
1
Reason:
The #MREQ return code indicates why an attempt to map out the dialog's map failed. See the #MREQ macro in the CA IDMS DML Reference Guide for Assembler.
Module:
ADSORUN2
Severity:
1
Reason:
The #PUTSCR return code indicates why an attempt to write the application's record buffers to scratch failed. See the #PUTSCR macro in the CA IDMS DML Reference Guide for Assembler.
Module:
ADSORUN2
Severity:
3
Reason:
The #GETSTG return code indicates why an attempt to acquire storage from the DC storage pool for the application's record buffers failed. See the #GETSTG macro in the CA IDMS DML Reference Guide for Assembler. Increase the size of the storage pool if the problem continues.
Module:
ADSORUN2
Severity:
3
Reason:
The #GETSCR return code indicates why an attempt to read the application's record buffers back into the storage pool from the scratch area failed. See the #GETSCR macro in the CA IDMS DML Reference Guide for Assembler.
Module:
ADSORUN2
Severity:
3
Reason:
A bug in either the CA ADS runtime system or in the dialog compiler caused a logical error while trying to initialize a record buffer. Print the dump.
Module:
ADSORUN2
Severity:
3
Reason:
The action code in the Online Terminal Block (OTB), which specifies the next action for ADSOMAIN, is invalid. Print the dump.
Module:
ADSORUN2
Severity:
3
Reason:
The dialog's load module (FDB) was loaded successfully, but the dialog name in the FDB does not match the load module name. These two names must be the same. Punch and reload the dialog load module, specifying the same name for both the load module and the dialog.
Module:
ADSORUN2
Severity:
3
Reason:
During an attempt to restore record buffers from scratch, a Variable Record Element (VRE) was found in the Variable Dialog Block (VDB) with no corresponding record buffer. Print the dump.
Module:
ADSORUN2
Severity:
3
Reason:
The #MREQ return code indicates why an attempt to map in the standard message map (ADSERRMP) failed. See the #MREQ macro in the CA IDMS DML Reference Guide for Assembler.
Module:
ADSORUN2
Severity:
3
Reason:
The #MREQ return code indicates why an attempt to map out the standard message map (ADSERRMP) failed. See the #MREQ macro in the CA IDMS DML Reference Guide for Assembler.
Module:
ADSORUN2
Severity:
3
Reason:
A record associated with the dialog was too large to fit into the buffer. Note that the secondary buffer size defined for CA ADS in the system generation ADSO statement must be at least large enough to hold the largest record for all applications. Either reduce the size of the record or increase the buffer size specifications on the ADSO statement.
Module:
ADSORUN2
Severity:
0
Reason:
An attempt to load the dialog load module (FDB) failed because the dialog's load module was not found in the load area. Either the dialog's load module was deleted from the load area or the dialog was never compiled. Use the dialog compiler to compile the dialog.
Module:
ADSORUN2
Severity:
0
Reason:
The load module (FDB) for the first dialog to be executed for the application was not flagged as a mainline dialog. Note that the first dialog to execute for an application must be compiled as a mainline dialog. To specify "mainline" on the program is not sufficient. Recompile the dialog as a mainline dialog.
Module:
ADSORUN2
Severity:
0
Reason:
A LINK TO PROGRAM command was encountered, but the user program either was not found in the load library or it could not be loaded. Either the program was never link edited into the local library or the DC/UCF system disabled the program.
Module:
ADSORUN2
Severity:
0
Reason:
The amount of storage remaining in the internal program stack cannot support another dialog in the application thread, which was discovered during variable dialog block (VDB) creation. CA ADS cannot support the temporary working storage needed for the application's resource requirements.
Module:
ADSORUN2
Severity:
0
Reason:
The number of map records as specified in the FDB header does not equal the number of map record definition elements (RDEs) in the FDB. Print the dump from the DC log.
Module:
ADSORUN2
Severity:
3
Reason:
A RETURN command that caused a return to a mapless dialog was coded without the CONTINUE option. Note that a simple RETURN command (without the CONTINUE option) specifies that the dialog's map be displayed. Change the RETURN command to RETURN CONTINUE.
Module:
ADSORUN2
Severity:
0
Reason:
A logical record buffer, previously allocated for a higher level dialog, does not contain the same number of logical record element records as is indicated for the current dialog. The logical record definition was changed and only one of the dialogs was recompiled. Recompile the other dialog.
Module:
ADSORUN2
Severity:
0
Reason:
Either one of the RDEs in the logical record definition was not flagged as an LR element, or the count of the number of LR elements in the LR-RDE does not equal the number of LR element RDEs. Print the dump.
Module:
ADSORUN2
Severity:
3
Reason:
The user interrupted the mapping operation by striking an attention or a break key, and a return code of 8 was returned from a mapping operation for the dialog's map. Note that this will not occur on a standard 3270-type terminal. See the #MREQ macro in the CA IDMS DML Reference Guide for Assembler.
Module:
ADSORUN2
Severity:
0
Reason:
A return code of 36 (X'24') was returned from a mapping operation for the dialog's map. The map load module or an unlinked edit or code table for the map was not found in the load area. See the #MREQ macro in the CA IDMS DML Reference Guide for Assembler. Generate the map or any edit and code tables for the map, or both.
Module:
ADSORUN2
Severity:
0
Reason:
A return code of 40 (X'28') was returned from a mapping operation for the dialog's map because the map was not compiled to be mapped to the terminal type used. See the #MREQ macro in the CA IDMS DML Reference Guide for Assembler. Change the map and recompile it to map to the terminal type required.
Module:
ADSORUN2
Severity:
0
Reason:
A return code of 48 (X'30') was returned from a map out operation for the dialog's map. See the CA IDMS DML Reference Guide for Assembler. The data in the field in the record that maps to the specified row and column on the screen could not be displayed on the screen. For example, an alphabetic field mapping to a numeric field could not be displayed on the screen. Find the field in the record from the dump, and, if necessary, correct the data type for the field or dialog coding.
Module:
ADSORUN2
Severity:
1
Reason:
A return code of 44 (X'2C') was returned from a mapping operation for the dialog's map. An edit routine associated with the dialog's map found an error in the field that maps to the specified row and column on the screen.
See the #MREQ macro in the CA IDMS DML Reference Guide for Assembler. Change the dialog code or edit routine if necessary.
Module:
ADSORUN2
Severity:
1
Reason:
A return code of 52 (X'34') was returned from a mapping operation for the dialog's map because the load library does not contain the edit routine for the field that maps to the screen row and column specified. Link the edit routine into the load library.
Module:
ADSORUN2
Severity:
1
Reason:
A return code of 4 was returned from a mapping operation for the dialog's map. A load module was found with the same name as an edit or code table for the field that maps to the row and column specified, but the load module did not resemble an edit or code table. See the #MREQ macro in the CA IDMS DML Reference Guide for Assembler. Note that edit and code table names must be unique. Rename and compile the edit or code table.
Module:
ADSORUN2
Severity:
1
Reason:
A menu function in an application compiled by CA ADS has no valid responses that can be displayed. Either the menu has no valid responses or the user's security classes prevent any valid responses for the menu from appearing. Note that a menu for a CA ADS application can be tailored to display only responses for which the user has security.
Module:
ADSORUN2
Severity:
0
Reason:
The Task Application Table (TAT) was loaded successfully, but the load module did not contain the identifier TAT* in the first four bytes. A load module with the name $ACF@TAT, which was not created by the application compiler, was found in the load area. Note that $ACF@TAT is a reserved load module name for the TAT. Delete the load module with that name from the load area. First punch, then rename the load module if necessary.
Module:
ADSORUN2
Severity:
3
Reason:
During setup for an application that was defined by CA ADS, the Application Definition Block (ADB) was loaded successfully, but the load module did not contain the identifier ADB* in the first four bytes. The error probably occurred because a load module with the name of an application is in the load area, but that load module is not defined for an application. Note that application names must be unique. A dialog or a map cannot have the same name. Either rename the application and compile it, or delete the load module with the same name, and then compile the application.
Module:
ADSORUN2
Severity:
3
Reason:
#LOAD returned an unacceptable return code while attempting to load the TAT. See the #LOAD macro in the CA IDMS DML Reference Guide for Assembler. The error probably resulted because of insufficient storage in the program pool; therefore, increase the size of the program pool.
Module:
ADSORUN2
Severity:
3
Reason:
#LOAD returned an unacceptable return code while attempting to load the ADB. See the #LOAD macro in the CA IDMS DML Reference Guide for Assembler. The error probably resulted because of insufficient storage in the program pool; therefore, increase the size of the program pool.
Module:
ADSORUN2
Severity:
3
Reason:
The storage for the Online Terminal Block (OTB) was acquired as relocatable storage and DC relocated it across a pseudoconverse. The relocated storage does not contain the eye catcher OTB* in the first four positions. The address of the relocated storage that DC passed back to CA ADS is probably incorrect. This indicates an error either in the DC storage manager or in the CA ADS runtime system. Contact Technical Support.
Module:
ADSORUN2
Severity:
3
Reason:
The storage for a Variable Dialog Block (VDB) was acquired as relocatable storage DC relocated it across a pseudoconverse. The relocated storage does not contain the eye catcher VDB* in the first four positions. The address of the relocated storage that DC passes to CA ADS is probably incorrect. This indicates an error either in the DC storage manager or in the CA ADS runtime system. Contact Technical Support.
Module:
ADSORUN2
Severity:
3
Reason:
The storage for the Online Terminal Block Extension (OTBX) was acquired as relocatable storage DC relocated it across a pseudoconverse. The relocated storage does not contain the eye catcher OTX* in the first four positions. The address of the relocated storage that DC passed back to CA ADS is probably incorrect. This indicates an error either in the DC storage manager or in the CA ADS runtime system. Contact Technical Support.
Module:
ADSORUN2
Severity:
3
Reason:
CA ADS is running with relocatable storage, but the Relocatable Storage Anchor Block (RLO) in which the addresses of relocatable storage blocks are saved is missing. This is an error in the CA ADS runtime system. Contact Technical Support.
Module:
ADSORUN2
Severity:
3
Reason:
The storage for the Online Terminal Block (OTB) was acquired as relocatable storage and DC relocated it across a pseudoconverse. However, the address of the OTB after the pseudoconverse was found to be invalid. The address of the relocatable storage that DC passed back to CA ADS after the pseudoconverse is incorrect. This indicates an error in the DC storage manager. Contact Technical Support.
Module:
ADSORUN2
Severity:
3
Reason:
During a DC debugger session, when the runtime system was about to map out the dialog abort DBUG screen, the CA ADS runtime system could not locate the DLB control block that is required for a debugging session. This is a system internal error. Run a PLOG and contact Technical Support.
Module:
ADSORUN2
Severity:
3
Reason:
The length of a buffer that was previously allocated for a record used by a dialog differs from the length of the record, as specified in the dialog's load module. This can indicate that the record was changed but that not all of the dialogs or applications using the record were recompiled. When a record used in a CA ADS application is changed, all dialogs and applications that use the record must be recompiled.
Module:
ADSORUN2
Severity:
0
Reason:
The dialog issued a DISPLAY command during dialog execution; however, terminal I/O is impossible because there is no LTE (Logical Terminal Element) associated with the task. The probable cause is that the runtime system was invoked by a queue-initiated task code that DC issued when a queue threshold was reached. When the dialog subsequently tried to issue a DISPLAY command, the runtime system discovered that there was no logical terminal to which the map could be displayed. Dialogs that are invoked through queue-initiated tasks cannot issue DISPLAY commands. Change the dialog process logic so that DISPLAY commands are not issued when the dialog is running under a queue-initiated task. The dialog does not have to be a mapless dialog, but that is one way to ensure that DISPLAY commands are not issued at runtime.
Module:
ADSORUN2
Severity:
3
Reason:
The indicated command is valid in the BATCH environment only and cannot be executed in the online environment.
Module:
ADSORUN2
Severity:
0
Reason:
The runtime system has loaded a dialog that contains one or more file maps. A dialog containing a file map can be executed only in the batch environment.
Module:
ADSORUN2
Severity:
0
Reason:
CA ADS Batch issues this message which corresponds to the DC171028 online message. An attempt to load the dialog load module (FDB) failed because the dialog's load module could not be found in the load area or load library (CDMSLIB or STEPLIB).
Make sure that the dialog has been successfully compiled in the load area or punched to your loadlib. If it is in a secondary load area, make sure you include the appropriate DICTNAME/DICTNODE control statements in your SYSIPT file.
If the dialog was punched, make sure the data set names in the JCL are correct. It might be simplest to omit CDMSLIB from the JCL and include everything in the STEPLIB.
If the dialog load module is in the load area, keep in mind that an attempt by CA ADS Batch to search the load area could fail for a variety of reasons (in which case CA ADS Batch goes on to examine CDMSLIB or STEPLIB). For example, CA ADS Batch might not be able to bind a run unit to examine the load area. This could mean that CA ADS Batch is short on storage or that the load area is locked by another job.
Module:
ADSORUN3
Severity:
0
Reason:
A fatal error occurred during the decompression of the compressed record buffer blocks. This is a system internal error. Run the PRINT LOG utility and contact Technical Support.
Module:
ADSORUN2
Severity:
3
Reason:
When CA ADS passes a run unit to a user program by means of a LINK SAVE command, the user program must not open a new run unit. Otherwise, the currencies that CA ADS will restore when it gets control back will be potentially damaging.
Module:
ADSORUN2
Severity:
0
Reason:
The LINK TO DIALOG USING (MAP-CONTROL) command cannot be executed because the calling dialog uses a different map than the linked dialog. The map name, version, and date/time stamp must be the same in both dialogs.
Module:
ADSORUN2
Severity:
3
Reason:
When issuing a link to program IDMSOLQS from CA ADS, record UNIVERSAL-COMMUNICATIONS-ELEMENT version 2 is required to be either the first or second record in the USING records list.
Module:
ADSORUN2
Severity:
0
Severity:
0
Reason:
The class for the command element (CME) could not be identified. Print the snap dump.
Module:
ADSOCDRV
Severity:
3
Reason:
The record <name> used by the dialog <dialog> is out of sync with the procedure or function SQL definition. The dialog must be recompiled.
Module:
ADSORUN3
Severity:
0
Reason:
An RBE* header was expected at the address given in the message but was not found. The RBE* headers were validated immediately following a return from a link to a user-written program. All RBBs are snapped. Also, see accompanying message DC171068 for the names of the current dialog and the name of the program to which the dialog linked.
Module:
ADSORUN2
Severity:
0
Reason:
The RBE* headers were validated immediately following a return from a link to a user-written program. One RBE has been overlaid. All RBBs are snapped. Also, message DC171068 shows the names of the current dialog and the name of the program to which the dialog linked.
Module:
ADSORUN2
Severity:
0
Reason:
The RBE* headers were validated when linking from a dialog to another dialog. An RBE header was found to be overlaid. The address of the expected RBE* is displayed and the task is abended with a snap dump. The overlay is most likely due to a subscript out of range when running with executable code, an invalid data base procedure, or map edit module associated with the record in the RBB that immediately precedes the address in the message. To identify the error, identify the record immediately preceding the message address. If the preceding record has occurring fields, recompile the dialog using symbol table, rerun and hope for a 'SUBSCRIPT OUT OF RANGE' message such as DC175010, DC175017, or DC178018. If the preceding record is used by a map edit module, SNAP RBB before each DISPLAY and at entry to each response process. If the preceding record is used by a data base procedure, SNAP RBB before and after each DML command that uses the data base procedure.
Module:
ADSORUN2
Severity:
3
Reason:
This is an internal error. ADSORUN2 called the ADSORUN3 routine to allocate records when a dialog begins and the code returned from ADSORUN3 ALRECS routine was not a valid code. The task is abended with a snap dump.
Module:
ADSORUN2
Severity:
3
Reason:
This message appears in conjunction with DC171069. The RBE headers were validated when linking from a dialog to another dialog. An RBE header was found to be overlaid. The name of the dialog that is most likely to have caused the overlay and the last control command are displayed.
Module:
ADSORUN3
Severity:
0
Reason:
The class for the command element (CME) could not be identified. Print the snap dump.
Module:
ADSOCDRV
Severity:
3
Reason:
The address of the command element (CME) did not fall within the process. Print the snap dump.
Module:
ADSOCDRV
Severity:
3
Reason:
An attempt to acquire working storage from the program stack failed. CA ADS cannot support the application's resource requirements for temporary working storage.
Module:
ADSOCDRV
Severity:
0
Reason:
A return code of 12 (X'0C') was returned after asking DC to determine a system default key assignment, because default assignments were not specified at DC/UCF system generation time for the CA ADS runtime system. Note that a KEYS statement must be specified for ADSORUN at DC/UCF system generation time. Ask the DC administrator to include a KEYS statement for ADSORUN in system generation statements.
Module:
ADSOCDRV
Severity:
0
Reason:
An invalid response was entered or selected from a menu screen, or security prevents execution of a valid response. Note that key struck or response field value entered must be defined as a valid response either for the dialog or for the application.
Module:
ADSOCDRV
Severity:
0
Reason:
The user selected more than one response from an application menu screen. Note that only one response at a time may be selected from an application screen.
Module:
ADSOCDRV
Severity:
0
|
Copyright © 2014 CA.
All rights reserved.
|
|