|
|
|
Reason:
The parameters passed to the Database Manager are not compatible with the action requested.
System Action:
The call is rejected.
User Action:
Correct the Database Manager call and retry.
Reason:
The specified sequence name does not exist.
System Action:
The Database Manager call is rejected.
User Action:
Correct the Database Manager call and retry.
Reason:
The Database Manager call parameters conflict with those used when the sequence was created.
System Action:
The Database Manager call is rejected.
User Action:
Correct the Database Manager call and retry.
Reason:
An error occurred when trying to access the database file.
System Action:
The Database Manager call is rejected.
User Action:
Determine the cause of the error from the return code and feedback code indicated and retry.
Reason:
The file in which the requested category resides has not been opened.
System Action:
The Database Manager call is rejected.
User Action:
Open the file in which the requested category resides and retry.
Reason:
The requesting user is not authorized to access the requested file.
System Action:
The Database Manager call is rejected.
User Action:
Contact your systems administrator to obtain appropriate file access authorization and retry.
Reason:
The user or job name has exclusive use of the requested application, category or record.
System Action:
The Database Manager call is rejected.
User Action:
Wait until the application, category or record becomes available and retry.
Reason:
A fatal error occurred when attempting to access an NCL LOCK.
System Action:
The Database Manager call is rejected.
User Action:
Determine the cause of the error and retry.
Reason:
The requested action is not a valid Database Manager action.
System Action:
The Database Manager call is rejected.
User Action:
Correct the Database Manager call and retry.
Reason:
No key was supplied for the requested record.
System Action:
The Database Manager call is rejected.
User Action:
Correct the Database Manager call and retry.
Reason:
An error occurred whilst processing an NCL VARTABLE.
System Action:
The Database Manager call is rejected.
User Action:
Determine the cause of the error and retry.
Reason:
Either the application ID or the category ID is not defined to the Database Manager.
System Action:
The Database Manager call is rejected.
User Action:
Correct the Database Manager call or register the application/category in the Database Manager and retry.
Reason:
The record could not be added because it already exists.
System Action:
The Database Manager call is rejected.
User Action:
Change the key of the record being added, or change the function to PUT and retry.
Reason:
A parameter specified on the call to the Database Manager was inconsistent with the category definition. For instance, a generic delete request may not be made on records with alternate keys or records which are cached.
System Action:
The Database Manager call is rejected.
User Action:
Correct the Database Manager call and retry.
Reason:
A fatal error occured because the requested alternate key was found, but the primary key record was not found.
System Action:
The Database Manager call is rejected.
User Action:
Delete the alternate key from the database and recreate the record if necessary.
Reason:
A VSAM feedback code of 14 was returned from an add, delete or put request. This means that the VSAM control interval in which the record resides was locked by another job or user. The Database Manager automatically retries the operation until successful.
System Action:
The requested action is retried automatically until successful.
User Action:
None.
Reason:
The requested maintenance option is invalid.
System Action:
The Database Manager call is rejected.
User Action:
Correct the Database Manager call and retry.
Reason:
The file processing action P1 was not consistent with the options specified when the file was opened. The most likely cause of this error is when an add, update, or delete request is made for a file which is open for read only.
System Action:
The Database Manager call is rejected.
User Action:
If the file is shared by more than one SOLVE region and therefore is only opened for update on one of those regions then perform the required action on the SOLVE region that has update capability. If the file is only accessed by one SOLVE region then close and re-open the file with the appropriate operands for the requested action and then retry.
Reason:
The record type identified by P1 could not be found on the file. This message usually indicates that database corruption has occurred due to a system failure.
System Action:
The Database Manager call is rejected with a return code of 4.
User Action:
This message is usually only issued when a record should be on file but is not. Contact your systems administrator who may be able to run a database clean up to rectify the problem.
Reason:
A delete was attempted on an NCL/CAS entity that is present at a level lower than the primary level in the NCL/CAS concatenation path. P1 is the primary level. Only the primary level in an NCL/CAS concatenation path may be modified.
System Action:
The delete request is rejected and the target entity remains intact.
User Action:
Use the NCL/CAS Copy/Delete/Compare/Apply/Browse facility to delete the entity.
Reason:
This message indicates that the MODS library path environment was not initialized. The MODS Database Manager failed to find a defined concatenation path. P1 is set to the name of the NCL procedure that issued the message and P2 is set to the feedback code set by the &VARTABLE GET verb.
System Action:
The database operation is unsuccessful.
User Action:
The MODS path is defined in the MODSFILES Customizer parameter group. Additional messages that relate to file allocation failures might also be present in the activity log prior to this message.
Review the data set names in your INI procedure for this group. The group is preceded by a label .MODSFILES.
Correct the data set names in the INI procedure and restart the region.
Reason:
This message indicates that the MODS library path environment was not initialized properly. A call to the MODS Database Manager failed to find specific data associated with the current path.
System Action:
The path inquiry fails
User Action:
Ensure that path initialization is properly executed.
Reason:
This indicates an internal logic failure. An attempt was made to access a subsidiary record without previously having accessed the related primary record.
System Action:
The database request is rejected.
User Action:
Contact your product support representative.
Reason:
The parameter ID=dbid passed to the Database Manager is no longer supported since files concatenation.
System Action:
The call is rejected.
User Action:
Correct the Database Manager call and retry.
Reason:
This message indicates that a message could not be retrieved from the message database because the MODS library path environment was not initialized. The MODS Database Manager failed to find a defined concatenation path. P1 is the ID of the message being retrieved.
System Action:
The database operation is unsuccessful.
User Action:
The MODS path is defined in the MODSFILES Customizer parameter group. Additional messages that relate to file allocation failures might also be present in the activity log prior to this message.
Review the data set names in your INI procedure for this group. The group is preceded by the .MODSFILES label.
Correct the data set names in the INI procedure, and restart the region.
Reason:
The user is not authorized to access the function requested.
System Action:
The Database Manager call is rejected.
User Action:
Contact your systems administrator for appropriate authorization if the function is required and retry.
Reason:
An invalid command was entered.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
Records can only be moved or copied within the same file if the language code is changed. This is to reduce the possibility of accidental corruption of the original records.
System Action:
The move/copy request is rejected.
User Action:
Specify a different input file id, output file id, or language code and retry.
Reason:
An invalid command was entered.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
The NDB system parameters were set successfully.
System Action:
None.
User Action:
None.
Reason:
The NDB system parameter indicated was unable to be set. Refer to the activity log for details.
System Action:
The system parameter is not changed.
User Action:
Determine the cause, correct and retry.
Reason:
The copy/conversion procedure is analysing the data on the file P1
System Action:
Informational Message.
User Action:
None.
Reason:
The copy/conversion procedure has determined that the P1 CAS control file is for NetMaster or SOLVE Version P2.
System Action:
None.
User Action:
None.
Reason:
The object P1 was successfully copied from the OLD CAS file to the NEW CAS file. P1 is a description of the object that was copied.
System Action:
Informational Message.
User Action:
None.
Reason:
The object P1 was not copied from the OLD MODS control file to the NEW MODS control file. P1 is a description of the object that was not copied. This could be because the object modified was a SOLVE object and not a user application object. Only objects with a non SOLVE application prefix will be copied to the new MODS control file.
System Action:
Informational Message.
User Action:
Note the object and check why the object was added/modified to the old CAS file. If you wish these changes to be made to the new file, they must be done manually.
Reason:
The subroutine P1 was not found in the procedure P2 . This subroutine is required so that a records for a particular application and category can be copied.
System Action:
Procedure Terminates.
User Action:
Note the subroutine and procedure names and contact your support representative.
Reason:
This message is the column headings for message DB0307. See the message DB0307 for further information.
System Action:
None.
User Action:
None.
Reason:
This message is the column headings for message DB0308. See the message DB0308 for further information.
System Action:
None.
User Action:
None.
Reason:
This message notifies you of data that is present on your CAS file. P1 will contain the following sections (from left to right) : * The fileid of the file. * The Language Code * CAS application Id. * Application Id.
System Action:
None.
User Action:
None.
Reason:
The copy of CAS records has completed.
System Action:
None.
User Action:
None.
Reason:
A error occurred when trying to access the database file.
System Action:
The copy utility terminates.
User Action:
Determine the cause of the error from the return code and feedback code indicated and retry.
Reason:
A error occurred when copying an object in the subroutine P1 . The subroutine had a return code of P2 . P3 is the key of the object being copied.
System Action:
The copy utility terminates.
User Action:
Determine the cause of the error from the return code indicated and retry.
Reason:
A error occurred when trying to access a vartable.
System Action:
The copy utility terminates.
User Action:
Determine the cause of the error from the return code and feedback code indicated and retry.
Reason:
The copy utility was not able to determine the version of the CAS file with a fileid of P1 .
System Action:
The copy utility terminates.
User Action:
Check that you have the correct CAS file allocated.
Reason:
A error occurred when retrieving an object. The DBMS procedure P1 ended with a return code of P2 . The key of the object is P3 .
System Action:
The copy utility terminates.
User Action:
Determine the cause of the error from the return code indicated and retry.
Reason:
The object P1 has been deleted from the installation's cas file by the CAS put file apply procedure because it was marked for deletion in the CAS put file. This is probably because the object is now obsolete.
System Action:
Informational Message.
User Action:
None.
Reason:
The CAS put file was not applied to the installation's CAS file because one or more of the objects that are being replaced on the installation's CAS file have been modified by a user. These modified objects would have been identified by the message DB0327.
System Action:
Informational Message.
User Action:
Check why the objects were modified on the CAS file. The CAS put file will not be applied unless you set the OVERRIDE option to YES in the procedure $CADB05U.
Reason:
An error occurred during Data Dictionary maintenance file processing. P1 is the file option that was being performed.
System Action:
The file processing request fails.
User Action:
Determine the cause of the error from the return and feedback codes and retry.
Reason:
An error occurred when trying to display or retrieve help. P1 is the SYSMSG returned from the Help Manager.
System Action:
The help request fails and processing continues.
User Action:
Determine the cause of the error from the return code and retry.
Reason:
An invalid command was entered.
System Action:
The command is ignored.
User Action:
Correct the command and retry.
Reason:
An error occurred on the call to the Selection List Manager. P1 is the SYSMSG returned from the Selection List Manager.
System Action:
Processing is terminated.
User Action:
Determine the cause of the error from the return code and retry.
Reason:
An error occurred while updating an element. P1 is the error message returned from the update procedure.
System Action:
The update may not have completed successfully.
User Action:
Determine the cause of the error from the retcode and retry.
Reason:
An error occurred during group/field/element add procedure. P1 is the SYSMSG returned from the update procedure.
System Action:
The add operation may not have completed successfully.
User Action:
Determine the cause of the error from the retcode and retry.
Reason:
An error occurred during group/field processing. P1 is the SYSMSG returned from the update procedure.
System Action:
Group/field processing is terminated.
User Action:
Determine the cause of the error from the return code and retry.
Reason:
An error occurred in the call to $DDNAMEC.
System Action:
The name list obtained for group and field validation may not be correct.
User Action:
Determine the cause of the error from the return code and retry.
Reason:
An error occurred while trying to display a data dictionary editor panel. P1 is the SYSMSG returned from panel services.
System Action:
The procedure is terminated.
User Action:
Determine the cause of the error from the return code and retry.
Reason:
An unknown command was entered on the command line.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
The element(s) were successfully saved in the database.
System Action:
None.
User Action:
None.
Reason:
The element add or update was cancelled at the user's request.
System Action:
None.
User Action:
None.
Reason:
The data entered on a data dictionary editor data entry panel is valid.
System Action:
None.
User Action:
Use the File or Save function key to save the data on the database.
Reason:
An error occurred while trying to build a panel for the data dictionary editor. P1 is the SYSMSG returned from panel services.
System Action:
The panel is not issued.
User Action:
Determine the cause of the error from the return code and retry.
Reason:
An error occurred in the SETFKA call to the General Purpose Procedure Library. P1 is the SYSMSG set by the General Purpose Procedure Library.
System Action:
Processing is terminated.
User Action:
None.
Reason:
The key type for an element must be 'L' for local, or 'I' for inherited.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the field value.
Reason:
The element name entered is already defined at this level in this map definition.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Change the element name or use the update option to change the existing element.
Reason:
The key entered for this element has already been used at this level in this map definition.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Change the key value.
Reason:
The included map specified on the element data entry panel is not defined in the data dictionary.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the name of the include map or erase the field value.
Reason:
The encoding rule entered in the element data entry panel of the data dictionary editor is invalid.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the encoding rule.
Reason:
If the user is entering the encoding rule in hex format, the second byte must be 00 (Eg: 12000202).
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the encoding rule.
Reason:
The second and third bytes of the encoding rule (the length length and the key length) must be equal.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the encoding rule.
Reason:
An invalid encoding rule was entered.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the encoding rule.
Reason:
The encoding rule entered is invalid.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the encoding rule.
Reason:
The encoding rule entered is invalid.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the encoding rule.
Reason:
The encoding rule entered is invalid.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the encoding rule.
Reason:
The encoding rule entered is invalid.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the encoding rule.
Reason:
There are no fields or groups defined within this element or group.
System Action:
None.
User Action:
None.
Reason:
A group or field by this name has already been defined for this element.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Enter a unique group or field name.
Reason:
The format entered for the group or field is invalid.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the field value.
Reason:
Groups and fields must be added in order of offsets - the validation procedure enforces this.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
IF you want a field with this particular offset, exit back to the selection list and add after the field/group with the largest offset smaller than this one.
Reason:
Groups and fields must be added in order of offsets, the validation procedure enforces this.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
IF you want a field with this particular offset, exit back to the selection list and add after the field/group with the largest offset smaller than this one.
Reason:
The groups/fields entered have been queued for saving on exit from the group/field update function.
System Action:
None.
User Action:
None.
Reason:
An error occurred while saving the group(s) or field(s) entered.
System Action:
The save function is terminated.
User Action:
Determine the cause of the error and retry.
Reason:
The add or update request was cancelled at the user's request.
System Action:
None.
User Action:
None.
Reason:
There are no elements defined within the enclosing element.
System Action:
None.
User Action:
None.
Reason:
There are no maps defined for the specified type. P1 is the requested type (System or User).
System Action:
None.
User Action:
Try the name/key toggle option to check if there is inconsistency in the name and key definitions.
Reason:
The message is either: SYSTEM MAP NAMES MUST BE PREFIXED WITH '$' or USER MAP NAMES CANNOT BE PREFIXED WITH '$' This convention is used to distinguish system map names from user map names.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
If a system map name is being entered, prefix it with a '$'. If a user map name is being entered, it must not have a '$' prefix.
Reason:
An update or delete of a map was requested from the Mapped Data Services Primary Menu, but no map name or key name was specified.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Enter the map name or map key and retry.
Reason:
A map name and map key cannot be specified at the same time.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Erase the value from either the Map Name field or the Map Key field.
Reason:
The requested map does not exist on the database.
System Action:
The request is rejected.
User Action:
Correct the map name and retry.
Reason:
An invalid value was entered into the map type field on the MDS Data Dictionary Editor Primary Menu.
System Action:
The request is rejected.
User Action:
Correct the field value and retry.
Reason:
The requested map was successfully deleted.
System Action:
None.
User Action:
None.
Reason:
The delete request was cancelled as requested by the user.
System Action:
The map is not deleted.
User Action:
None.
Reason:
Only 7 levels of enclosure are allowed for elements. This message is issued when the 7th level is reached, and no more elements can be added or viewed within this enclosure.
System Action:
None.
User Action:
None.
Reason:
The system map '$DDMAP' was not found on the OSCNTL file, or the SYSPARMS MAPLOAD=$DDMAP command failed.
System Action:
MDS Data Dictionary maintenance is not available.
User Action:
Contact your product support representative.
Reason:
The offset + length of this group/field make it lie fully or partially outside the boundaries of the enclosing group.
System Action:
Group/field not saved.
User Action:
Reduce either the offset or the length in this group definition, or alternately, cancel the update or add and adjust the enclosing groups boundaries.
Reason:
A field with no name is invalid, so a name must be entered when adding or updating a field. This is different for groups, which can have a blank name.
System Action:
None.
User Action:
Put a name into the name field on the field data entry panel.
Reason:
Fields with binary, packed decimal or zoned decimal formats are stored as fullwords, and thus cannot be more than 4 bytes in length.
System Action:
None.
User Action:
Change length field.
Reason:
When entering a map key on the primary menu, the key must be hexadecimal.
System Action:
None.
User Action:
Change key field.
Reason:
The record selected has been deleted, and is overlayed with the *** DELETED *** message, and thus can't be selected.
System Action:
None.
User Action:
Press the refresh function key (F6), and then make a new selection.
Reason:
The &SECCALL statement was used to check user authorization for the requested operation. This request was unsuccessful.
System Action:
The request is rejected.
User Action:
Determine the cause of the failure in the security system, and retry.
Reason:
Userid P1 is not authorized to use the MDS dictionary maintenance facility. System Support Services access is required.
System Action:
The request is rejected.
User Action:
Contact the System Administrator if the function is required.
Reason:
For the CA (Convert All) option on the old MDS primary menu, the replace option must have been filled in with Y or N (YES/NO), indicating whether conversion is to replace existing converted maps or not.
System Action:
none.
User Action:
Fill in the REPLACE field.
Reason:
The REPLACE option is used to indicate whether conversion is to replace existing asn maps, and must be Y or N.
System Action:
The request is rejected.
User Action:
Correct the field value and retry.
Reason:
This is the message returned after converting all maps. P1 is the number successfully converted. P2 is the number not converted because no replace was specified, and they existed already. P3 is the number which had errors occur during conversion. P4 is the number for which conversion was bypassed completely because the source was in error.
System Action:
none.
User Action:
Investigate which maps were in error by converting individually. Change replace option to YES if necessary.
Reason:
For conversion, the source map wasn't found.
System Action:
none.
User Action:
Check if source map exists.
Reason:
The map specified couldn't be converted because the target asn.1 map already exists, and REPLACE=NO was specified.
System Action:
none.
User Action:
Change REPLACE option to Y.
Reason:
During conversion, a file processing error occurred trying to write one of the target ASN.1 map records.
System Action:
None.
User Action:
Ensure that OSCNTL file is open for update.
Reason:
Message indicates conversion to ASN.1 was successful.
System Action:
none.
User Action:
none.
Reason:
During conversion a file processing error occurred trying get one of the source MDS map records.
System Action:
none.
User Action:
Check that the source map exists, and is defined correctly.
Reason:
Conversion of a map to ASN.1 failed because the OSCNTL file is not opened for update.
System Action:
none.
User Action:
The OSCNTL file must be opened for update during SOLVE startup. It is necessary to add the OSINP=NO JCL parm to the SOLVE startup in order to be able to define and modify maps.
Reason:
The map specified couldn't be converted because the target asn.1 map is a reserved system map and cannot be replaced. P1 = Map name.
System Action:
none.
User Action:
Create the map under a different name.
Reason:
When an attempt to automatically convert this map was made, it was detected that ASN.1 source already exists for a map of this name, implying that the map has already been defined using SOLVE V3.0 Mapping Services.
System Action:
Conversion fails.
User Action:
To override this safety mechanism, explicitly convert the map using option C on the V2.2 MDS Data Dictionary Editor, with REPLACE=Y .
Reason:
The Object Services Control file has been opened for input only and cannot be written to.
System Action:
The requested action is rejected.
User Action:
The SOLVE region must be restarted using the OSINP=NO start-up parameter before any actions can be used which write to this file.
Reason:
An error occurred while processing an VSAM file. If RC=16 then a message was written to the activity log. P1 is the file action. P2 is the file ID. P3 is the record key. P4 is the return code. P5 is the feedback code.
System Action:
None.
User Action:
Determine the cause of the error from the return code and retry.
Reason:
A file add request failed because the specified record already exists on the control file.
System Action:
The request fails.
User Action:
Delete the existing record from the control file or change the name of the record to be added.
Reason:
A file processing request failed because the specified record was not on the control file.
System Action:
The request fails.
User Action:
Correct the name or class of the record to be processed and retry.
Reason:
A file processing request was rejected either because the user with the indicated Userid was not authorized for the request (by NCLEX01) or the file was opened for input only and an update request was made against the file.
System Action:
The request is rejected.
User Action:
If the file update is required, either close and reopen the file without the INPUT parameter, or change the authority of the user in the security exit to permit the action.
Reason:
Either the entire MIB database or the requested record was already in use by another user. P1 is either DATABASE or RECORD.
System Action:
The request is rejected.
User Action:
Retry the action after a period of time.
Reason:
A mapping error occurred when retrieving a record from the MIB. P1 is the file ID. P2 is the record key. P3 is the Mapping Services return code. P4 is the map name. P5 is the Mapping Services feedback code. P6 is the map component in error (if applicable). A message was also written to the activity log.
System Action:
The request is rejected.
User Action:
Determine the cause of the error from the return and feedback codes. This type of problem can occur when the map definition in Mapping Services is missing or is not compatible with the version used to create the record.
Reason:
The Mapping Services external interface procedure received an invalid value for a keyword parameter. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $DDCALL terminates.
User Action:
Correct the keyword value and retry the request.
Reason:
Userid P1 is not authorized to use the Mapping Services maintenance facility.
System Action:
The request is rejected.
User Action:
Contact the System Administrator if the function is required.
Reason:
The ASN1COMP subsystem start request failed because invalid messages or no response has been received from commands issued.
System Action:
None.
User Action:
None.
Reason:
The ASN1COMP subsystem start request was not processed because the sub-system is already active.
System Action:
None.
User Action:
None.
Reason:
A procedure has been invoked without ALL required keywords being specified.
System Action:
Procedure ends with error message
User Action:
Re-invoke the procedure, specifying ALL required keywords.
Reason:
A procedure has been invoked with an invalid value specified for the nominated keyword.
System Action:
Procedure ends with error message
User Action:
Re-invoke the procedure, specifying correct values for all keywords.
Reason:
An error was detected while assigning a MAP to an MDO. The names of the MDO and the MAP are supplied as well as the return code and feedback.
System Action:
Procedure ends with error message
User Action:
Correct the error and re-try
Reason:
Error has occurred during compilation of ASN.1 module. The TYPEREFERENCE appearing in LINENO of ASN.1 source module is not a standard ASN.1 type and it has not been defined elsewhere in ASN.1 source module.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
Error has occurred during compilation of ASN.1 module. When real number is referenced in a standard form, ASN.1 allows a use of BASE 2 or BASE 10.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
Error has occurred during compilation of ASN.1 module. Module name has not been specified in ASN.1 source module.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
Error has occurred during compilation of ASN1 module. ASN1 module contains invalid character string in line LINENO.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
Error has occurred during compilation of ASN1 module. ASN1 module contains invalid assignment operator in line LINENO.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
Error has occurred during compilation of ASN1 module. ASN1 module contains invalid binary or hex string in line LINENO.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
Error has occurred during compilation of ASN1 module. ASN1 module contains definition of a NAME in line LINENO, that has been already defined within the current definition segment.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
Error has occurred during compilation of ASN1 module. ASN1 module contains definition of a NAME in line LINENO, that has been already defined within the current definition segment.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
Error has occurred during compilation of ASN1 module. ASN1 module contains definition of a TYPE in line LINENO, that has been already defined elsewhere in the ASN1 source module.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
Error has occurred during compilation of ASN1 module. ASN1 module contains definition that results in a long string reference, which can not be handled by NCL.
System Action:
Load records are not generated, compile process terminates.
User Action:
Split up the definition into 2 or more smaller definitions and recompile the module.
Reason:
Error has occurred during compilation of ASN1 module. ASN1 module contains definition with a Mapped Services tag TAG, that has been already used previously within current segment definition.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
Error has occurred during compilation of ASN1 module. ASN1 module contains invalid syntax in line LINENO, near symbol SYMBOL.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
An error has occurred during compilation of an ASN1 module. ASN1 source contains invalid range specification.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
An error has occurred during compilation of an ASN1 module. ASN1 source contains a SIZE constraint with range exceeding 32767 limit.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
An error has occurred during compilation of an ASN1 module. ASN1 source contains a SIZE constraint for SEQUENCE/SET definition with range not starting with 1.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
An error has occurred during compilation of an ASN1 module. ASN1 source contains a FIX constraint within a definition that is not a SEQUENCE.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
The ASN1 source defines the map under MODULENAME, however the mapname being compiled is different from the MODULENAME.
System Action:
Compilation terminates. Load records are not generated.
User Action:
Correct MODULENAME and/or MAPNAME and recompile.
Reason:
An error has occurred during compilation of an ASN1 module. ASN1 source contains an integer number that is larger than 2,147,483,647 or smaller than -2,147,483,648.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
An external format has been specified for REAL type definition. However the specification is not valid.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
An external format has been specified for INTEGER type definition. However the specification is not valid.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
An external format has been incorrectly specified. The valid range for external format specification is 0 - 255.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
Range constraint has been specified for a type that can not have range constraint.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
Size constraint has been specified for a type that can not have size constraint.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
Alphabet limitation has been specified for a type that can not have limited alphabet.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
An attempt to specify integer value in hex format has been made. However specification is not correct or integer value is too large.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
An attempt to specify character value in mixed case format within character set constraint has been made. This specification is not allowed.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
An attempt to specify null string in quotes has been made. This is invalid specification.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
ASN.1 source contains EXPORT statement for the imported type.
System Action:
Load records are not generated, compile process terminates.
User Action:
Correct the error and recompile the module.
Reason:
ASN.1 source module does not end with END statement.
System Action:
Load records are not generated, compile process terminates.
User Action:
Make sure there is an END statement at the end of ASN.1 source and recompile the module.
Reason:
This is a warning message. A component is defined in an ASN1 type and it is not named. If definition is a CHOICE then all components within the definition must be named, otherwise an error will occur during the loading of the map.
System Action:
Compilation continues.
User Action:
Correct ASN1 module if required and recompile.
Reason:
This is a warning message. References with a hyphen appear in ASN1 source module. In order not to cause problems in NCL procedure, the hyphen is converted to underscore on compiler output.
System Action:
Compilation continues.
User Action:
Correct ASN1 module if required and recompile.
Reason:
This is a warning message. ASN1 source contains the statement STATEMENT, which is not supported by object services.
System Action:
Compilation continues, the compiler produces no output for the statement
User Action:
None.
Reason:
This is a warning message. ASN1 source contains two references, REF1 and REF2, which are spelled syntactically the same way, however some letters in REF1 are in a different case (upper or lower) from the same letters in REF2.
System Action:
Compilation continues, REF1 and REF2 are treated as two different entities.
User Action:
None.
Reason:
This is a warning message. References with an underscore appears in ASN1 source module. Underscore is not supported by standard ASN.1, therefore ASN.1 source is not portable.
System Action:
Compilation continues.
User Action:
Correct ASN1 module if required and recompile.
Reason:
The maintenance procedure $DDMD04P for Mapping Services failed because it received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
Procedure $DDMD04P terminates.
User Action:
Contact the system administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
The Mapping Services maintenance panel was displayed requesting the user to confirm the deletion of the Map Definition presented.
System Action:
None.
User Action:
Press the ENTER key to allow the deletion, or press the CANCEL key to cancel the delete request.
Reason:
An invalid command was entered in the Command field.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
The Map Definition P1 was successfully deleted.
System Action:
None.
User Action:
None.
Reason:
The Map Definition P1 was successfully added.
System Action:
None.
User Action:
None.
Reason:
The Map Definition P1 was successfully updated.
System Action:
None.
User Action:
None.
Reason:
A request to delete a Map Definition was cancelled.
System Action:
None.
User Action:
None.
Reason:
A request to add a Map Definition was cancelled.
System Action:
None.
User Action:
None.
Reason:
A request to update a Map Definition was cancelled.
System Action:
None.
User Action:
None.
Reason:
A request to modify, browse or retrieve a Map Definition failed because the definition was not found in the database. The Map Definition name requested was P1 .
System Action:
The request is rejected.
User Action:
Specify a Map Definition that was previously added to the database.
Reason:
A request to update a Map failed because the Map Appl ID correlator specified did not match the Appl ID already defined in the Map or there is no Appl ID correlator in the specified map definition. The Map specified was P1 .
System Action:
The request is rejected.
User Action:
Use the facilities provided by the application identified in the Map Definition or use Mapping Services fullscreen facilities if the map does not belong to an application.
Reason:
Userid P1 is not authorized to use the Mapping Services maintenance facility.
System Action:
The request is rejected.
User Action:
Contact the System Administrator if the function is required.
Reason:
A request to update a Map failed because the Map was generated by an application. Maps that are generated by applications are not permitted to be updated outside the context of the application. The Appl ID of the application that owns the map is P1 .
System Action:
The request is rejected.
User Action:
Use the facilities provided by the application identified in the application register with Appl ID P1 to modify the map.
Reason:
The map P1 was successfully printed. The PSM print request is P2 .
System Action:
None.
User Action:
None.
Reason:
The maintenance procedure $DDMD04P for Mapping Services failed because it received an invalid variable value. The variable was P1 and the invalid value was P2 .
System Action:
Procedure $DDMD04P terminates.
User Action:
Contact the system administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
The load module for the map P1 was not found in the Mapping Services database. This may be because the map has not yet been compiled successfully.
System Action:
None.
User Action:
Compile the map.
Reason:
An error was detected while assigning a MAP to an MDO. The name of the the MAP is P1 and the MDO return code is P2 and the MDO feedback code is P3 .
System Action:
None.
User Action:
Correct the error and re-try.
Reason:
The list service procedure $DDMD05L for Mapping Services failed because it received an invalid value for a shared variable. The variable name was P1 and it value was P2 .
System Action:
Procedure $DDMD05L terminates.
User Action:
Contact the system administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
This message replaces the line of a selection list to indicate that the Map Definition that the line represented was deleted since the list had been built.
System Action:
None.
User Action:
None.
Reason:
Userid P1 is not authorized to use the Mapping Services maintenance facility.
System Action:
The request is rejected.
User Action:
Contact the System Administrator if the function is required.
Reason:
The maintenance procedure $DDCM06Z for Mapping Services failed because it received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
Procedure $DDCM06Z terminates.
User Action:
Contact the system administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
An invalid return code was received from the ASN.1 compiler. The function requested was P1 and the return code was P2 . The following table indicates the possible return codes for each function and the table after that explains the return codes.
Function Possible Return Codes
OPEN 12,16,24,28
CLOSE 12,20,24
INPUT 12,16,24
EXEC 8,12,20,24
READ 4,12,20,24,32
other 12,24
Return Code Explanation
4 No more data to read from the compile.
8 The ASN.1 compiler detected compilation errors in the source.
12 ASN.1 Compiler subsystem not initialized. Mapping services will automatically start the ASN.1 compiler as a SOLVE subsystem.
16 GETMAIN error. The compiler was unable to obtain enough storage to satisify the request.
20 A request other than OPEN was issued, however no previous OPEN had been issued.
24 Invalid or missing operands were passed to the compiler.
28 A duplicate request to OPEN was issued.
32 An insufficient number of parameters were specified for a READ request.
System Action:
Compile of ASN.1 source is terminated.
User Action:
Determine the cause of the error from the return code. Contact the system administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
The maintenance procedure $DDCM06Z for Mapping Services failed because it received an invalid variable value. The variable was P1 and the invalid value was P2 .
System Action:
Procedure $DDCM06Z terminates.
User Action:
Contact the system administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
The ASN.1 compiler was invoked to compile the source for map P1 and it detected errors.
System Action:
The request is terminated.
User Action:
Correct the errors in the source as indicated in the accompanying messages and retry the request.
Reason:
The ASN.1 compiler was invoked to compile the source for a map. The compile was successful, however no load module records were returned.
System Action:
Procedure $DDCM06Z terminates.
User Action:
Contact the system administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
The ASN.1 compiler was invoked to compile the source for map P1 and it issued warning messages. The compile was still successfully completed and the load module saved.
System Action:
None.
User Action:
Check the warnings as indicated in the accompanying messages to ensure that the desired results have been produced.
Reason:
The ASN.1 compiler was invoked to compile the source for map P1 and it completed successfully.
System Action:
None.
User Action:
None.
Reason:
A request to retrieve or delete map load module records for the Map P1 failed because the load module records were not found in the database.
System Action:
The request is rejected.
User Action:
Specify a Map that was previously compiled.
Reason:
An assign of the load module object failed with an MDO error. The return code was P1 and the feed back code was P2 . The value being assigned was P3 and it was being assigned to component P4 .
System Action:
The compile is aborted.
User Action:
Contact the system administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
Userid P1 is not authorized to use the Mapping Services maintenance facility.
System Action:
The request is rejected.
User Action:
Contact the System Administrator if the function is required.
Reason:
The maintenance procedure $DDSM07D for Mapping Services failed because it received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
Procedure $DDSM07D terminates.
User Action:
Contact ypur Systems Administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
Userid P1 is not authorized to use the Mapping Services maintenance facility.
System Action:
The request is rejected.
User Action:
Contact your Systems Administrator if this function is required.
Reason:
A request to retrieve a source records for the Map P1 failed because the source records were not found in the database.
System Action:
The request is rejected.
User Action:
Specify a Map that was previously compiled or had its source records added to the database.
Reason:
A request to retrieve a Map Definition failed because the definition was not found in the database. The Map Definition name requested was P1 .
System Action:
The request is rejected.
User Action:
Specify a Map Definition that has previously been added to the database.
Reason:
A request to retrieve the source for a Map failed because the DDNAME contained in the Map Definition (or overwritten by the request) was not found or was an invalid DDNAME. The DDNAME used was P1 and the Map was P2 .
System Action:
The request is rejected.
User Action:
Check the Map Definition for the correct DDNAME or verify that the DDNAME has been allocated and retry the request.
Reason:
A request to retrieve the source for a Map failed because the PDS member contained in the Map Definition (or overwritten by the request) was not found or was an invalid name. The member name used was P1 and the Map was P2 .
System Action:
The request is rejected.
User Action:
Check the Map Definition for the correct member name or verify that the member exists in the library allocated to the DDNAME.
Reason:
A request to retrieve the source for a Map failed because the PDS member contained in the Map Definition (or overwritten by the request) was an empty member. The member name used was P1 and the Map was P2 .
System Action:
The request is rejected.
User Action:
Check the Map Definition for the correct member name or verify that the DDNAME used has the correct libraries allocated. Make sure the ASN.1 source is added to the specified member.
Reason:
A request to retrieve the source for a Map failed because the PDS member contained too many source lines. The member name used was P1 and the Map was P2 .
System Action:
The request is rejected.
User Action:
Redefine your ASN.1 source into smaller units that include other source members.
Reason:
The changes made to the Map P1 were saved.
System Action:
None.
User Action:
None.
Reason:
The changes made while in the Map source editor for Map P1 were cancelled as requested.
System Action:
The changes since the last SAVE are cancelled.
User Action:
None.
Reason:
A request to retrieve the source for a map failed because the number of source lines in the PDS member exceeded the internal queue limit of 32767.
System Action:
The request fails.
User Action:
Redefine your ASN.1 source into smaller units that include other source members.
Reason:
The text editor service procedure $DDSM08X for Mapping Services source editor failed because it received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
Procedure $DDSM08X terminates.
User Action:
Contact the system administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
The changes made to the Map P1 were saved.
System Action:
None.
User Action:
None.
Reason:
The Map P1 was successfully copied into the edit session.
System Action:
None.
User Action:
None.
Reason:
The list service procedure $DDCM09L for Mapping Services failed because it received an invalid value for a shared variable. The variable name was P1 and it value was P2 .
System Action:
Procedure $DDCM09L terminates.
User Action:
Contact the system administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
Userid P1 is not authorized to use the Mapping Services maintenance facility.
System Action:
The request is rejected.
User Action:
Contact the System Administrator if the function is required.
Reason:
A request to locate message line P1 failed because P1 is not numeric.
System Action:
The request is rejected.
User Action:
Specify a numeric message line number.
Reason:
The map P1 was compiled and the compiler issued the messages accompanying this one.
System Action:
None.
User Action:
See the accompanying messages.
Reason:
The field validation exit $DDMD10X for Mapping Services failed because it received an invalid field name for the exit type. The field name was P1 and the exit type was P2 .
System Action:
Procedure $DDMD10X terminates.
User Action:
Contact the system administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
The map name P1 cannot be specified because a map with that name already exists.
System Action:
The panel is redisplayed and the field is set in error.
User Action:
Specify a unique map name and retry.
Reason:
The maintenance procedure $DDMD11M for Mapping Services failed because it received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
Procedure $DDMD11M terminates.
User Action:
Contact the system administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
Userid P1 is not authorized to use the Mapping Services maintenance facility.
System Action:
The request is rejected.
User Action:
Contact the System Administrator if the function is required.
Reason:
The transaction processor to retrieve a map failed because the program that invoked it violated the transactions protocol. The transaction program expected to receive P2 but in fact received P1 .
System Action:
The procedure terminates.
User Action:
Ensure that the caller adheres to the protocol and then retry the transaction.
Reason:
The transaction processor to retrieve map details failed as the program that invoked it passed an invalid request. The request passed a command of " P1" which is not supported.
System Action:
The procedure terminates.
User Action:
Ensure that the caller sends a valid map name to be retrieved and retry the transaction.
Reason:
The transaction processor to retrieve a map failed because the APPC send of a map component failed with return code P1 and feedback code P2 .
System Action:
The procedure terminates.
User Action:
Check the return code and feedback code for the appropriate action.
Reason:
The transaction processor to retrieve a map failed because the map was not found in the Mapping Services database. The name of the map not found was P1 .
System Action:
The request is rejected.
User Action:
Specify a Map that was previously added to the database and retry the request.
Reason:
The MDO keyword must specify the name of an MDO to be dumped.
System Action:
None.
User Action:
Correct call to $DEMDODP.
Reason:
The OFFSETF (offset format) keyword must specify 'DEC' (decimal) or 'HEX' (hexadecimal). The default is 'DEC'.
System Action:
None.
User Action:
Correct call to $DEMDODP.
Reason:
The MDO P1 has been dumped by userid P2 with an NCLID of P3 . The mdo has the map P4 attached to it.
System Action:
None.
User Action:
None.
Reason:
This is a description of the dump.
System Action:
None.
User Action:
None.
Reason:
Dump with a decimal offset
System Action:
None.
User Action:
None.
Reason:
Dump with a hexadecimal offset
System Action:
None.
User Action:
None.
Reason:
End of Dump
System Action:
None.
User Action:
None.
Reason:
Alert threshold values for high and low value alerts for attributes of type gauge, counter, and total can only be an unsigned integer.
System Action:
The alert definition is not updated.
User Action:
Correct the value field.
Reason:
When defining multiple alert values, the threshold values for High Value, Above Baseline, and Below Baseline alerts must be defined in ascending order, and those for Low Value alerts must be defined in descending order.
System Action:
The alert definition is not updated.
User Action:
Correct the value field.
Reason:
An alert severity has been provided for an alert definition, but no alert threshold value has been specified.
System Action:
The alert definition is not updated.
User Action:
Specify an alert threshold value in the Value field.
Reason:
Alert severity values can only be an integer between 1 and 4 inclusive.
System Action:
The alert definition is not updated.
User Action:
Correct the severity field.
Reason:
An alert value has been provided for an alert definition, but no severity has been specified.
System Action:
The alert definition is not updated.
User Action:
Specify a severity value in the Severity field.
Reason:
When specified, the clear alert value must be less than or equal to the lowest alert value specified for a High Value, Above Baseline alert, and Below Baseline alert or greater than or equal to the highest alert value specified for a Low Value.
System Action:
The alert definition is not updated.
User Action:
Correct the Clear Alert Value field.
Reason:
When defining a Value alert, you have the option to define a clear alert condition that is either equal to or not equal to a specific value. However, you cannot define both conditions.
System Action:
The alert definition is not updated.
User Action:
Correct the Clear Alert Value field.
Reason:
F11 was pressed to view the full alert text, but the cursor was not positioned over a text field.
System Action:
No text was selected so no text is displayed.
User Action:
Place the cursor on the text field you want to view and press F11.
Reason:
An attempt to save the alert details failed because an alert action was was defined but there was no associated threshold.
System Action:
The request to save the alert details is rejected.
User Action:
Specify an alert threshold or delete the action.
Reason:
An attempt to save the alert details failed because alert text was specified but there was no associated threshold.
System Action:
The request to save the alert details is rejected.
User Action:
Specify an alert threshold, or delete the alert text.
Reason:
An attempt to save the alert details failed because a clear alert value was specified but there was no associated threshold.
System Action:
The request to save the alert details is rejected.
User Action:
Specify an alert threshold or delete the clear alert value.
Reason:
Clear Alert value can only be an unsigned integer.
System Action:
The alert definition is not updated.
User Action:
Correct the value field.
Reason:
The valid range for a Below Baseline Alert threshold is 0-100 .
System Action:
The alert definition is not updated.
User Action:
Correct the value field.
Reason:
The threshold value overlaps with a range of values previously set for P2 . When defining alert thresholds, the High Value range of values should always be greater than the Low Value range of values.
System Action:
The alert definition is not updated.
User Action:
Correct the value field.
Reason:
An invalid request was made to view a non-existent Alert Description.
System Action:
Request is rejected.
User Action:
None.
Reason:
Low Alert value can only be an unsigned non-zero integer.
System Action:
The alert definition is not updated.
User Action:
Correct the value field.
Reason:
An alert action has been set for an alert definition, but no severity has been specified.
System Action:
The alert definition is not updated.
User Action:
Specify a severity value in the Severity field.
Reason:
An attempt to save the alert details failed because alert text was specified but there was no associated severity.
System Action:
The request to save the alert details is rejected.
User Action:
Specify an alert severity.
Reason:
The value specified to create an alert must not be the same as the value specified to clear the alert.
System Action:
The alert definition is not updated.
User Action:
Correct either the Alert Value field or the Clear Alert Value field.
Reason:
The value specified to create an alert for an enumerated attribute must not be the same as another value.
System Action:
The alert definition is not updated.
User Action:
Correct or remove one of the duplicate alert values.
Reason:
The value for the "Clear Alert When Value is NOT" field must be the same value as that specified to create the alert. It does not make sense to say: 1.Create alert when value is X 2.Clear the alert when the value is NOT Y The two statements contradict each other. Thus the only sensible value that the field can have is the same value as that specified to create the alert.
System Action:
The alert definition is not updated.
User Action:
You can either blank out the 'Clear Alert When Value is NOT' field or change it to the same value as the alert value field.
Reason:
The value for the "Clear Alert When Value is NOT" field cannot be specified if there are multiple alert values specified. It does not make sense to say: 1. Create alert when value is X 2. Create alert when value is Y 3. Clear the alert when the value is NOT X Statement 3 contradicts statement 2. Thus you cannot have a value in the 'Clear Alert When Value is NOT' field when there is more than one alert value.
System Action:
The alert definition is not updated.
User Action:
You can either blank out the 'Clear Alert When Value is NOT' field, or you can clear all the alert values except one.
Reason:
An ACTIONONLY alert type (Severity 0) has been specified, and there are no defined actions.
System Action:
The alert definition is not saved.
User Action:
Modify the definition to have actions, or set an alert severity of 1 to 4.
Reason:
The Data Sampling framework attempted to call back an application, but an error was encountered loading the call-back package. The procedure being loaded was P1 which was in the package P2 . The OML error code was P3 . This message is written to the log.
System Action:
The associated application function is not performed.
User Action:
To determine why the application package is not loading, refer to the messages in the log. Notify the systems administrator.
Reason:
The call to the procedure failed because the keyword identified by P1 had an invalid value identified by P2 .
System Action:
The request is rejected.
User Action:
Contact your system administrator.
Reason:
The field highlighted in the error is not a valid monitor group name.
System Action:
The request is rejected.
User Action:
Correct the name to remove embedded blanks.
Reason:
A monitor group description has not been entered.
System Action:
The group is not updated nor added.
User Action:
Specify a group description.
Reason:
The Collection Status field is not set to a valid value.
System Action:
The group is not updated nor added.
User Action:
Correct the Collection Status field.
Reason:
The 'Send to ReportCenter' field must be set to a valid value. If ReportCenter is not enabled in this region, the only valid value is 'No'.
System Action:
Definition cannot be saved.
User Action:
Correct the 'Send to ReportCenter' field. Valid values are:
No - Do not send any data to ReportCenter. This is the default value. If ReportCenter is not enabled in this NetMaster region, leave this value set to 'No'.
Yes - Send data to ReportCenter.
A value of 'Yes' specifies that you want hourly summaries of all monitored IP Node attributes for this group to be sent to ReportCenter.
Hourly data summaries will be queued to this region's Data Warehouse Service for delivery to ReportCenter, which adds the data into its SQL database.
You can then use ReportCenter to generate a variety of web-based graphical reports from this data.
Web reports may be run on demand, or scheduled for regular generation.
Reason:
The monitor group definition P1 has been saved to the IPFILE.
System Action:
The monitoring activities for the associated nodes are updated.
User Action:
None.
Reason:
The CANCEL command was used to terminate the action.
System Action:
None.
User Action:
None.
Reason:
The monitor group definition P1 is already defined.
System Action:
The ADD operation is prevented.
User Action:
Change the monitor group name to be a unique value.
Reason:
The monitor group is new or does not contain any activities.
System Action:
None.
User Action:
Use F4=Add to add monitoring activities to the group definition.
Reason:
An attempt was made to set the Send to ReportCenter field to YES, but the ReportCenter feature is not enabled in this region.
System Action:
The group is neither updated nor added.
User Action:
When the ReportCenter feature is not enabled on a region, the only valid value for this field is NO.
ReportCenter is an optional and non-chargeable feature of many CA NetMaster products, including CA NetMaster NM for TCP/IP and CA NetMaster FTM.
ReportCenter stores performance data collected by various monitors in a z/OS SQL database. You can then use its web interface to generate web-based graphical reports from this data.
These web reports can be run on demand or scheduled for regular generation. A variety of historical and trend reports are provided. Report output consists of HTML and graphic files stored as standard HFS files.
ReportCenter can be enabled on any region that is licensed for one of its supporting products.
Enabling ReportCenter involves these steps:
This z/OS Java application runs in the z/OS UNIX System Services environment and provides services including SQL database access and report generation.
Note: For more information, see the Installation Guide and also the ReportCenter Guide.
Even without ReportCenter enabled, you can see an example of a report at the following URL:
http://?your-host-and-port/public/reports/example1/report.html
?your-host-and-port specifies the IP name/address and port of the WebCenter web server on this region (for example, 192.168.66.44:8744).
The WebCenter URL appears on the Primary Menu. You can also use OCS command SELFTEST to display it.
Reason:
You tried to file the Monitor Group identified by P1 which has not been changed. The requested action is not performed.
System Action:
The definition is not saved again.
User Action:
None.
Reason:
A monitor group name has not been entered.
System Action:
The group is not added.
User Action:
Specify a group name.
Reason:
The value specified must numeric and fall in the range specified.
System Action:
The value is rejected.
User Action:
Specify a value within the range.
Reason:
A new qualified alert is saved in the database.
System Action:
The monitoring activities for the associated nodes are updated.
User Action:
None.
Reason:
A request to update the alert details for a selected attribute has failed because the attribute is not in the current monitoring definition for this resource. This can occur when an attribute was removed manually from the monitoring definition and the history report reflects the sampled data prior to removal. This condition can also occur for resource classes that have special internal attributes that are always present regardless of the monitor definition.
System Action:
The request is rejected.
User Action:
To restore an attribute that has been removed, exit the Performance Display panel, issue the UM line command for the resource, and add the desired attribute. You cannot specify alerts for special internal attributes.
Reason:
An attempt was made to set the 'Send to ReportCenter' field to 'Yes', but the ReportCenter Data Feed parameter group was not configured correctly on this NetMaster region.
System Action:
The group is not updated nor added.
User Action:
Review parameter group '$WR REPORTDATA' via the 'Customizer : Parameter Groups' panel (/PARMS) and ensure that all required fields are specified correctly.
Reason:
No selection was made from the attribute selection list.
System Action:
None.
User Action:
None.
Reason:
The call to the procedure failed because the keyword identified by P1 has an invalid value identified by P2 .
System Action:
The request is rejected.
User Action:
Contact your system administrator.
Reason:
A request to add attributes has failed because all available attributes have already been selected for monitoring.
System Action:
None.
User Action:
None.
Reason:
An invalid value for Baseline Type has been specified. It must be either Daily, DayOfWeek, or HourOfDay.
System Action:
The attribute definition is not updated.
User Action:
Specify a valid Baseline Type.
Reason:
Alerting details have been defined for Baseline alerting, but no baseline has been specified.
System Action:
The attribute definition is not updated.
User Action:
You must specify a valid Baseline Type if you want to alert against baselines.
Reason:
An invalid value for the monitoring rate has been specified. The rate value specifies the monitoring interval in minutes and it must be at least 5 and not greater than 60 minutes.
System Action:
The attribute definition is not updated.
User Action:
Specify a valid Rate value.
Reason:
The CANCEL command was used to terminate the action.
System Action:
None.
User Action:
None.
Reason:
The application ID P1 is not defined to the Data Sampling framework.
System Action:
The Data Sampling action is terminated.
User Action:
Report the error to Technical Support.
Reason:
A request to update a list of Alert Automated Actions has failed because the selected alert does not specify any threshold(s).
System Action:
The request is rejected.
User Action:
Update the selected alert and specify an alert threshold before defining an action.
Reason:
A request to Clear Actions has failed because the selected alert has no associated actions.
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to Reset Alert has failed because the selected alert has no threshold(s) defined.
System Action:
The request is rejected.
User Action:
None.
Reason:
A Baseline Type has been specified, but no Baseline Alert Type threshold ( Above/Below Baseline ) has been defined.
System Action:
The attribute definition is not updated.
User Action:
You must specify a Baseline Alert Type threshold or if not required, clear the Baseline Type field.
Reason:
A request to display a list of Alert Automation Actions has failed because none have been defined.
System Action:
The request is rejected.
User Action:
None.
Reason:
A request was made to view a list of known qualifiers for a qualified attribute, but nothing was found.
System Action:
None.
User Action:
Try again after monitoring has been in progress for this class-resource-attribute-qualifier combination for at least one hour.
Reason:
A qualifier has been specified for an attribute and the corresponding rate field has been cleared. Qualified attributes are only used to contain information that is necessary to generate alerts based on a qualifier. They do not require the rate field.
System Action:
The rate field is cleared. When issued from the Alert Control Details panel, the rate field also becomes unavailable for update.
User Action:
None.
Reason:
A selected or supplied qualifier is already in use as an alert criteria for this resource.
System Action:
Qualifier is highlighted in error.
User Action:
Supply another qualifier or consider using the qualifier that is already defined as an alert criteria.
Reason:
A request to define a new alert qualifier has exceeded the maximum internal buffer size of 64 KB.
System Action:
Request is rejected and the qualifier is highlighted in error.
User Action:
Consider removing or reusing alert qualifiers that are already defined for this resource.
Reason:
A request was made to view the baseline data for a specific class- resource-attribute- qualifier combination, but no baseline data exists in storage.
- The resource many not have been monitored for long enough for any baseline data to be collected
- The baseline data may not yet have been loaded from disk to storage
System Action:
The baseline values display is not presented.
User Action:
Try again after monitoring has been in progress for this class-resource-attribute-qualifier combination for at least one hour.
Reason:
A request was made to view the baseline data for a qualified attribute without specifying a qualifier. In this case, a list of all known qualified attributes is returned.
System Action:
The baseline display shows a list of qualified baseline data.
User Action:
Select the qualifier that you want to view.
Reason:
The Data Sampling framework attempted to call back an application, but an error was encountered loading the call-back package. The procedure being loaded was P1 which was in the package P2 . The OML error code was P3 . This message is written to the log.
System Action:
The associated application function is not performed.
User Action:
To determine why the application package is not loading, refer to the messages in the log. Notify the systems administrator.
Reason:
The CANCEL command was used to terminate an update. P1 was the function name.
System Action:
None.
User Action:
None.
Reason:
The Data Sampling action indicated by P1 failed due to one of the following:
APPLICATION ID 'applid' INVALID - The application is not recognized.
EVERY COMMAND NOT ACCEPTED - Refer to the activity log.
System Action:
None
User Action:
Notify your systems administrator.
Reason:
A call to the Data Sampling framework omitted an operand or incorrectly specified a value for the keyword P1 .
System Action:
None.
User Action:
Correct the keyword value and retry the operation.
Reason:
The specified Data Collection activity has been stopped for the resource
P3 .
System Action:
The scheduled activity is stopped.
User Action:
None.
Reason:
All data collection activities have been stopped for type P1 resource P2
System Action:
All scheduled activities for the resource are stopped.
User Action:
None.
Reason:
A call to the Data Sampling framework to stop an activity for the resource P2 failed because the activity is not scheduled.
System Action:
None.
User Action:
None.
Reason:
A call to the Data Sampling framework to stop an activity failed because the PURGE TIMER command returned an unexpected response.
System Action:
None.
User Action:
Notify your system administrator.
Reason:
The request of type P1 to $DFCALL failed because the attribute P2 had an invalid value of P3 .
System Action:
None.
User Action:
Contact the system administrator.
Reason:
An error occurred while manipulating an NCL VARTABLE in the procedure $DFCALL. P1 is the vartable identifier, P2 is the function being performed and P3 is the feedback code set by the vartable verb.
System Action:
None.
User Action:
Notify your systems administrator.
Reason:
Data Collection activities have been started for a resource. P1 is a description of the data collection application P2 is the name of the resource
System Action:
None.
User Action:
None.
Reason:
Scheduled data collection for the resource P1 failed because the $DFREGISTRY vartable does not contain the activity schedule.
System Action:
None.
User Action:
Notify your systems administrator.
Reason:
A request to present the statistics for the attribute P1 failed because the attribute was not present in the history sample.
System Action:
Processing terminates.
User Action:
Check that sampling is activate for the resource. It may be that statistics have not yet been gathered because the sampling interval has not expired.
Reason:
The Data Sampling framework attempted to clear an alert. However an error occurred, as described in the previous message.
System Action:
None.
User Action:
Refer to the help for the previous AMCALLxx message.
Reason:
A call to the Sample Collect procedure of $DFCALL did not pass any arguments or $DFCNTRL object.
System Action:
None.
User Action:
Report the error to your system administrator.
Reason:
A request to display the sampling history for a resource has failed because no history exists.
System Action:
None
User Action:
If necessary update the resource and set monitoring to active.
Reason:
An internal error occurred. The map P1 experienced the error described by MDORC= P2 and MDOFDBK= P3 .
System Action:
The request is rejected.
User Action:
Contact your local systems administrator.
Reason:
Summary processing for a gauge attribute has detected a non-numeric value.
System Action:
The value is ignored.
User Action:
Report the error to your product support representative.
Reason:
The current cycle for data collection of resource P1 will use an updated attribute information.
System Action:
None.
User Action:
Scan previous RMDFAP03 log entries to determine the attribute ID.
Reason:
The current cycle for data collection of resource P1 will be restarted to implement recent changes to the sampling definition.
System Action:
None.
User Action:
None.
Reason:
A data sampling summary has been collated for a resource with ID P2 and class P1. The summary contains P3 entries from the P4 attributes in the sampling history. This message is a diagnostic used for determining data sampling activity.
System Action:
A sample summary event is generated if recording level for the resource is not NONE.
User Action:
Refer to your product support representative.
Reason:
A data sampling sample has been collected for a resource with ID P2 and class P1. The sample contains P3 entries from the P4 attributes in the sampling history. This message is a diagnostic used for determining data sampling activity.
System Action:
A sample detail event is generated if recording level for the resource is DETAIL.
User Action:
Refer to your product support representative.
Reason:
The request of type P1 to $DFCALL failed because the attribute ID is either null or has a length greater than 20 bytes.
System Action:
Processing continues.
User Action:
Contact the system administrator.
Reason:
The attribute P1 failed registration because an identical attribute is already registered with an application different from P2 .
System Action:
Registration is ignored and an error message is written to the log.
User Action:
Notify your systems administrator.
Reason:
The Data Sampling action indicated by P1 failed because no attributes were selected in the monitoring definition for resource P2 .
System Action:
No sample is taken.
User Action:
Review the definition of the affected resource and, if required, select at least 1 attribute from the Monitoring Definition panel. If monitoring is not desired, set the 'Monitoring Activity' field to INACTIVE in the 'General Description' panel.
Reason:
The condition monitor is still being initialized.
System Action:
No conditions are displayed.
User Action:
None.
The monitor will refresh when initialization has completed.
Reason:
The conditions for P1 were not available at the time the display was being generated.
System Action:
No conditions are displayed.
User Action:
Try again later.
Reason:
The sample details are not available for the selected condition. This may be because the resource is not active and sampling cannot be done, or monitoring has not yet started for the condition.
System Action:
None.
User Action:
Try again later. If the resource is inactive, then ensure that it is started before trying again.
Reason:
The parameter passed to the VIEW command is invalid. The passed parameter is P1.
System Action:
Command rejected.
User Action:
Enter a valid parameter for the VIEWCOND command. The syntax for the command is:
VIEWCOND [ ALL | NOTOK ]
If no parameters are specfied then the view is toggled between ALL and NOTOK. You can abbreviate the view keywords to the smallest number of characters to make them unique.
The ALL view (default) will show all the conditions sorted in logical order of importance.
The NOTOK view shows conditions sorted by status. Problem conditions first then warning conditions and lastly OK conditions, which are grouped and collapsed under a heading at the bottom of the list.
Examples:
1. Toggle the view: VIEWCOND
2. View by NOTOK status: VIEWCOND NOTOK
3. View all conditions: VIEWCOND ALL
Reason:
A request to change the view of the condition summary completed successfully. The new view settings are P1.
System Action:
None.
User Action:
None.
Reason:
The conditions for region P1 were not accessible at the time the display was being generated. This may be because the region is not currently executing or there is a communications link problem between P1 and this region.
System Action:
No conditions are displayed.
User Action:
Try again later.
Reason:
The initialization of the condition monitor failed because the definitions of conditions were recursive.
System Action:
Initialization of the condition monitor is terminated.
User Action:
Contact Technical Support.
Reason:
The condition is not being monitored because of one of the following reasons:
The resource's monitoring definition does not include the performance data attribute that this condition is based on.
For example, an address space or stack is not running.
The Monitoring Activity parameter of the resource is set to INACTIVE or OFF. This may be set in the resource definition or set dynamically by a monitoring map.
Many condition attributes come from SNMP. SNMP may be inactive or incorrectly configured for the z/OS stack.
System Action:
The condition is shown as not monitored.
User Action:
To get the name of the attribute that needs to be monitored, enter I or H next to the condition.
To add this attribute to the monitoring definition for this resource, enter E next to the condition.
After this attribute has been monitored for a while and you have an idea of its likely values, you can use the UA action to set alert criteria and warning/problem limits for the condition.
For more information about condition actions and limits, use the IP Condition Summary online help.
Start the address space or stack. Consider placing this under the control of operations automation.
To make the condition available, do one of the following:
Check that the z/OS TCP/IP SNMP agent is active on this system.
Ensure that the SNMP agent has been set up correctly.
For more information, see topics related to SNMP agent in the CA NetMaster Network Management for TCP/IP Installation Guide.
Reason:
The condition's value is currently not available. The sample returned from the sampling infrastructure is null and cannot be plotted on a graph.
System Action:
The condition is shown as not available.
User Action:
None.
Reason:
The condition's value is currently not available due to a sampling error in the sampling infrastructure.
System Action:
The condition is shown as sampling error.
User Action:
Enter H next to the condition to get help on the specific error encountered with the sampling infrastructure.
Reason:
The condition's value is currently not available because there are too few samples. There needs to be at least two samples for certain types of attributes.
System Action:
The condition is shown as pending.
User Action:
None.
A subsequent sample will be taken in due course, and the determined rate of change will be plotted.
Reason:
The condition monitor failed to find a mandatory record in the database. The missing condition is P1.
System Action:
Processing is terminated.
User Action:
Contact Technical Support.
Reason:
No stacks are being monitored for this system because of the following possible reasons:
System Action:
No stack related conditions are shown.
User Action:
If no stacks are defined, define them.
If stacks are defined, turn on monitoring for them.
Reason:
No stack interfaces are being monitored for this system because of the following possible reasons:
System Action:
No stack interface related conditions are shown.
User Action:
If no stacks are defined, define them.
If stacks are defined, turn on monitoring for the stack interfaces.
Reason:
No ports are being monitored for this system because of the following possible reasons:
System Action:
No port related conditions are shown.
User Action:
If no stacks or address spaces are defined, define them.
If stacks and address spaces are defined, turn on monitoring for them.
Reason:
No ports are being monitored for this system by address space because of the following possible reasons:
System Action:
No port related conditions are shown.
User Action:
If no stacks or address spaces are defined, define them.
If stacks and address spaces are defined, turn on monitoring for them.
Reason:
The resource of type P1 is not being monitored for this system for one of the following possible reasons:
System Action:
None of the conditions for this resource are shown.
User Action:
If the P1 resource has not been defined, define it.
If defined, turn on monitoring by entering U beside the condition and selecting the first panel from the Panel Display List. Ensure that the Monitoring Activity field is set to ACTIVE and press F3.
Reason:
The user P1 deleted the baseline sampling statistics for class P2 and resource P3 . If P4 is present, it indicates that only the statistics for attribute ID P4 were deleted; if P5 is present, only the statistics for qualifier P5 of attribute P4 were deleted.
System Action:
None.
User Action:
None.
Reason:
A request to display a list of attributes with baselines for a resource cannot be performed because the resource does not have any attributes that have baselines. This may be because another user has deleted the baselines. The resource class is P1 and the name is P2.
System Action:
None.
User Action:
None.
Reason:
A request to display the performance history for a resource has failed because no history exists.
System Action:
None.
User Action:
If necessary, update the resource and set monitoring to active.
Reason:
A request to display the sampling history for a resource using the view
P1 failed because the view does not exist.
System Action:
None.
User Action:
Create the view before issuing the request.
Reason:
A request to the Data Framework database failed. The failed action is P1 and the file ID is P2. P3 is the file return code, P4 is the file error code, P5 is the key (only present for some actions) and P6 is an optional error message.
System Action:
Processing terminates.
User Action:
Check the file error code in the VSAM Macro Return and Reason Codes section of the DFSMS Macro Instructions for Data Sets SC26-7408-01 manual.
If the reason indicates a macro error, contact Technical Support.
Reason:
An attribute read from the DF database is invalid. P1 is the key of the record in error and P2 is the error message indicating the error.
System Action:
The attribute data that may have been saved on the database is ignored.
User Action:
Contact Technical Support.
Reason:
The Data Framework database cleanup process searches the performance statistics database and deletes all unreferenced baseline data older than 70 days. This data represents baseline performance metrics for attributes that are no longer being sampled and hence no longer provide value. This helps to keep the database size under control.
This message indicates that the cleanup process has started.
System Action:
The cleanup process removes unreferenced attributes.
User Action:
None.
Reason:
The Data Framework database cleanup process searches the performance statistics database and deletes all unreferenced baseline data older than 70 days. This data represents baseline performance metrics for attributes that are no longer being sampled and hence no longer provide value. This helps to keep the database size under control. This message indicates that this process has completed and that P1 attributes were removed from the database.
System Action:
None.
User Action:
None.
Reason:
Data sampling is unable to add or update baseline data in the MSDB file. The file is full or unable to expand to an additional extent due to a lack of DASD space.
System Action:
Attempts to add or update baseline records fail. Details of each failure appear in the activity log (see message DFDBPKG03).
User Action:
If the file is full, you must increase its size.
To recover from a file-full condition
Reason:
The resource identified by class P1 and name P2 was not found in the data framework sampling database. This may be because the resource is not defined or it is defined and has had its monitoring activity turned off.
System Action:
Processing terminates.
User Action:
The resource can be added or have its monitoring activity turned on via the /RADMIN menu.
Reason:
The baseline for the indicated attribute is migrated to the p5 file from the p6 file.
p1 is the resource class.
p2 is the resource name.
p3 is the attribute ID.
p4 (optional) is an attribute qualifier.
System Action:
Processing continues.
User Action:
None.
Reason:
The migration of attribute baselines to the p1 file from the p2 file is complete. During the migration process, there were p3 errors and p4 warnings.
System Action:
Processing continues.
User Action:
If there are errors, check and review other messages for more details of the process, and for details of the errors that occurred.
Reason:
During the migration process, p1 baseline attributes were found in the p2 file.
System Action:
Processing continues.
User Action:
For more details on the baseline migration process, check the other messages prefixed with DFDBPKG.
Reason:
Before the start of migration, p1 baseline records were deleted from the p2 file.
System Action:
Processing continues.
User Action:
For more details on the baseline migration process, check the other messages prefixed with DFDBPKG.
Reason:
A baseline cannot be retrieved from the p1 file because an expected record with the p2 key was not found. The baseline for the attribute cannot be recovered and is ignored.
System Action:
Processing continues.
User Action:
None.
Reason:
There were p1 attribute baselines converted and saved as p2 records in the p3 file.
p4 is the minimum record length.
p5 is the average length.
p6 is the maximum length.
p7 is the total of number of bytes.
System Action:
Processing continues.
User Action:
None.
Reason:
There were p1 baseline records deleted from the p2 file after the migration process completed.
System Action:
Processing continues.
User Action:
For more details on the baseline migration process, see the other messages prefixed with DFDBPKG.
Reason:
The process of migrating sampled attribute baselines has started.
p1 identifies the file to which the baselines are migrated.
p2 identifies the file from which the baselines are migrated.
System Action:
Processing continues.
User Action:
For more details of the process and for any errors, see the other messages prefixed with DFDBPKG.
Reason:
The migration of sampled attribute baselines does not start because there are existing baselines in the output file.
p1 identifies the output file to which the baselines are to be migrated.
p2 identifies the input file from which the baselines are to be migrated.
System Action:
Processing terminates.
User Action:
If you want to force the migration to occur even though there are existing baseline records in the P1 file, you must use the FORCE=YES parameter.
FORCE=YES allows you to migrate into a file that has existing baseline records. If the RESET=YES parameter is also specified, then all the existing baseline records will be deleted before the migration takes place. If you do not specify the RESET= parameter or specify RESET=NO, then existing baseline records in the P1 file will not be deleted; however if an existing baseline record conflicts with a migrating record, then the migrating record will overwrite the existing record.
Reason:
The migration process encountered a baseline record, p1 , that is invalid and cannot be interpreted. The baseline data is ignored.
This condition can occur if baselines were not saved successfully to the VFS.
System Action:
Processing continues. The discarded baseline cannot be recovered.
User Action:
None.
Reason:
During the migration process, this message appears approximately every 30 seconds to indicate the stage of the process that is being performed.
p1 identifies the file to which the baselines are migrated.
p2 identifies the file from which the baselines are migrated.
p3 indicates the current stage of the migration.
System Action:
Processing continues.
User Action:
None.
Reason:
The migration of sampled attribute baselines has completed and there were no existing baselines in the input file to convert and transfer to the output file.
p1 identifies the output file to which the baselines are to be migrated.
p2 identifies the input file from which the baselines are to be migrated.
System Action:
Processing terminates.
User Action:
None. If baselines were expected to exist in the file P2 then check that the dataset specified was correct or that the baselines have not already been migrated.
Reason:
The p2 parameter cannot be specified if the p1 parameter is already specified.
System Action:
Processing terminates.
User Action:
Specify either p1 or p2 but not both parameters.
Reason:
The value of the 2 parameter cannot be the same as the value of the p1 parameter.
System Action:
Processing terminates.
User Action:
Specify different values for p1 and p2.
Reason:
p1 is both the input and the output data set. The data sets must be different.
The input data set (or the data set containing the data you want to migrate) is specified by one of the following parameters:
Specifies the file ID of an allocated and open input data set.
Specifies the name of the input data set. The command will allocate and open this data set.
The output data set (or the data set to which you want to migrate data) is specified by one of the following parameters:
Specifies the file ID of an allocated and open output data set.
Specifies the name of the output data set. The command will allocate and open this data set.
Note: If the parameters are omitted, then the defaults are FFID=VFS and TFID=MSDB.
System Action:
Processing terminates.
User Action:
Specify different input and output data sets.
Reason:
A request to migrate baselines from an old VFS file to a new MSDB file was aborted because an error was encountered while processing the command parameters. p1 displays the error.
The correct command syntax is as follows:
$CAPKCAL $DFDBPKG DFDBMIGRATE { FFID=vfs_file_id |
FDSN=data_set_name }
[ TFID=MSDB | TDSN=data_set_name ]
[ RESET={ NO | YES } ]
[ FORCE={ NO | YES } ]
[ CLEANUP={ NO | YES } ]
Specifies the file ID or data set name of the VFS that contains the data to be migrated.
Specifies the file ID or data set name of the MSDB file to which data is to be migrated.
Default: TFID=MSDB
Specifies whether existing baseline data is deleted from the MSDB before migration.
Default: NO
Specifies whether to migrate the data even when the MSDB contains baseline data. If data exists for an attribute in both the VFS and the MSDB, the data in the MSDB is overwritten. That is, any data collected for that attribute in the MSDB is lost.
Default: NO
Specifies whether to delete the migrated baseline data from the VFS.
Default: NO
We recommend that you submit the command to the background system user because migration can take a while and you may not want to wait for the command to complete before logging off. Use the command:
SUBMIT BSYS $CAPKCAL $DFDBPKG DFDBMIGRATE...
System Action:
Processing terminates.
User Action:
Correct the command parameters as indicated by the error message p1.
Reason:
The migration of baselines from an old VFS file to a new MSDB file has ended.
System Action:
Processing terminates.
User Action:
Check previously issued messages prefixed with DFDBPKG that indicated the success of the migration process.
Reason:
During the migration of baselines, an error occurred with the p1 data set.
System Action:
Processing terminates.
User Action:
Check a message prefixed with DFDBPKG that follows this message and identifies the specific error.
Reason:
During the migration of baselines, a data set error occurred. The characteristics of the data set are not compatible, and the data set cannot be used for baseline migration.
p1 identifies the specific characteristic that is not compatible.
In general, both data sets must be VSAM key-sequenced data sets. The data set from which to migrate baselines must have a key length of 36 and is a VFS from a region running a previous version. The data set to which baselines are migrated must have a key length of 132 and is a MSDB created for newer versions.
System Action:
Processing terminates.
User Action:
An earlier DFDBPKG message identifies the data set in error. Retry the command, specifying a valid VFS or MSDB data set.
Reason:
An invalid value for Baseline Type has been specified. It must be either Daily, DayOfWeek, or HourOfDay.
System Action:
The attribute definition is not updated.
User Action:
Specify a valid Baseline Type.
Reason:
Alerting details have been defined for Baseline alerting, but no baseline has been specified.
System Action:
The attribute definition is not updated.
User Action:
You must specify a valid Baseline Type if you want to alert against baselines.
Reason:
An invalid value for the monitoring rate has been specified. The rate value specifies the monitoring interval in minutes and it must be at least 5 and not greater than 60 minutes.
System Action:
The attribute definition is not updated.
User Action:
Specify a valid Rate value.
Reason:
An invalid value for the PING Packet size has been specified. The value sets the size of each echo request to be sent to the TCP/IP host. The default value is 256.
System Action:
The attribute definition is not updated.
User Action:
Specify a valid packet size value.
Reason:
An invalid value for the PING Count has been specified. The value sets the number of echo requests to send to the TCP/IP host. The default value is 3.
System Action:
The attribute definition is not updated.
User Action:
Specify a valid count value.
Reason:
An invalid value for the PING Wait has been specified. The value sets the number of seconds to wait for a response to each echo request. The default value is 3.
System Action:
The attribute definition is not updated.
User Action:
Specify a valid Wait value.
Reason:
The CANCEL command was used to terminate the action.
System Action:
None.
User Action:
None.
Reason:
The application ID P1 is not defined to the Data Sampling framework.
System Action:
The Data Sampling action is terminated.
User Action:
Report the error to your technical support representative.
Reason:
A request to update a list of Alert Automated Actions has failed because the selected alert does not specify any threshold.
System Action:
The request is rejected.
User Action:
Update the selected alert and specify an alert threshold before defining an action.
Reason:
A request to Clear Actions has failed because the selected alert has no associated actions.
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to Reset Alert has failed because the selected alert has no thresholds defined.
System Action:
The request is rejected.
User Action:
None.
Reason:
A baseline type has been specified, but no alert threshold has been defined.
System Action:
The attribute definition is not updated.
User Action:
You must specify a baseline alert threshold or if not required, clear the Baseline Type field.
Reason:
A request to display a list of Alert Automation Actions has failed because none have been defined.
System Action:
The request is rejected.
User Action:
None.
Reason:
A request was made to view a list of known qualifiers for a qualified attribute.
System Action:
None.
User Action:
None.
Reason:
A request was made to view a list of known qualifiers for a qualified attribute but nothing was found.
System Action:
None.
User Action:
Try again after monitoring has been in progress for this class-resource-attribute-qualifier combination for at least 1 hour.
Reason:
A request was made to view a list of known qualifiers for a qualified attribute but only the first 999 qualifiers were shown.
System Action:
None.
User Action:
To show the full list of qualifiers clear the Qualifier field and hit PF10=Baseline. This is not an option for enumerated attributes.
Reason:
Resource monitoring raised a severity P1 alert for the P2 attribute. The alert description is P3.
System Action:
None.
User Action:
Use the AL action for a resource to see the alerts. Use the Alert Monitor (shortcut /ALERTS) to see all alerts.
Reason:
An Above Baseline data sample was returned for the P2 attribute of resource P1 P8.
The latest sample value or rate is P3. This is P4 % above the P5 baseline of P6.
A baseline is a moving average of hourly summary values. This alert is raised if a P2 sample value or hourly rate is more than P7% above the P5 baseline.
A sample which is a significant percent higher than an established baseline indicates atypical activity and might signify an impending performance problem.
Note: For counter or total attributes, the sample value is converted to its equivalent hourly rate before it is compared to the baseline. For gauge attributes, the unchanged sample value is compared to the baseline.
System Action:
If an alert already exists for this attribute and resource, its elapsed time and occurrence count are incremented.
If not, a new alert is raised..
User Action:
Use the IP Resource Monitor, IP Node Monitor, or the Performance options to view the performance history of this resource.
To specify what performance attributes are sampled and when performance data alerts are raised and cleared, update the monitoring definition for this resource.
Reason:
An Above Baseline value was returned by each of the last three data samples of the P2 attribute of resource P1 P8.
The last sample value/rate is P3.
This is P4% above the P5 baseline of P6.
A baseline is a moving average of hourly summary values.
This is a "Three Strike Alert". This alert is only raised after a value exceeding the P5 baseline by more than the specified percent of P7% is returned for three successive sampling intervals.
Back-to-back samples a significant percent higher than an established baseline indicate a pattern of atypical activity and might signify an impending performance problem.
Note: For counter or total attributes, the sample value is converted to its equivalent hourly rate before it is compared to the baseline. For gauge attributes, the unchanged sample value is compared to the baseline.
System Action:
If an alert already exists for this attribute and resource, its elapsed time and occurrence count are incremented. If not, a new alert is raised.
Note: For Three Strike Alerts, no action is taken for the 1st or 2nd above baseline sample. Alerting is triggered only by the 3rd consecutive above baseline sample.
User Action:
Use the IP Resource Monitor, IP Node Monitor, or the Performance options to view the performance history of this resource.
To specify what performance attributes are sampled and when performance data alerts are raised and cleared, update the monitoring definition for this resource.
Reason:
A Below Baseline data sample was returned for the P2 attribute of resource P1 P8.
The latest sample value or rate is P3.
This is P4% below the P5 baseline of P6.
A baseline is a moving average of hourly summary values. This alert is raised if a P2 sample value or hourly rate falls more than P7% below the P5 baseline.
A sample which is a significant percent lower than an established baseline indicates atypical activity and might signify an impending performance problem.
Note: For counter or total attributes, the sample value is converted to its equivalent hourly rate before it is compared to the baseline. For gauge attributes, the unchanged sample value is compared to the baseline.
System Action:
If an alert already exists for this attribute and resource, its elapsed time and occurrence count are incremented. If not, a new alert is raised.
User Action:
Use the IP Resource Monitor, IP Node Monitor, or the Performance options to view the performance history of this resource.
To specify what performance attributes are sampled and when performance data alerts are raised and cleared, update the monitoring definition for this resource.
Reason:
A Below Baseline value was returned by each of the last three data samples of the P2 attribute of resource P1 P8.
The last sample value/rate is P3.
This is P4% below the P5 baseline of P6.
A baseline is a moving average of hourly summary values.
This is a "Three Strike Alert". This alert is only raised after a value below the P5 baseline by more than the specified percent of P7% is returned for three successive sampling intervals.
Back-to-back samples a significant percent lower than an established baseline indicate a pattern of atypical activity and might signify an impending performance problem.
Note: For counter or total attributes, the sample value is converted to its equivalent hourly rate before it is compared to the baseline. For gauge attributes, the unchanged sample value is compared to the baseline.
System Action:
If an alert already exists for this attribute and resource, its elapsed time and occurrence count are incremented. If not, a new alert is raised.
Note: for Three Strike Alerts, no action is taken for the 1st or 2nd below baseline sample. Alerting is triggered only by the 3rd consecutive below baseline sample.
User Action:
Use the IP Resource Monitor, IP Node Monitor, or the Performance options to view the performance history of this resource.
To specify what performance attributes are sampled and when performance data alerts are raised and cleared, update the monitoring definition for this resource.
Reason:
A High Value data sample was returned for the P2 attribute of resource P1 P5.
The latest sample value or rate is P3.
This alert is raised when a sample value or rate exceeds the specified high limit of P4.
A sample significantly higher than the limit may indicate unusual activity and might signify an impending performance problem.
Note: For counter or total attributes, the sample value is converted to its equivalent hourly rate before it is compared to the limit. For gauge attributes, the unchanged sample value is compared to the limit.
System Action:
If an alert already exists for this attribute and resource, its elapsed time and occurrence count are incremented. If not, a new alert is raised.
User Action:
Use the IP Resource Monitor, IP Node Monitor, or the Performance options to view the performance history of this resource.
To specify what performance attributes are sampled and when performance data alerts are raised and cleared, update the monitoring definition for this resource.
Reason:
A High Value sample above the limit of P4 was returned by each of the last three data samples of the P2 attribute of resource P1 P5.
The last sample value or rate was P3.
This is a "Three Strike Alert". This alert is raised only after a sample value or rate exceeding the specified high limit of P4 has been returned for three successive sampling intervals in a row.
Back-to-back samples significantly higher than the limit may indicate a pattern of unusual activity and may signify an impending performance problem.
Note: For counter or total attributes, the sample value is converted to its equivalent hourly rate before it is compared to the limit. For gauge attributes, the unchanged sample value is compared to the limit.
System Action:
If an alert already exists for this attribute and resource, its elapsed time and occurrence count are incremented. If not, a new alert is raised.
Note: For Three Strike Alerts, no action is taken for the 1st or 2nd high sample. Alerting is triggered only by the 3rd consecutive high sample.
User Action:
Use the IP Resource Monitor, IP Node Monitor, or the Performance options to view the performance history of this resource.
To specify what performance attributes are sampled and when performance data alerts are raised and cleared, update the monitoring definition for this resource.
Reason:
A Low Value data sample was returned for the P2 attribute of resource P1 P5.
The latest sample value or rate is P3.
This alert is raised when a sample value or rate falls below the specified low limit of P4.
A sample significantly lower than the limit may indicate unusual activity and may signify an impending performance problem.
Note: For counter or total attributes, the sample value is converted to its equivalent hourly rate before it is compared to the limit. For gauge attributes, the unchanged sample value is compared to the limit.
System Action:
If an alert already exists for this attribute and resource, its elapsed time and occurrence count are incremented. If not, a new alert is raised.
User Action:
Use the IP Resource Monitor, IP Node Monitor, or the Performance options to view the performance history of this resource.
To specify what performance attributes are sampled and when performance data alerts are raised and cleared, update the monitoring definition for this resource.
Reason:
A Low Value sample below the limit of P4 was returned by each of the last three data samples of the P2 attribute of resource P1 P5.
The last sample value or rate was P3.
This is a "Three Strike Alert". This alert is only raised after a sample value or rate below the specified low limit of P4 has been returned for three successive sampling intervals in a row.
Back-to-back samples significantly lower than the limit may indicate a pattern of unusual activity and may signify an impending performance problem.
Note: For counter or total attributes, the sample value is converted to its equivalent hourly rate before it is compared to the limit. For gauge attributes, the unchanged sample value is compared to the limit.
System Action:
If an alert already exists for this attribute and resource, its elapsed time and occurrence count are incremented. If not, a new alert is raised.
Note: For Three Strike Alerts, no action is taken for the 1st or 2nd low sample. Alerting is triggered only by the 3rd consecutive low sample.
User Action:
Use the IP Resource Monitor, IP Node Monitor, or the Performance options to view the performance history of this resource.
To specify what performance attributes are sampled and when performance data alerts are raised and cleared, update the monitoring definition for this resource.
Reason:
A value of P3 was returned by the last data sample of the P2 attribute of resource P1 P4.
An alert is raised when this value is detected.
Status related enumerated attributes generally indicate whether a device is operational or in a desired state.
Device statuses may be other than normal if one of the following conditions occurs:
System Action:
If an alert already exists for this attribute and resource, its elapsed time and occurrence count are incremented. If not, a new alert is raised.
User Action:
Use the IP Resource Monitor, IP Node Monitor, or the Performance options to view the performance history of this resource.
To see the values of all recent samples, use the Sample Values Graph.
Use the IP Monitors or the Diagnostics options to look for possible problems with this resource.
To specify what performance attributes are sampled and when performance data alerts are raised and cleared, update the monitoring definition for this resource.
Reason:
A value of P3 was returned by the last of three data samples of the P2 attribute of resource P1 P4.
This is a "Three Strike Alert". This alert is raised only after the value of attribute P2 has returned error values for three successive sampling intervals in a row. The last error value sampled was P3.
Status related enumerated attributes generally indicate whether a device is operational or in a desired state.
Device statuses may not be normal for the following conditions:
System Action:
If an alert already exists for this attribute and resource, its elapsed time and occurrence count are incremented. If not, a new alert is raised.
Note: For Three Strike Alerts, no action is taken for the 1st or 2nd sample with this value. Alerting is triggered only by the 3rd consecutive sample that returns the specified value.
User Action:
Use the IP Resource Monitor, IP Node Monitor, or the Performance options to view the performance history of this resource.
To see the values of all recent samples, use the Sample Values Graph.
Use the IP monitors or the Diagnostics options to look for possible problems with this resource.
To specify what performance attributes are sampled and when performance data alerts are raised and cleared, update the monitoring definition for this resource.
Reason:
The resource is monitored by a remote region that has been linked using migration mode. You cannot update the definition of such resources from this region.
System Action:
The action is rejected.
User Action:
Perform the action from the resource's home region or any region linked as a focal point to that home region.
Reason:
Another user is updating this definition.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
The user P1 is updating the IP node monitor group P2.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
The updated alert details are saved to the database. The values will be effective the next time a sample is taken. For IP conditions, the values will be reflected on the display at the next five-minute period.
System Action:
None.
User Action:
None.
Reason:
An attempt to save an unchanged definition was rejected.
System Action:
The definition is not saved.
User Action:
None.
Reason:
The monitoring of attribute P1 (which may have a qualifier in parenthesis) is already enabled for resource P2.
System Action:
None.
User Action:
None.
The resource already has the attribute in its monitoring definition.
Reason:
The selected condition has been enabled for monitoring. The related attribute will be sampled on the next scheduled interval. The condition will be effective at the next five-minute period after the sample is taken.
System Action:
None.
User Action:
None.
Reason:
Resource monitoring detected a severity 0 condition for a resource. The attribute sampled is P1. The associated description is P2.
System Action:
The alert actions are executed.
User Action:
None.
Reason:
An unsupported CALLTYPE was requested of a selection list service procedure. The unsupported call type is P1.
System Action:
Processing terminates.
User Action:
Contact your local technical support representative.
Reason:
A line command was entered against a record that does not support the command. The E (expand) and C (contract) line commands can only be entered against grouping records. The S (summary) and D (detail) commands can only be entered against data records.
System Action:
The command is rejected.
User Action:
Choose a different line command.
Reason:
The list cannot be displayed because the total number of lines in the list has exceeded the maximum of 9999.
System Action:
Display of the selection list terminates.
User Action:
The maximum number of lines that can be presented is 9999. Do not expand attributes or qualifiers that cause this limit to be exceeded. It may be preferable to limit the number of attributes or qualifiers that are sampled by your monitoring application.
Reason:
The sample display will be automatically refreshed when new samples are made for the resource currently displayed.
System Action:
Display has been refreshed and automatic refresh has been turned ON.
User Action:
None.
Reason:
The sample display will not be automatically refreshed when new samples are made for the resource currently displayed.
System Action:
Display has been refreshed and automatic refresh has been turned OFF.
User Action:
None.
Reason:
You entered UA beside an entry that does not support the action. For a column heading of Qualifier/Attribute , the action can only be used on attributes.
System Action:
The action is rejected.
User Action:
Enter the action beside an attribute.
Reason:
Another user is updating this definition.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
The updated alert details are saved to the database.
System Action:
None.
User Action:
None.
Reason:
An attempt to save an unchanged definition was rejected.
System Action:
The definition is not saved.
User Action:
None.
Reason:
Another user is updating this definition.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
The resource displayed is running on a region linked in MIGRATION mode. The UA action is not supported for these resource.
System Action:
The action is rejected.
User Action:
Issue the action from the resource's home region, or any region linked as a focal to the resource's home region.
Reason:
An unsupported CALLTYPE was requested of a selection list service procedure. The unsupported call type is P1.
System Action:
Processing terminates.
User Action:
Contact your local technical support representative.
Reason:
A request to present the statistics for the attribute P1 failed because the attribute was not present in the history sample.
System Action:
Processing terminates.
User Action:
Check that sampling is activated for the resource. It is possible that statistics have not yet been gathered because the sampling interval has not expired.
Reason:
A request to increase the scale was rejected because the current scale is already at the maximum allowed.
System Action:
Request rejected.
User Action:
None.
Reason:
A request to reduce the scale was rejected because the current scale is already at the minimum allowed.
System Action:
Request rejected.
User Action:
None.
Reason:
A request to display a bar chart of P1 values failed because no samples are available yet. Summary values are available on the hour while detail values are reported on the next sampling period.
For example, if the current time is 4:30PM, the next summary value will be reported at 5.00PM while the next detail value will be reported at 4:45PM for a sampling period of 15 minutes.
System Action:
None.
User Action:
Retry till the next reporting period. Summary charts are reported on the hour while detail charts are reported on the next sampling period.
Reason:
An unsupported CALLTYPE was requested of a selection list service procedure. The unsupported call type is P1.
System Action:
Processing terminates.
User Action:
Contact your local technical support representative.
Reason:
A request to present the statistics for the attribute P1 failed because the attribute was not present in the history sample.
System Action:
Processing terminates.
User Action:
Check that sampling is activated for the resource. It is possible that statistics have not yet been gathered because the sampling interval has not expired.
Reason:
A request to increase the scale was rejected because the current scale is already at the maximum allowed.
System Action:
Request rejected.
User Action:
None.
Reason:
A request to reduce the scale was rejected because the current scale is already at the minimum allowed.
System Action:
Request rejected.
User Action:
None.
Reason:
A request to display a bar chart of P1 values failed because no samples are available yet. Summary values are available on the hour while detail values are reported on the next sampling period.
For example, if the current time is 4:30PM, the next summary value will be reported at 5.00PM while the next detail value will be reported at 4:45PM for a sampling period of 15 minutes.
System Action:
None.
User Action:
Retry till the next reporting period. Summary charts are reported on the hour while detail charts are reported on the next sampling period.
Reason:
Trace information produced by many performance data displays is written to the activity log as this message.
Usually, performance display tracing is disabled. Enable this tracing only when requested by Technical Support.
Tracing may produce a large number of trace messages and should be left enabled only as long as necessary.
Performance data displays that produce trace data include the following:
- 3270 Performance Overview
- Baseline, Samples, Hourly/Daily Summary, and Weekly Interval lists
- Some WebCenter performance pages
The format of the message varies but is frequently as follows:
- The first word of the message is always the name of the issuing procedure.
- The second or third word is usually a keyword, such as the following:
Parmdata indicates the parameter data input to the procedure.
Exitdata indicates the summary/count of the output data from the procedure.
Callrc indicates the return code from an external call made by the procedure.
Diag indicates diagnostic information for the procedure.
System Action:
Messages with ID DFUI0099 are written to the activity log.
User Action:
If requested, enable tracing and provide these messages to Technical Support. Disable tracing when enough trace messages have been produced. You can peform these tasks from an OCS window.
To enable tracing, enter the following command:
$glbl $dftrui 1
To disable tracing, enter the following command:
$glbl $dftrui 0
Reason:
A performance history action (hours, days, weeks, or baseline values) was requested for an enumerated attribute. Performance history data is kept for numeric attributes (attribute types counter, total, gauge) only.
The only action available for enumerated attributes is S (samples).
System Action:
None.
User Action:
None.
Reason:
A run-time error was detected when processing a P1 display. This is generally caused by unexpected data values, which may be the result of device or data sampling errors.
System Action:
None.
User Action:
Retry the action.
If the problem persists, provide your support staff with any additional error details from Activity Log message DFUI00L03.
Reason:
A run-time error was detected during a performance data display. This message contains all available details of the error.
System Action:
None.
User Action:
None.
Reason:
A request was made to display performance data sourced from a remote NetMaster region, via link or domain name P1 .
This is not possible because the remote region cannot be contacted. Either the region itself, or the link to it, is not active.
System Action:
None.
User Action:
None. This function is not available until the remote NetMaster region restarts, and/or the link to it recovers.
Reason:
A request was made to show a Performance Overview; however, no performance history data of this type is currently available.
In most cases this is not an error. It may indicate a normal condition, such as one of the following:
System Action:
None.
User Action:
Ensure that all necessary resources are monitored by the IP Resource Monitor.
Ensure that performance monitoring is active for these resources (use command UM - Update Monitoring, from the IP Resource Monitor), and that all required attributes are enabled.
If this region has been active for a very short time, wait for an hour for hourly performance summarization to occur, then retry the request.
Confirm that the Packet Analyzer, SSI, and SMF interface are set up correctly and that they are active.
Reason:
A request was made to display Performance Overviews from domain P1. This is not possible because P1 is running an earlier version of the product, which does not support this display.
System Action:
None.
User Action:
None.
This function is not available until the linked region is upgraded to r11.5 or later.
Reason:
A request was made to show a Performance Overview; however, no resources of this type are currently being monitored.
The type refers to one of the IP Monitor resource classes: STACK, ASMON, EE, APPNHPR, CIP, CSM, IPNODE, VIPA or OSA.
No P1 resources are being monitored by this region. This is displayed when the Overview is requested from the local system. This region must be monitoring resources before they appear on any local Performance Overviews.
No P1 resources are being monitored by region ?nmid on ?sysid is displayed when the Overview is requested from a remote system. The remote region ?nmid on system ?sysid must be monitoring resources, before they appear on any Performance Overviews from that remote link/domain.
Note: Resources of this type may appear in this region's IP Summary, even if they are not known to the IP Resource Monitor. The IP Summary gets real/near-time data from the Packet Analyzer for all resources involved in IP activity. To collect longer-term performance history data, resources must be defined to the IP Resource Monitor.
System Action:
None.
User Action:
If the system does not include any resources of this type, no action is possible or necessary.
If the system does include resources of this type, check the following:
IP resources are found by the auto-discovery (Express Setup), which is run the first time the region is initialized.
To add new resources to the IP Resource Monitor, you can rerun auto-discovery at any time.
To add new IP Nodes to the IP Node Monitor, add their details to the required IP Node Monitor group.
Use the UM command next to a resource on the IP Resource Monitor, and ensure that all attributes that you are interested in are listed.
For more information about how to set up performance monitoring, see the User Guide.
Reason:
A sort command was entered on a Performance Overview; however, the sort column specified is not valid.
- Sort column 99 does not exist; it must be between 1 and N inclusive
The integer that you specified does not indicate a valid column.
- Sort column XX does not match the start of any column heading
No column heading starts with the characters XX.
Sort command format:
SORT ?sort-column ?optional-sort-direction
?sort-column can be one of the following:
- An integer that indicates the column number.
- A character string that partially or fully matches a column heading. This string is case- insensitive. It cannot contain blanks. If it matches more than one column heading, the first one is sorted. ?optional-sort-direction can be A (ascending) or D (descending) The default is descending for numeric columns; otherwise ascending.
System Action:
None.
User Action:
Retry the command with a correct sort column specification.
You can also press F4 (Sort) repeatedly, to sort on each column in turn.
Reason:
A sort command was entered on a Performance Overview; however, the sort direction specified is not valid.
Sort command format:
SORT ?sort-column ?optional-sort-direction
?sort-column can be one of the following:
- An integer that indicates the column number.
- A character string that partially or fully matches a column heading. This string is case- insensitive. It cannot contain blanks. If it matches more than one column heading, the first one is sorted.
?optional-sort-direction is either a (ascending) or d (descending). If omitted, the default sort direction is used - descending for numeric columns, ascending for character columns.
A frequent reason for this error is that you have specified a sort column with embedded blanks. Column headings that appear with blanks or on multiple lines on the display should be specified without blanks, for example, TelnetB for Telnet Bytes, or TCPOpensP for TCP Opens Passive.
In general, for column headings with long unique prefixes it is easier to specify the sort column as an integer. Alternatively, use F4 (Sort).
System Action:
None.
User Action:
Retry the command with the correct sort direction. Omit the direction, to use the default. You can also press F4 (Sort) repeatedly, to sort on each column in turn.
Reason:
Performance Overviews are initially sorted by resource name. Use the SORT command to sort the data by any column and direction.
Sort command format:
SORT ?sort-column ?optional-sort-direction
?sort-column can be one of the following:
- An integer that indicates the column number.
- A character string that partially or fully matches a column heading. This string is case- insensitive. It cannot contain blanks. If it matches more than one column heading, the first one is sorted.
Column headings that appear with blanks or on multiple lines should be typed without blanks, for example, TelnetB for Telnet Bytes or TCPOpensP for TCP Opens Passive. In general, for column headings with long unique prefixes it is easier to type the sort column as an integer. Alternatively, use F4 (Sort).
?optional-sort-direction is either a (ascending) or d (descending). If omitted, the default sort direction is used - descending for numeric columns, ascending for character columns.
Sort Command Examples:
sort 6 a Ascending sort on 6th column
sort bytesi Descending sort on Bytes Inbound column
sort byteso a Ascending sort on Bytes Output column sort s Descending sort on the first column whose name starts with s
sort ippkts Descending sort on the first column whose name starts with IP Pkts
sort ippktsr Descending sort on column IP Pkts Received
System Action:
None.
User Action:
Enter a valid SORT command.
You can also press F4 (Sort) repeatedly, to sort on each column in turn.
Reason:
This Performance Overview display is sorted as requested.
P1 is the position of the sort column. P2 is the column heading of the sort column. P3 is the sort order, either descending or ascending.
Sort command format:
SORT ?sort-column ?optional-sort-direction
?sort-column can be one of the following:
- An integer that indicates the column position.
- A character string that partially or fully matches a column heading. This string is case- insensitive. It cannot contain blanks. If it matches more than one column heading, the first one is sorted. ?optional-sort-direction can be either A (ascending) or D (descending) The default is descending for numeric columns, otherwise ascending.
You can also press F4 (Sort) repeatedly, to sort on each column in turn.
System Action:
None.
User Action:
None.
Reason:
User P1 attempted to display a P2-related Performance Overview, but did not have the necessary authorization.
System Action:
None.
User Action:
Contact your security administrator.
Reason:
A request was made from a Performance Overview display to show a related workload display. P1 is the related display type. However, the related display cannot be shown due to insufficient data.
Stack monitoring is active, but no workload samples of this type have been recorded since this region was restarted. This may be because of the following reasons:
- Stack monitoring has detected no Connection, Telnet, or FTP activity.
Use the other Connection Workload, Telnet Workload, and FTP Workload Performance Overviews to see if any recent workload activity has been detected.
- Connection, Telnet, or FTP activity may have been detected, but the specific attributes that record this activity on a 'by network' or 'by interface' (home address) basis are not being monitored.
Unlike other workload attributes, the 'by network' and 'by interface' attributes are not monitored by default and must be explicitly added.
System Action:
None.
User Action:
Ensure you are monitoring the necessary attributes for this Overview.
To add and administer monitored attributes
1. Enter /IPMON .
IP Resource Monitor appears.
2. Enter UM beside the required stack.
The Monitoring Definition panel appears. From this panel, you can administer the monitoring attributes.
For Connection, Telnet, and FTP Workload by Network, you need to monitor the Con*ByNet , Tel*ByNet , and &FTP*ByNet &attributes.
For Connection by Home Address, you need to monitor the Con*ByIf attributes.
When these attributes are being monitored, this is a a normal and expected condition after a region restart.
Retry the request after waiting for activity to occur. All Telnet and FTP Workload attribute values are derived from SMF records issued when a Telnet connection or FTP transfer terminates. Statistics for a connection are reported in the sampling interval in which the connection terminates. For Telnet and FTP throughput rates during connections, define Telnet and FTP as business applications, and use the Business Application Overview to supplement this Overview.
Reason:
A run-time error was detected when processing the data for this action. This is generally caused by unexpected data values, which may be the result of device or data sampling errors.
System Action:
None.
User Action:
Retry the action. As new samples summaries become available, the data values may change.
If the problem persists, provide your support staff with any additional error details from Activity Log message DFUIAPI11.
Reason:
A run-time error was detected when processing the data for this action. This message contains all available details of the error.
System Action:
None.
User Action:
None.
Reason:
A request was made to show a Performance Overview; however, no performance history data of this type is currently available.
In most cases, this is not an error. It may indicate a normal condition, such as one of the following:
System Action:
None.
User Action:
Ensure that all necessary resources are monitored by the IP Resource Monitor.
Ensure that performance monitoring is active for these resources (use command UM - Update Monitoring, from the 3270 IP Resource Monitor), and that all required attributes are enabled.
If this region has been active for a very short time, wait for an hour for hourly performance summarization to occur, then retry the request.
Confirm that the Packet Analyzer, SSI, and SMF interface are set up correctly and that they are active.
Reason:
A request was made to show a Performance Overview; however, no resources of type p1 are currently being monitored.
The type refers to one of the IP Monitor resource classes: STACK, ASMON, EE, APPNHPR, CIP, CSM, IPNODE, VIPA or OSA.
This region must be monitoring resources of this type, before they can appear on any Performance Overviews.
Note: Resources of this type may appear in this region's IP Summary, even if they are not known to the IP Resource Monitor. The IP Summary gets real/near-time data from the Packet Analyzer for all resources involved in IP activity. To collect longer-term performance history data, resources must be defined to the IP Resource Monitor.
System Action:
None.
User Action:
If the system does not include any resources of this type, no action is possible or necessary.
If the system does include resources of this type, check the following:
IP resources are found by the auto-discovery (Express Setup), which is run the first time a CA NetMaster region is initialized.
To add new resources to the IP Resource Monitor, you can rerun auto-discovery at any time.
To add new IP Nodes to the IP Node Monitor, add their details to the required IP Node Monitor group.
Use the UM command next to a resource on the 3270 IP Resource Monitor and ensure that all attributes that you are interested in are listed.
For more information about setting up performance monitoring, see the User Guide.
Note: All monitoring setup is done using the 3270 interface.
Reason:
A request was made to show a Performance Overview. While monitoring of P1 resources is active, no relevant performance samples have been taken for any individual P2 since this region last started.
Sampling commences after activity occurs.
System Action:
None.
User Action:
After a region restart, this is a normal condition for some types of performance data. Retry the request after waiting for activity to occur.
Ensure you are monitoring the required attributes for this Overview. For Connection, Telnet, and FTP Workload by Network, you need to monitor the Con*ByNet, Tel*ByNet, and FTP*ByNet attributes.
Reason:
A request was made to show a workload by network Performance Overview.
P1 is the type of stack workload (Connection, Telnet, or FTP).
Stack monitoring is active, but no network or interface (home address) workload samples of this type have been recorded since this region was restarted. This may be because of the following reasons:
- Stack monitoring has detected no Connection, Telnet, or FTP activity.
Use the other Connection Workload, Telnet Workload, and FTP Workload Performance Overviews to see if any recent workload activity has been detected.
- Connection, Telnet, or FTP activity may have been detected, but the specific attributes that record this activity on a 'by network' or 'by interface' (home address) basis are not being monitored.
Unlike other workload attributes, the 'by network' and 'by interface' attributes are not monitored by default and must be explicitly added.
System Action:
None.
User Action:
Ensure you are monitoring the necessary attributes for this Overview.
To add and administer monitored attributes
1. Enter /IPMON .
IP Resource Monitor appears.
2. Enter UM beside the required stack.
The Monitoring Definition panel appears. From this panel, you can administer the monitoring attributes.
For Connection, Telnet, and FTP Workload by Network, you need to monitor the Con*ByNet , Tel*ByNet , and FTP*ByNet attributes. For Connection by Home Address, you need to monitor the Con*ByIf attributes.
When these attributes are being monitored, this is a a normal and expected condition after a region restart.
Retry the request after waiting for activity to occur. All Telnet and FTP Workload attribute values are derived from SMF records issued when a Telnet connection or FTP transfer terminates. Statistics for a connection are reported in the sampling interval in which the connection terminates. For Telnet and FTP throughput rates during connections, define Telnet and FTP as business applications, and use the Business Application Overview to supplement this Overview.
Reason:
A request was made to show a Baseline List; however, no performance activity (sample observations, or hourly summaries) has been recorded for this resource since the monitoring region restarted, so there is no current performance data to compare.
System Action:
None.
User Action:
None.
Reason:
A request was made to show performance history data for a specific resource, attribute and qualifier, but the corresponding data record cannot be read.
Possible reasons for this may include:
- The data record has recently been deleted.
- An internal error occurred accessing the data sampling in-storage variable tables.
- An error occured loading the data into storage from the VFS file.
System Action:
None.
User Action:
None.
Reason:
A request was made to view historical performance data sourced from a linked region, P1. This is not possible because region P1 is running an earlier version of the product, which does not support this type of display.
System Action:
None.
User Action:
None.
This function is not available until the linked region is upgraded to r11.5 or later.
Reason:
A request was made to show a Samples List but no recent samples are available for this attribute, qualifier, and resource.
Recent samples are those which have been taken since the monitoring region was last restarted. Sample values are not retained across region restarts.
In some cases, sample values are available after the sample interval has passed. In others, sample values are only available after activity occurs.
System Action:
None.
User Action:
None.
Reason:
A request was made to show an Hourly Summary List, but this attribute /qualifier/resource has no hourly performance data.
Possible reasons for this may include:
- Monitoring of this attribute/qualifier/resource has only been active for a short time.
- The baseline data has very recently been deleted.
- The monitoring region has been restarted and performance history data is not yet loaded.
System Action:
None.
User Action:
None.
Reason:
A request was made to show a Daily Summary List or a Weekly Interval List, but this data cannot be displayed for this resource/attribute /qualifier.
Possible reasons for this may include:
- The available performance history data is too sparse to be aggregated into daily totals.
- Monitoring of this attribute/qualifier/resource has only been active for a short time.
- The baseline data has been deleted.
- The monitoring region has been restarted and performance history data is not yet loaded.
System Action:
None.
User Action:
None.
Reason:
An attempt to translate an object into an XML document for transmission to a data warehouse failed. The data was sourced from application P1, data class P2. The error occurred in mapping the object, the return code and feedback codes for the action were P3. P4 is the name of the component in error.
System Action:
The object is discarded and processing continues.
User Action:
Contact your local support representative.
Reason:
The NDB for which the report was requested could not be opened.
System Action:
The report request is cancelled.
User Action:
Correct the NDB name or open the requested NDB and retry.
Reason:
An attempt to get database information about the requested NDB failed.
System Action:
The report request is cancelled.
User Action:
Contact the systems administrator.
Reason:
An error occurred in the specified vartable P1.
System Action:
The report request is terminated. An incomplete report may have been produced.
User Action:
Contact the systems administrator.
Reason:
The requested NDB was not found.
System Action:
The report request is cancelled.
User Action:
Correct the NDB name or open the NDB and retry.
Reason:
The required parameter was not specified.
System Action:
The report request is cancelled.
User Action:
Correct the call parameters and retry.
Reason:
An invalid command was entered.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
The NDB system parameters were set successfully.
System Action:
None.
User Action:
None.
Reason:
The NDB system parameter indicated was unable to be set. Refer to the activity log for details.
System Action:
The system parameter is not changed.
User Action:
Determine the cause. Correct and retry.
Reason:
The SORT command was entered in the Command field, however, there were no entries displayed on the list.
System Action:
The command is rejected.
User Action:
None.
Reason:
The SORT command was entered in the Command field, however, a sort expression was not specified.
System Action:
The command is rejected.
User Action:
Specify a sort expression and retry.
Reason:
An error has occurred whilst defining an NDB format for the list. The NDB return code was P1 and the NDB error information was P2 .
System Action:
The selection list terminates.
User Action:
Check that the list exit is setting valid values in the &$NDNDBFF* variables.
Reason:
An error has occurred whilst defining a default NDB format for the list. A default NDB format is created when the list exit does not set &$NDNDBFF* variables. The NDB return code was P1 and the NDB error information was P2 .
System Action:
The selection list terminates.
User Action:
Look up the NDB return codes in the appropriate manual.
Reason:
The NDB which the list was accessing could not be opened. The name of the NDB was P1 , the NDB return code was P2 and the NDB error information was P3 .
System Action:
Request rejected.
User Action:
Correct the NDB name or open the requested NDB and retry.
Reason:
The NDB which the list was accessing could not be closed. The name of the NDB was P1 , the NDB return code was P2 and the NDB error information was P3 .
System Action:
Request rejected.
User Action:
Check that a procedure that has been called from the list has not closed the NDB during list processing.
Reason:
An error occurred getting a record from the NDB whilst building the list. The name of the NDB was P1 , the NDB return code was P2 and the NDB error information was P3 .
System Action:
Selection List Terminates.
User Action:
Check that a procedure that has been called from the list has not closed the NDB during list processing.
Reason:
You have entered a locate command when the list has not been sorted.
System Action:
Locate command rejected.
User Action:
Sort the list using the sort command or change the list handler definition for the list to specify a sort expression for the list.
Reason:
An error occurred whilst resetting the position in the list. The name of the NDB was P1 , the NDB return code was P2 and the NDB error information was P3 .
System Action:
Selection List Terminates.
User Action:
Contact your systems administrator.
Reason:
An error occurred whilst scanning the NDB for records to build the selection list.
P1 is the name of the NDB.
P2 is the NDB response code.
P3 is the NDB error information. If no NDB error information is available, then it displays the error description from the NETINFO database.
System Action:
The selection list terminates.
User Action:
The /NDBERR shortcut lets you find out more about the NDB response codes. For response codes 5 through 8, check the limits in the NDBLIMITS - NDB Processing Limits parameter group. You can change the following parameters:
- Maximum Logical I/O Limit for Response Code 5.
- Maximum Record Limit for Response Code 8.
- Maximum Storage Limit for Response Code 7.
- Maximum Elapsed Time Limit for Response Code 6.
If a value is already at the maximum, consider changing the selection criteria for the list to reduce the number of records read. If this is not practical, contact Technical Support.
Reason:
There were no records in the NDB that matched the criteria that was supplied for building the selection list.
System Action:
List terminates.
User Action:
If you were asked to specify some form of criteria, check that it is correct and retry.
Reason:
The LOCATE command has failed because of an invalid operand. The format of the operand depends on the NDB data format of the current sorting field that is in effect. The reason for the failure is described in P1:
Indicates that the operand contains nonnumeric characters or exceeds the allowable range (-2,147,483,648 to +2,147,483,647).
Indicates that the operand contains characters other than hexadecimal characters (0 to 9, A to F, or a to f) or contains an odd number of characters. For example, specify 02 instead of 2.
Indicates that the operand does not conform with any of the supported NCL date formats.
For more information about the supported date formats, see NCL Reference Guide.
Indicates that the operand is not in a valid time format (hh:mm:ss, hh.mm.ss, or hhmmss) with a value that ranges from 00.00.00 to 23.59.59.
Indicates that the operand is not in a valid timestamp format (NCL system variable &DATE11).
Indicates that the operand is not in valid floating point number notation or exceeds the limit of 0.1e+71.
System Action:
The LOCATE command is rejected.
User Action:
Specify the operand in a correct data format, and retry the command.
Reason:
The bottom of data was reached when trying to locate a record with a string specified with the LOCATE command.
System Action:
None.
User Action:
None.
Reason:
Procedure $NDCR04Z failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
None.
User Action:
Contact the system administrator.
Reason:
Right and left parentheses were entered without any search information between them. This is an invalid situation.
System Action:
Field highlighted in error.
User Action:
Enter some search information between the parentheses.
Reason:
While specifying a search the field identified by P1 was not entered and is a required field.
System Action:
Field highlighted in error.
User Action:
Enter a value for the specified field
Reason:
While defining a search the field highlighted as being in error will only accept the value identified by P1 as being valid.
System Action:
Field highlighted in error.
User Action:
Enter the valid value for the specified field
Reason:
An unbalanced number of parentheses have been specified in the search expression. P1 parentheses were specified on the left and P2 parentheses were specified on the right. There must be an equal number of parentheses on the left and right.
System Action:
Field highlighted in error.
User Action:
Add or remove parentheses to balance them.
Reason:
There was an NDB error on the database P1 . - The &NDBRC return code is P2 and the &NDBERRI error information is P3 .
System Action:
None
User Action:
Refer to the NCL Programmer Guide for information on the return code.
Reason:
The field name P1 that you specified is not a valid field name.
System Action:
Field highlighted in error.
User Action:
Enter a valid field name or place a '?' in the field to get a list of valid field names. You can also enter a field prefix followed by a ? for a list of field with that prefix.
Reason:
The line command P1 is an invalid line command. Valid line commands are:
I - Insert a line
D - Delete a line
R - Repeat a line
System Action:
Field highlighted in error.
User Action:
Enter a valid line command.
Reason:
The field in error contains characters other that the character P1 .
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
The field in error contains characters which are invalid.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
An attempt to open the VFS database failed with the FILERC identified by
P1 which may be 0 or 12. IF it is 0 then the file has been opened but may not be written to, it the FILERC is 12 it that the user does not have the authority to access the database.
System Action:
None.
User Action:
Contact your Security Administrator for assistance.
Reason:
An attempt to ADD a search criteria with a key of P1 failed because a record with this key already exists.
System Action:
ADD fails.
User Action:
Choose a different name for the search criteria or set the 'Replace?' field to YES.
Reason:
An attempt to perform the function identified by P1 on the VFS file failed with the Return Code identified by P2 and the Error identified by P3
System Action:
Request is rejected.
User Action:
Contact your System Administrator for assistance.
Reason:
The search criteria P1 was successfully saved to the VFS file.
System Action:
None
User Action:
None
Reason:
No search criteria have previously been saved for this search.
System Action:
None
User Action:
None
Reason:
The NDB which the fields list was accessing could not be opened. The name of the NDB was P1 , the NDB return code was P2 and the NDB error information was P3 .
System Action:
Request rejected.
User Action:
Correct the NDB name or open the requested NDB and retry.
Reason:
A request to present a field List failed because an error was encountered allocating a variable table. The request was P1 , the identifier of the vartable was P3 and the feedback code was P2 .
System Action:
The request is rejected.
User Action:
Interpret the feedback code using the NCL Reference.
Reason:
A request to present a fields List failed because an error was encountered accessing a vartable. The request was P1 , the identifier of the vartable was P3 , the feedback code was P2 and the key value used was P4 .
System Action:
The request is rejected.
User Action:
Interpret the feedback code using the NCL Reference.
Reason:
The NCL/EF Report Writer service procedure $NDRW06Z was unable to open the Database File (NDB). The name of the NDB to be opened was P1 and the NDB return code was P2 .
System Action:
Processing is terminated.
User Action:
Interpret the NDB return codes using NCL Programmer Guide.
Reason:
An error has occurred whilst deleting an NDB format for the report. The NDB return code was P1 and the NDB error information was P2 .
System Action:
The report terminates.
User Action:
Look up the NDB return codes in the appropriate manual.
Reason:
An error has occurred whilst defining an NDB format for the report. The NDB return code was P1 and the NDB error information was P2 .
System Action:
The report terminates.
User Action:
Look up the NDB return codes in the appropriate manual.
Reason:
There were no records found in the NDB that passed the report's criteria.
System Action:
None.
User Action:
None.
Reason:
An error occurred while scanning the NDB for records that pass the report's criteria. The NDB return code set by the &NDBSCAN verb was
P2 and the NDB error information was P3 .
System Action:
None.
User Action:
For information about diagnosing the error, see the Network Control Reference Guide. Some common NDBRC values are:
5 - I/O limit exceeded
6 - Time limit exceeded
7 - Storage limit exceeded
8 - Record limit exceeded
For these values, modify the criteria to be more specific or review the NDBLIMITS parameter group.
Reason:
An error occurred whilst attempting to retrieve field information from the vartable P1 . The feedback code set by the &VARTABLE verb was P2 .
System Action:
Request rejected.
User Action:
Contact your systems administrator.
Reason:
An error occurred getting a record from the NDB whilst building the report. The name of the NDB was P1 , the NDB return code was P2 and the NDB error information was P3 .
System Action:
Report Terminates.
User Action:
Contact your systems administrator.
Reason:
Procedure $NDUT07P failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
None.
User Action:
Contact the system administrator.
Reason:
The NDB record ID P1 that was to be displayed does not exist.
System Action:
Request Rejected.
User Action:
None.
Reason:
The NDB which the display was accessing could not be opened. The name of the NDB was P1 , the NDB return code was P2 and the NDB error information was P3 .
System Action:
Request rejected.
User Action:
Correct the NDB name or open the requested NDB and retry.
Reason:
An error occurred getting a record from the NDB whilst building the display. The name of the NDB was P1 , the NDB return code was P2 and the NDB error information was P3 .
System Action:
Dump of NDB Record Terminates.
User Action:
Contact you Systems Administrator.
Reason:
An error occurred deleting a record from the NDB. The name of the NDB was P1 , the NDB return code was P2 and the NDB error information was P3 .
System Action:
Delete of NDB record fails.
User Action:
Contact your Systems Administrator.
Reason:
You pressed the Cancel function key on the Confirm Force Delete panel so the delete request was cancelled.
System Action:
None.
User Action:
None.
Reason:
The NDB record P1 was successfully force deleted.
System Action:
None.
User Action:
None.
Reason:
An attempt by the NDB forward recovery utility (UTIL0010) to open a VSAM journal dataset or NDB failed for the reason given in the message.
System Action:
If it is the JOURNAL dataset that failed, processing is discontinued, otherwise processing continues with the next NDB.
User Action:
Check the JCL for the job and other job output. Correct and re-run.
Reason:
This message is issued by the NDB forward recovery utility when forward recovery is about to comence for an NDB.
System Action:
N/A
User Action:
N/A
Reason:
This message shows the VSAM retcode and feedback that occured for a journal record GET during NDB forward recovery processing.
System Action:
Forward recovery processing is terminated.
User Action:
Correct the job and re-run. If neccessary restore the journal dataset.
Reason:
The NDB forward recovery utility (UTIL0010) detected an unexpected VSAM return code while updating the NDB copy dataset.
VSAM retcode and feedback are displayed in the message.
System Action:
Forward recovery for the NDB is terminated and processing continues with the next NDB.
User Action:
Use the VSAM retcode information to diagnose the dataset error. If forward recovery can not be re-run, stop the primary NDB and copy it to the backup copy.
Reason:
This is an information message issued by the NDB forward recovery utility. no. UPDATES APPLIED shows the number of NDB records modified, no. TRANSACTIONS shows the number of NDB transactions found, no. JOURNAL RECORDS shows the number of journal records read.
System Action:
none.
User Action:
This message provides an indication of the activity against an NDB.
Reason:
The journal dataset specified to the NDB forward recovery utility was not a valid NDB journal.
System Action:
NDB forward recovery is terminated.
User Action:
Correct the forward recovery JCL.
Reason:
A SYSIN control card provided to the forward recovery utility was invalid.
System Action:
The control card is echoed with this message. Processing is terminated.
User Action:
Correct the SYSIN control card and re-submit job.
Reason:
This message is issued by the NDB forward recovery utility once the journal dataset has been successfully opened.
System Action:
Forward Recovery processing proceeds.
User Action:
N/A
Reason:
A journal validation error was detected by the NDB forward recovery utility (UTIL0010).
This was either because the journal being applied to the NDB is out of sequence, or the NDB domain id does not match the domain id of the journal.
System Action:
Processing for this NDB is terminated and continues for the NDB.
User Action:
Check the NDB with the reported error. It may be necessary to stop the primary NDB and restore the duplicate copy from it.
Reason:
This message follows a previous error message issued by the NDB Forward Recovery Utility, to warn of abnormal recovery termination for an NDB.
System Action:
N/A
User Action:
See related message.
Reason:
This message is issued if an error is detected in the time stamp sequence of records on the NDB journal. This may indicate that the journal was not correctly closed.
System Action:
Out of sequence journal records are not processed.
User Action:
This message usually may be taken as a warning only. Only records in the correct time sequence wil be applied to the NDB copies.
Reason:
The Dataset Services Manager external interface procedure $DSCALL failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $DSCALL terminates. Control is returned to the NCL procedure which executed $DSCALL. If $DSCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the NCL procedure which executed $DSCALL. If executed from OCS, check the command entered on the command line and retry.
Reason:
Processing requires that one of these keyword parameters be provided on the request. Keyword DD is the DDNAME. Keyword DSN is the dataset name. Since neither of these were provided the request is terminated.
System Action:
None.
User Action:
Provide either the DDNAME or the dataset name on the request.
Reason:
The data function being performed for a partitioned data set(PDS) requires a member name. P1 is the name of the PDS provided as input.
System Action:
None.
User Action:
Run the data function again providing a member name in the PDS name.
Reason:
A data function was requested which required a partitioned data set. The dataset P1 is not a partitioned dataset. The data function is cancelled.
System Action:
None.
User Action:
Check the dataset name supplied on the request. If it is correct think about what you are trying to do.
Reason:
A data function was requested which required a physical sequential dataset. The dataset P1 is not a physical sequential dataset. The data function is cancelled.
System Action:
None.
User Action:
Check the dataset name supplied on the request. If it is correct think about what you are trying to do.
Reason:
A data operation was requested using two files. P1 is the keyword parameter for the first file. P2 is the keyword parameter for the second file. The data operation requires the files to have the same logical record length. This is not the case so the data operation is cancelled.
System Action:
None.
User Action:
Examine the input parameters for the operation. Verify that the file names were entered correctly.
Reason:
A data operation was requested using two files. P1 is the keyword parameter for the first file. P2 is the keyword parameter for the second file. The data operation requires the files to have the same record format. This is not the case so the data operation is cancelled.
System Action:
None.
User Action:
Examine the input parameters for the operation. Verify that the file names were entered correctly.
Reason:
A data operation tried to use a path to access a file. The path did not exist. P1 is the name of the non-existent path. The data operation is terminated.
System Action:
None.
User Action:
Examine the input parameters for the operation. Verify that the parameters were entered correctly.
Reason:
An operation was requested for a file with record format U. This record format is not supported for the $DSCALL operation. P1 is the file name. The request is terminated.
System Action:
None.
User Action:
Perform the operation using a system utility instead of $DSCALL.
Reason:
A request to process an object was cancelled at the users request. P1 is the action that was cancelled.
System Action:
None.
User Action:
None.
Reason:
Dataset Services is supported on the following operating systems only:
- z/OS
- MSP
System Action:
User Action:
Reason:
A user confirmation is required before processing a requested action.
System Action:
None.
User Action:
Press either the Confirm or Cancel key (or enter the corresponding command) to continue.
Reason:
A request to call an operating system utility program was cancelled because the utility program is not supported by Dataset Services. P1 is the name of the utility program which is not supported.
System Action:
None.
User Action:
Use a supported utility or do the desired processing another way.
Reason:
A data operation was requested against a file. The operation is cancelled because the file has no records. P1 is the data operation.
System Action:
None.
User Action:
None.
Reason:
A request to edit a file was rejected because the file contains more than 32767 records. This is the maximum number of records that the CAS text editor can process.
System Action:
None.
User Action:
None.
Reason:
A request to browse a file that has more than 32767 records cannot be completed sucessfully. Only the first 32767 records are displayed. This is the maximum number of records that the CAS text editor can process.
System Action:
Browse of the first 32767 records.
User Action:
None.
Reason:
A data set services request was terminated because a member name was specified on a request for a partitioned dataset. The request does not allow a member name to be specified. P1 is the fully qualified dataset name used on the request.
System Action:
None.
User Action:
Either do not specify a member name on the request or request a different dataset service which allows the specification of a member name.
Reason:
An attempt was made to rename a PDS member to a sequential data set or to a PDS member of a different dataset. The request is terminated since a PDS member can only be renamed to a PDS member of the same dataset.
System Action:
None.
User Action:
Use the ALLOC, COPY, and DELMEM options to perform the rejected request.
Reason:
A request was made where a dataset name contained a member name. The use of the member name as part of the dataset set name was invalid in this request. P1 is the dataset name used in the request. The request is terminated.
System Action:
None.
User Action:
Examine what you were trying to do. Perhaps the use of a member name is inappropriate. Also, the problem may be that the member name should be specified using the MEMBER keyword in the request.
Reason:
The DSS_CALL verb was used to execute an IBM utility. The IBM utility did not execute succesfully. The error messages from the utility have been written to the SYSPRINT output.
System Action:
None.
User Action:
Read the SYSPRINT output if it is available.
Reason:
A maximum of 50 DDNAMEs can be concatenated using the $DSCALL utility. This limit has been surpassed in the request. The request is termiated with no concatenation done.
System Action:
None.
User Action:
Reduce the number of DDNAMEs in the concatenation request.
Reason:
The text being edited or browsed contains characters which can not be displayed. This message is informational only.
System Action:
None.
User Action:
None.
Reason:
A request was made to browse an IBM utility SYSPRINT file which was a SYSOUT file. The request was terminated. The SYSPRINT file must be a dataset to be browsed.
System Action:
None.
User Action:
Request that the SYSPRINT file be a dataset. Then the SYSPRINT file can be browsed. On a $DSCALL request, add parameter SYSPRINT=DSN to direct SYSPRINT to a dataset.
Reason:
The OPT=ALLOCINFO request requires one of the keyword parameters DD or RELNUM. Neither was provided. The request is terminated.
System Action:
None.
User Action:
Provide one of the two parameters on the request.
Reason:
An attempt was made to allocate (create) a dataset with an invalid or non-supported dataset organization. P1 is the dataset organization supplied on the request. The request is terminated.
System Action:
None.
User Action:
Examine the dataset organization parameter to see if it is correct. If the dataset organization is correct, then create the dataset using some means other than $DSCALL.
Reason:
An attempt was made to allocate (create) a dataset. The dataset organization required that directory blocks be allocated at creation time but no directory blocks were requested. P1 is the dataset organization. The request is terminated.
System Action:
None.
User Action:
Provide the number of directory blocks on the request. This is done by using the keyword parm DIR on the $DSCALL call.
Reason:
A dataset is being created with an allocation of directory blocks. However, directory blocks are not required for that dataset organization. P1 is the dataset organization. The request is terminated.
System Action:
None.
User Action:
Remove the directory block allocation from the request.
Reason:
The space parameter on a new dataset creation(allocation) request is incorrect. P1 is the component of the space parameter which is wrong.
P2 is the invalid value provided in the request.
System Action:
The request is terminated.
User Action:
Correct the space parameter and try again.
Reason:
A copy was requested and the target dataset was a PDS member. The REPLACE=NO option was specified on the request as well. However, the target PDS member P1 exists.
System Action:
The copy is terminated without writing over the target PDS member.
User Action:
Either specify REPLACE=YES on the copy or specify a non-existing target member name.
Reason:
A request to ENQ or DEQ a dataset was received with both the DD keyword parm and the DSN keyword parm specified. Only one of these parameters should be specified on the request.
System Action:
The request is terminated.
User Action:
Try the request again only specifying one of the keyword parameters.
Reason:
A data operation was terminated because no non-blank variables were found starting with the string provided with the VARS keyword parm.
System Action:
None.
User Action:
Check that the value of the keyword parm VARS is correct and that the variables starting with this keyword parm are shared on the call.
Reason:
An attempt was made to copy all PDS member matching a mask. P1 is the mask used on the request. No member names matched the mask.
System Action:
None.
User Action:
None.
Reason:
No path ID was provided on an open request. The DDname P1 was checked for use as a path ID. The DDname was already in use as a path ID.
System Action:
The open request is terminated.
User Action:
Examine the logic in your program. It may be that an attempt was made to open a file which was already open.
Reason:
A $DSCALL OPT=DELETE request was made and the keyword MEMBER was given a value. The member name is not a valid parameter on this request.
System Action:
The request is terminated.
User Action:
Use $DSCALL OPT=DELMEM to delete a PDS member.
Reason:
A $DSCALL OPT=RENAME request was made and the keyword MEMBER was given a value. The member name is not a valid parameter on this request.
System Action:
The request is terminated.
User Action:
Use $DSCALL OPT=RENMEM to rename a PDS member.
Reason:
The copy request specified member information in the MEMBER parameter and in the dataset name(s). These two methods are mutually exclusive.
System Action:
The COPY request is terminated.
User Action:
Provide member information on COPY request in just one place.
Reason:
A $DSCALL OPT=COPY request had the MEMBER parm specified and at least one of the FROMDSN and TODSN was not a partitioned dataset. The member parameter is valid only if both of these datasets are partitioned.
System Action:
The COPY request is terminated.
User Action:
Resubmit the request including the member information in the dataset name.
Reason:
The OPT=VOLSPACE call uses the IEHLIST utility to compute the number of free tracks on the volume. The IEHLIST utility output had fewer than the minimum expected number of lines. The OPT=VOLSPACE call terminates with this message.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
The dataset space calculation is not supported for the this particular dataset organization. The unsupported dataset organization is P1.
System Action:
None.
User Action:
None.
Reason:
The string "CYLINDERS" was expected to be found in the IEHLIST utility output. The line with the string contains the number of free cylinders on the volume. The free space on the volume could not be calculated because this line could not be located.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
The OPT=DSNSPACE call uses the IDCAMS utility to determine the data and index component names of a VSAM dataset. There was no output from the IDCAMS call. The OPT=DSNSPACE call terminates with this message.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
An error occurred while processing a VARTABLE. P1 is the function that was being performed when the error occurred. P2 is the name of the VARTABLE. P3 is the VARTABLE key. P4 is the &ZFDBK code.
System Action:
None.
User Action:
Determine the cause of the error from the feedback code.
Reason:
A request to move a dataset to volume was terminated because the target volume did not have enough free space. P1 is the number of free tracks required on the target volume.
System Action:
None.
User Action:
Select a different target volume with the required number of free tracks or make the required space available on the original target volume.
Reason:
A read/write operation was requested to a file which had logical record length greater than 250 bytes. No truncate option was specified on the request. The request is terminated.
System Action:
None.
User Action:
Specify a valid truncate length or read the record into multiple variables.
Reason:
A request has been received by Dataset Services to perform an action on a member of a Partitioned Dataset (PDS), but the dataset specified is not a PDS.
System Action:
The request is rejected.
User Action:
Remove the MEMBER= operand or specify the name of a dataset which is a PDS.
Reason:
A request has been received by Dataset Services to perform an action on a specified DD or dataset, and the DD or dataset is a Partitioned Dataset (PDS). The name of the member to be actioned has not been specified, and is required for this request.
System Action:
The request is rejected.
User Action:
Specify a member name using the MEMBER= operand.
Reason:
The requested function uses a utility which supports a maximum data length of 256. The data in the selected dataset exceeds this maximum.
System Action:
The request is rejected.
User Action:
None.
Reason:
The requested function uses $DSCALL OPT=READ and OPT=WRITE which support records length up to 250. The data in the selected dataset excesses this limit and is truncated. You can press Cancel key to abort the editing.
System Action:
The request is rejected.
User Action:
None.
Reason:
The requested function supplied a relative GDG number on a dataset name. The number is invalid for this function. For example, a positive number (greater than 0) for the OPT=INFO function.
System Action:
The request is rejected.
User Action:
Correct the number.
Reason:
A call to the IDCAMS program failed whilst attempting to derive the full dataset name for a relative generation number.
The actual $DSCALL return information is displayed
System Action:
The request is rejected.
User Action:
Examine the embedded error information to determine the cause of the problem.
Reason:
The OPT=INFO call uses the IDCAMS utility to determine the full dataset name of a relative GDG reference. There was no output from the IDCAMS call. The OPT=INFO call terminates with this message.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
The OPT=INFO call was passed a relative GDG reference (For example, A.B(-1)). However, the passed dataset name was not a GDG base name.
System Action:
The OPT=INFO request is terminated.
User Action:
Correct the GDG base name.
Reason:
The OPT=INFO call was passed a relative GDG reference (For example, A.B(-1)). However, the GDG currently has no entries.
System Action:
The OPT=INFO request is terminated.
User Action:
None.
Reason:
The OPT=INFO call was passed a relative GDG reference (For example, A.B(-1)). However, the reference is outside the range of current GDG entries. (For example, -5 when only 5 datasets (-4 up to 0).
System Action:
The OPT=INFO request is terminated.
User Action:
None.
Reason:
The requested action is not valid because the dataset is a SYSOUT file.
System Action:
The request is rejected.
User Action:
None.
Reason:
The selection list service procedure for the $DSCALL PDS member list displays failed because it received an invalid value for a shared variable. The variable name was P1 and it value was P2 .
System Action:
The selection list service procedure terminates.
User Action:
Contact your Systems Administrator.
Reason:
An invalid command was entered in the Command field on the panel.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
Function key P1 was pressed on the new member name data entry panel and the command assigned to it was invalid.
System Action:
The command is rejected.
User Action:
Correct the setting of the function key and retry.
Reason:
A request was received to rename a dataset or a member of a Partitioned dataset (PDS). When the new name was requested, the user cancelled the function.
System Action:
None.
User Action:
None.
Reason:
The selection list service procedure for the $DSCALL allocated files list display failed because it received an invalid value for a shared variable. The variable name was P1 and it value was P2 .
System Action:
The selection list service procedure terminates.
User Action:
Contact your Systems Administrator.
Reason:
No response was received for a command issued in the INTCMD environment in the alloted time. The procedure waiting for the response terminates.
System Action:
None.
User Action:
The system is extremely sluggish. That is why the response was not received in a reasonable time. Try what you were doing again when your system's performance is better.
Reason:
An unexpected response was received from a command issued in the INTCMD environment. P1 is the unexpected response. This response is not normally received from the command which was issued and could indicate a problem with your system. The procedure processing the response terminates after issuing this message.
System Action:
None.
User Action:
Contact your Systems Administrator.
Reason:
An error occurred while processing an NCL VARTABLE. P1 is the function that was being performed when the error occurred. P2 is the name of the VARTABLE. P3 is the VARTABLE key. P4 is the &SYS.FDBK code.
System Action:
None.
User Action:
Determine the cause of the error from the feedback code.
Reason:
A dataset which is not the first in a concatenation can not be deallocated. The request is terminated.
System Action:
None.
User Action:
Perform a deconcatenation, then the deallocation, and then do the concatenation again if you like.
Reason:
The selection list service procedure for the $DSCALL CATLIST list display failed because it received an invalid value for a shared variable. The variable name was P1 and it value was P2 .
System Action:
The selection list service procedure terminates.
User Action:
Contact your Systems Administrator.
Reason:
An invalid command was entered in the Command field on the panel.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
Function key P1 was pressed on the new name data entry panel and the command assigned to it was invalid.
System Action:
The command is rejected.
User Action:
Correct the setting of the function key and retry.
Reason:
The expected sysout output from a LISTCAT command has the dataset name followed by the catalog that the dataset is in on the next line. The catalog name did not follow the dataset name. P1 is the line which followed the dataset name. The procedure terminates when the unexpected line is found.
System Action:
None.
User Action:
Contact your Systems Administrator.
Reason:
A display of catalog entries for a qualifier was requested. P1 is the qualifier. However, there were no entries for the qualifier.
System Action:
The procedure terminates without a display.
User Action:
None.
Reason:
There was a problem in obtaining the display of cataloged datasets for a qualifier. P1 is the qualifier used in the display request.
System Action:
None.
User Action:
To see the error information for the request run: $DSCALL OPT=LISTC SYSPRINT=DSN DISPLAY=YES QUAL=P1 PARM=VOLUME where P1 is the qualifier used in the original display request.
Reason:
The selected option is invalid because the the dataset organization ( P1 ) does not support the type of request:
* to Browse, Edit, or Print a dataset the dataset organization must be either PO (Partitioned Organization - a PDS) or PS (Partitioned Sequential).
* to display a Member List the dataset must be a PDS; the dataset organization must be PO (Partitioned Organization)
System Action:
The request fails.
User Action:
Specify a different dataset or DD name.
Reason:
A request to browse a dataset or provide a member list cannot be actioned because both the Dataset Name and the DD Name are specified. Only one of these may be specified.
System Action:
The request fails.
User Action:
Remove either the Dataset Name or DD name and retry.
Reason:
The field contains embedded blank/s which is invalid.
System Action:
The request fails.
User Action:
Specify a correct name.
Reason:
The DSS menu service procedure $DS0004M failed because it received a menu number ($MHMENUNUM= P1 ) and/or function ($MHOPT= P2 ) that it does not support.
System Action:
Procedure $DS0004M terminates.
User Action:
Contact your Systems Administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
The requested action is not valid because the dataset is a SYSOUT file.
System Action:
The request is rejected.
User Action:
None.
Reason:
An attempt has been made to browse, delete, print, or rename a member of a dataset that does not exist.
System Action:
None.
User Action:
None.
| Copyright © 2012 CA. All rights reserved. |
|