MON10170 SPECIFIED RECORD NAME NOT IN RULES
Explanation: The record name specified on the Monitor request was not found in the rules language. This problem is probably caused by an invalid command definition in SCC Explorer.
Message Level: E
Response: Please contact Customer support.
MON10171 rectype reclen recname
Explanation: This message displays information about the record being processed by Monitor. The message displays the record type (GRID or REPORT format), the length of the record, and the record name.
Message Level: I
Response: None
MON10172 fldname offset length type mkey mftype
Explanation: This message displays information about each field in the record being processed by Monitor. The message displays the field name, the offset in the record, length, type, and the key and type fields used by SCC Explorer.
Message Level: I
Response: None
MON10180 # RECORDS WRITTEN TO name
Explanation: This message is displays information about each the number of records written to each PDS member during SPLIT processing. The SPLIT parameter on the SORT statement can be used to sort the output records into separate DD statements or PDS members using a field in the record to split the records into groups. For example, instead of producing a single large output file containing every data set for each storage pool, the SPLIT command can be used to create a PDS containing storage pool members and where each member contains only the records for the storage pool.
Message Level: A
Response: None
MON10220 INVALID DATE SPECIFIED
Explanation: An internal Monitor routing is attempting to convert a requested date into a standard internal format date string. This routine also handles the TODAY, TODAY+n, and TODAY-n requests. The format of the specified date is incorrect.
Message Level: E
Response: If you have questions about the date format, please contact Customer support.
MON10310 UNKNOWN REMOTE SYSTEM
Explanation: Monitor and JCLQA can be set up to run the application on remote systems. This is especially useful for many installations that run JCLQA. However, the system that is requesting remote execution did not have a DEFCONN statement that defined the connection.
Message Level: E
Response: If you have questions about running Monitor or JCLQA on remote systems, please contact Customer support.
MON10900 UNKNOWN COMMAND
Explanation: The Monitor COMMAND statement was used, but the only commands that the statement current support is HSEND and HSENDCMD. A non-supported command was requested using the COMMAND statement.
Message Level: E
Response: If you have questions about using the Monitor COMMAND statement, please contact Customer support.
MON10901 FUNCTION NOT ALLOWED BY SECURITY SYSTEM
Explanation: The Monitor COMMAND statement was used, but an installation security call (SAF) rejected the command request. The security call checked for READ access to the FACILITY class with an entity of command-name.
Message Level: E
Response: If you have questions about using the Monitor COMMAND statement, please contact Customer support.
MON10960 HFS CALL FOR pgmname - RC=rc-rs
Explanation: SCC Monitor is processing an HFS directory and made a call to pgmname. The call failed. The message displays the return and reason codes (rc and rs).
Message Level: E
Response: Please contact Customer support.
MON11110 FIELD field_name NOT DEFINED IN DEFREC
Explanation: The Monitor has a report generation facility. The product can examine the information from many sources: VTOCs, VVDSs, Catalogs, DFSMShsm MCDS, and SMF data. The rules language can use this information to write records that can be sorted, processed, and formatted into reports. This reporting facility is performed with an internal interface to the DFSORT ICETOOL utility.
A FORMAT, SELECT, or SORT statement used a field_name that could not be matched with a name in the record definition defined by the DEFREC statement.
For more information and examples, examine “Building Reports” on page 5-31 in the MON-Snapshot User’s Guide.
Message Level: E
Response: Correct the field name to use a valid field name defined in DEFREC.
MON11300 MORE THAN 20 FIELDS ON FORMAT
Explanation: SCC Monitor is processing a FORMAT statement. The statement uses ICETOOLS to produce the report. However, ICETOOLS is limited to formating 20 input fields, and the request on the FORMAT statement exceeded the limit.
Message Level: E
Response: None
MON11700 NO BVIR COMMAND SPECIFIE
Explanation: SCC Monitor is processing a BVIR statement. The statement did not contain a BVIR command request. The BVIR command terminates after issuing this message.
Message Level: None
Response: None
MON11701 INVALID BVIR DATA READ
Explanation: SCC Monitor is processing a BVIR statement. The request is made by writing the BVIR command to a scratch tape, closing the output file, and then issuing an open to remount the tape. Once BVIR command processing completes, the mount is satisfied. Monitor then reads the data and validates the original command request which should be returned in the output data. The validation failed.
Message Level: None
Response: Please contact Customer support.
MON11702 REMOTE SYSTEM DID NOT RETURN ALL DATA
Explanation: SCC Monitor is processing a BVIR statement on a remote system. The request is made by requesting that the remote system process the BVIR command then return the output data via TCP/IP. The local Monitor job gets notified of the expected amount of data that should be returned through the TCP/IP link, but the returned data was truncated.
Message Level: E
Response: Please contact Customer support.
MON11703 PROCESSING gridname
Explanation: SCC Monitor is processing a BVIR statement on multiple systems. This message displays the grid name of the current request.
Message Level: I
Response: None
MON11704 FUNCTION NOT AUTHORIZED
Explanation: MONRUN is processing a BVIR statement. However, the Monitor BVIR command is only allowed when the TS7700 product has been started.
Message Level: E
Response: Please contact Customer support.
MON12112 JCL CONVERSION FAILED - RC=rc-rs
Explanation: JCL statements were issued by
MON-JCLQA to process a job stream from a sequential dataset. The JCLQA function calls the operating system converter/interpreter to convert the JCL. However, the converter failed. The message displays the return and reason codes (rc and rs).
Message Level: E
Response: Please contact Customer support.
MON12113 JCL CONVERSION FAILED FOR member - RC=rc-rs
Explanation: JCL statements were issued by MON- JCLQA to process one or more job streams from a partitioned dataset (PDS). The JCLQA function calls the operating system converter/interpreter to convert the JCL in the PDS members. However, the converter failed on the specified member. The message also displays the return and reason codes (rc and rs).
Message Level: E
Response: Please contact Customer support.
MON12114 JCL CHECKS FAILED - RC=rc
Explanation: JCL statements were issued by
MON-JCLQA to process one or more job streams from a partitioned dataset (PDS). After calling the converter/ interpreter to convert the JCL in the PDS members, the validation rules were performed on the JCL member(s). The validation failed, and the return code (rc) for the job is set to the highest message return code encountered in the validation step.
Message Level: E
Response: Please examine the message output for the JCLQA job to determine the reason for the validation failure.
MON12130 RUNNING JCL CHECK ON SYSTEM sysid
Explanation: JCLQA can be used to validate jobs on one or more remote systems. When the product is used to validate a job stream on a remote system (sysid), this message is returned to the calling system for documentation purposes.
Message Level: I
Response: None
MON12131 UNKNOWN SYSTEM
Explanation: JCLQA can be used to validate jobs on one or more remote systems. Each system must be defined on the calling system using a DEFLIST statement to configure the connection to the remote system. The REMOTE parameter located on the JCL statement is used to select the remote system used for validation. However, the requested system was not found.
Message Level: E
Response: For information about configuring and using the remote validation facility, examine “REMOTE SYSTEM TESTING” on page 6-1 in the MON-JCLQA User’s Guide.
MON12140 CARD # - CHANGED "oldtext" TO "newtext”
Explanation: JCLQA modifies text strings during input processing on the job stream, and writes the modified records to a specified DD statement - see the CHANGE keyword parameter on the JCL statement. This message displays the old and new text fields encountered in the JCL along with the card number.
Message Level: I
Response: None
MON12190 USER userid FAILED
Explanation: During JCLQA processing, the caller used the defaults for all validation checks, or requested CHECK(SECURITY) on the JCL statement. JCLQA obtained the current user and group information from the job card on the job stream being validated, or the information specified on the USER parameter for the JCL statement. Note: The user and group fields from the job card has precedence. JCLQA uses the user and group information to make a SAF call to your security product. The SAF call failed validation.
Message Level: E
Response: None. JCLQA is reporting the validation failure.
MON12300 JOB jobname STEP stepname/ procstep
Explanation: After JCLQA performs JCL conversion, the product starts the validation process. This message can be issued multiple times for each job stream. The message is first issued when processing the JOB statement, and no step names will be present. When JCLQA starts processing a job step, the message will be issued with the current STEPNAME from the JCL, and if available the stepname used by the calling PROC.
Message Level: None
Response: None
MON12390 USER user FAILED
Explanation: The USER keyword parameter was specified on the JCLQA test. The application attempted to use the SAF interface on the system running the QA test to construct an ACEE security context. The request failed. Ensure the user and group specified on the USER parameter exist on the target system running the JCLQA test.
Message Level: E
Response: If the userid and group exist on the target system, please contact Customer support.
MON12500 STMT num DDNAME ddname : DSNAME dsname NOT CATALOGED
Explanation: During JCLQA processing, the caller used the defaults for all validation checks, or requested CHECK(CATALOG) on the JCL statement. JCLQA looped through the DD statements in the job stream. Catalog checks were performed for each DD statement using DISP=SHR/OLD/MOD and no UNIT and VOL were available. The CATALOG check failed validation.
Note: If the ORDER statement has been used to simulate multiple jobs, JCLQA uses a catalog cache to simulate catalog updates occurring between jobs. If the ORDER statement has been specified, be aware that a previous job stream may have deleted the catalog entry in the catalog cache.
Message Level: E
Response: None. JCLQA is reporting the validation failure.
MON12501 STMT num DDNAME ddname : DSNAME dsname ALREADY CATALOGED
Explanation: During JCLQA processing, the caller used the defaults for all validation checks, or requested CHECK(CATALOG) on the JCL statement. JCLQA looped through the DD statements in the job stream. Catalog checks were performed for each DD statement using DISP=(NEW,CATALOG) to ensure the dataset is not already cataloged. The CATALOG check failed validation.
Note: If the ORDER statement has been used to simulate multiple jobs, JCLQA uses a catalog cache to simulate catalog updates occurring between jobs. If the ORDER statement has been specified, be aware that a previous job stream may have created the catalog entry in the catalog cache.
Message Level: E
Response: None. JCLQA is reporting the validation failure.
MON12502 STMT num DDNAME ddname : INVALID UNIT NAME unitname
Explanation: During JCLQA processing, the caller used the defaults for all validation checks, or requested CHECK(UNIT) on the JCL statement. JCLQA looped through the DD statements in the job stream. On DD statements that have the UNIT specified, JCLQA first checks the esoteric unit names available on the current system. The product also checks the rules for the DEFLIST DISKUNIT and TAPEUNIT statements used to include or exclude specific unit names during validation. The UNIT check failed validation.
For information about using the DEFLIST statements, examine “Environmental Overrides” on page 4-6 in the MON- JCLQA User’s Guide.
Message Level: E
Response: None. JCLQA is reporting the validation failure.
MON12503 STMT num DDNAME ddname : UNKNOWN VOLUME volser
Explanation: During JCLQA processing, the caller used the defaults for all validation checks, or requested CHECK(VOLSER) on the JCL statement. JCLQA looped through the DD statements in the job stream. On DD statements that have one or more volumes specified, JCLQA first checks the volumes available on the current system. The product also checks the rules for the DEFLIST VOLUME statement used to include or exclude specific volumes during validation. The VOLSER check failed validation.
For information about using the DEFLIST statements, examine “Environmental Overrides” on page 4-6 in the MON- JCLQA User’s Guide.
Message Level: E
Response: None. JCLQA is reporting the validation failure.
MON12504 STMT num DDNAME ddname:VOLUME volser NOT IN UNIT unitname
Explanation: During JCLQA processing, the caller used the defaults for all validation checks, or requested CHECK(VOLSER) on the JCL statement. JCLQA looped through the DD statements in the job stream. On DD statements that have one or more volumes specified, JCLQA first checks the volumes available on the current system. If a unit name is also available on the DD statement, JCLQA then obtains the list of devices assigned to the unit and cross checks the volume(s) specified on the DD statement with the devices assigned to the unit name. The VOLSER check failed validation.
Message Level: E
Response: None. JCLQA is reporting the validation failure.
MON12505 STMT num DDNAME ddname : SMS smstype smsvalue NOT DEFINED
Explanation: During JCLQA processing, the caller used the defaults for all validation checks, or requested CHECK(SMS) on the JCL statement. JCLQA looped through the DD statements in the job stream. On DD statements that have one or more SMS constructs specified (smstype: STORCLAS, MGMTCLAS, DATACLAS) or have the same constructs located in the dataset catalog record, JCLQA validates the specified construct type to determine whether the construct (smsvalue) exists on the current system. The product also checks the rules for DEFLIST STORCLAS, MGMTCLAS, and
DATACLAS statements used to include or exclude specific SMS constructs during validation. The SMS construct check failed validation.
For information about using the DEFLIST statements, examine “Environmental Overrides” on page 4-6 in the MON- JCLQA User’s Guide.
Message Level: E
Response: None. JCLQA is reporting the validation failure.
MON12506 STMT num DDNAME ddname : DSNAME dsname : RACF FAILED
Explanation: During JCLQA processing, the caller used the defaults for all validation checks, or requested CHECK(SECURITY) on the JCL statement. JCLQA looped through the DD statements in the job stream. For non- temporary datasets, JCLQA uses a security environment (ACEE) created for the job stream using the USER parameter specified on the JCL statement.
The product then uses the DISP field on the DD statement to test access permissions using a SAF call. DISP=DELETE checks for ALTER authority. DISP=OLD/MOD checks for UPDATE access and DISP=SHR validates for READ access.
The security check failed validation.
For information about using the DEFLIST statements, examine “Environmental Overrides” on page 4-6 in the MON- JCLQA User’s Guide.
Message Level: E
Response: None. JCLQA is reporting the validation failure.
MON12507 STMT num DDNAME ddname : DSNAME dsname NOT ON volser
Explanation: During JCLQA processing, the caller used the defaults for all validation checks, or requested CHECK(VOLSER) on the JCL statement. JCLQA looped through the DD statements in the job stream. For non- temporary datasets, non-VSAM, non-HFS/ZFS, non- migrated datasets, JCLQA issues an OBTAIN to verify that the dataset is on the volume. The dataset locate attempt failed validation.
Message Level: E
Response: None. JCLQA is reporting the validation failure.
MON12508 STMT num DDNAME ddname : DSNAME dsname ALREADY ON volser
Explanation: During JCLQA processing, the caller used the defaults for all validation checks, or requested CHECK(VOLSER) on the JCL statement. JCLQA looped through the DD statements in the job stream. For a new dataset request on non-temporary, non-VSAM, non- HFS/ZFS, JCLQA issues an OBTAIN to verify that the dataset is not already on the volume. The dataset locate attempt was successful. Since the request was for a new dataset, the validation test fails.
Message Level: E
Response: None. JCLQA is reporting the validation failure.
MON12510 STMT num DEST dest NOT DEFINED
Explanation: During JCLQA processing, the caller used the defaults for all validation checks, or requested CHECK(DEST) on the JCL statement. JCLQA looped through the SYSOUT DD statements in the job stream.
The product first checks the rules for a DEFLIST DEST statement used to include or exclude specific DEST names during validation. JCLQA then makes a subsystem request on the current system to check for the DEST name. The DEST check failed validation.
For information about using the DEFLIST statements, examine “Environmental Overrides” on page 4-6 in the MON- JCLQA User’s Guide.
Message Level: E
Response: None. JCLQA is reporting the validation failure.
MON12520 PDS dsname NOT CATALOGED
Explanation: The caller requested job stream(s) located in a Partitioned Data Set (PDS). However, JCLQA performed a catalog call and was not able to locate the requested dsname.
Message Level: E
Response: None. JCLQA is reporting the validation failure.
MON12521 PDS dsname NOT ON VOLUME volser
Explanation: The caller requested job stream(s) located in a Partitioned Data Set (PDS). However, JCLQA performed a catalog call and was not able to locate the requested dsname on the volume (volser) returned by the catalog request.
Message Level: E
Response: None. JCLQA is reporting the validation failure.
MON12522 PDS dsname IS NOT A PDS
Explanation: The caller requested job stream(s) located in a Partitioned Data Set (PDS). However, JCLQA performed a catalog call to locate the dataset, and then issued an OBTAIN to read the dataset attributes from the volume returned by the catalog request. The requested dataset is not a PDS.
Message Level: E
Response: None. JCLQA is reporting the validation failure.
MON12523 PDS dsname NO READ ACCESS
Explanation: The caller requested job stream(s) located in a Partitioned Data Set (PDS). JCLQA created a security environment (ACEE) for the job stream using the USER parameter specified on the JCL statement and used the SAF security interface to ensure the simulated user has access to the PDS. The security check failed validation.
Message Level: E
Response: None. JCLQA is reporting the validation failure.
MON12540 STMT num DDNAME ddname : DSNAME dsname NOT CATALOGED
Explanation: During JCLQA processing, the caller used the defaults for all validation checks, or requested CHECK(CATALOG) on the JCL statement. JCLQA looped through the DD statements in the job stream. For DD statements with existing datasets (e.g., non-DISP=NEW) using non-specific allocation (e.g., no VOL=SER specified), the product checks the catalog to ensure a catalog record exists. The catalog check failed validation.
Note: If the ORDER statement has been used to simulate multiple jobs, JCLQA uses a catalog cache to simulate catalog updates occurring between jobs. If the ORDER was been specified, be aware that a previous job stream may have deleted the catalog entry in the catalog cache.
Message Level: E
Response: None. JCLQA is reporting the validation failure.
MON12700 DDNAME ddname:MEMBER member NOT IN dsname
Explanation: During JCLQA processing, the caller used the defaults for all validation checks, or requested CHECK(MEMBER) on the JCL statement. JCLQA looped through the DD statements in the job stream. For DD statements using PDS datasets with specified member names, the product attempts to locate the requested member name in the PDS. The member locate attempt failed validation.
Message Level: E
Response: None. JCLQA is reporting the validation failure.
MON12701 PROGRAM pgmname NOT FOUND
Explanation: During JCLQA processing, the caller used the defaults for all validation checks, or requested CHECK(PGM) on the JCL statement. JCLQA performed validation on the program name specified on the EXEC statement. The product ensures that the program exists in LPA, LNKLIST, JOBLIB, or STEPLIB. The program check failed validation.
Message Level: E
Response: None. JCLQA is reporting the validation failure.
MON20100 YOU HAVE nnn DATASETS TO REVIEW
Explanation: This message is produced by the MONNOTFY program in SCC Monitor/Review. This message is delivered to the user during TSO logon and displays the number of data sets in the review list.
Message Level: I
Response: None
MON20101 SELECT OPTION option - MON FROM ISPF PRIMARY MENU
Explanation: This message is produced by the MONNOTFY program in SCC Monitor/Review. This message is delivered to the user during TSO logon and displays the ISPF menu selection option for the user. This message is obtained from the parameter field on the MONNOTFY program.
Message Level: I
Response: None
MON31101 AGGREGATE NAME NOT DEFINED TO SMS
Explanation: This message is produced by the ABC aggregate generation program (ABCAGG). The aggregate name specified by the user does not exist. The ABCAGG program terminates.
Message Level: E
Response: Correct the INPUTAGG parameter to use a valid aggregate name. Note: the name of the aggregate is displayed in a previous message.
MON31103 NO SELECTION DATASETS DEFINED IN AGGREGATE
Explanation: This message is produced by the ABC aggregate generation program (ABCAGG). The aggregate name specified by the user exists, but has no selection data sets defined. The ABCAGG program terminates.
Message Level: E
Response: Select an aggregate name that has selection data sets, or define one or more selection data sets in the aggregate and rerun the ABCAGG program. Note: the name of the aggregate is displayed in a previous message.
MON31301 USER SELECT CARDS FAILED
Explanation: This message is produced by the ABC aggregate generation program (ABCAGG). The user select cards obtained from the SELECT DD statement are not valid.
Message Level: E
Response: Please examine the control cards passed to ABCAGG via the SELECT DD statement. These cards should conform to the selection data set control card syntax.
MON31302 LOAD BALANCE AT #
Explanation: This message is produced by the ABC aggregate generation program (ABCAGG). The user specified multiple output aggregate names which activates load balancing. By default, load balancing splits the input aggregate into multiple output aggregates based on the size of the included data sets. This message displays the target for the total size of the data sets in each output aggregate selection data set.
Message Level: I
Response: None
MON31500 OUTPUT SELECTION DATASET dsname NOT GENERATED BY ABC
Explanation: This message is produced by the ABC aggregate generation program (ABCAGG). The program did not generate the aggregate selection data set. Either the program encountered errors in the validation process, or the user requested a VALIDATE action. If VALIDATE is specified, no selection data set is produced.
Message Level: E
Response: For GENERATE requests, please examine the output for a previous message that explains the validation error.
MON31600 CATALOG INTERFACE ERROR FOR dsname - RC=rc-rs
Explanation: This message is produced by the ABC aggregate generation program (ABCAGG). During validation processing on the selection data set, the program received an error on the catalog request. The data set name, return code (rc) and reason code (rs) are displayed in the message.
Message Level: E
Response: Please contact Customer support.
MON50100 A SYSIN COMMAND CAN ONLY SPAN 12 CARDS
Explanation: This message is produced by the ABC host-based ABARS log management program (ABCLM). The program encountered a command in the SYSIN DD statement that spans more than 12 control statements.
Message Level: E
Response: Condense the command input to less than 12 control statements.
MON50111 LOG PREVIOUSLY ADDED TO PDS: logname
Explanation: This message is produced by the ABC host-based ABARS log management program (ABCLM). The COMPRESS command was issued to compress an ABARS log and write the log to the staging PDS. The log had previously been compressed and added to the staging PDS.
Message Level: W
Response: None
MON50112 QUALIFIER SCAN FAIL ON logname
Explanation: This message is produced by the ABC host-based ABARS log management program (ABCLM). The ABCLM program parses the log name to obtain the aggregate name. The log name does not conform to ABARS standards. The COMPRESS command issued by the user failed.
Message Level: W
Response: Please contact Customer support.
MON50113 MEMNAME TABLE OVERFLOW: num KB MEMBERS
Explanation: This message is produced by the ABC host-based ABARS log management program (ABCLM). An internal table used by the host-based ABCLM program overflowed. The current number of logs that can be processed by ABCLM is displayed in num.
Message Level: A
Response: The table size can be increased with the TABLESIZE parameter. For more information, examine “TABLESIZE” on page 8-43 in the ABC User’s Guide.
MON50120 COMPRESS SUCCESSFUL FOR logname
Explanation: This message is produced by the ABC host-based ABARS log management program (ABCLM). The COMPRESS command was issued to compress an ABARS log and write the log to the staging PDS. The COMPRESS was successful for the logname.
Message Level: None
Response: None
MON50122 STOW FAILED WITH RC=rc
Explanation: This message is produced by the ABC host-based ABARS log management program (ABCLM). The user requested a COMPRESS command, but the STOW macro failed on the request. The STOW return code (rc) is displayed in the message. For more information, examine “The ABC/ LM Batch Interface” on page 8-40 in the ABC User’s Guide.
Message Level: E
Response: Please contact Customer support.
MON50123 QUALIFIER SCAN FAIL ON logname
Explanation: This message is produced by the ABC host-based ABARS log management program (ABCLM). The COMPRESS command parses the log name to obtain the aggregate name. The log name does not conform to ABARS standards. The COMPRESS command issued by the user failed.
Message Level: A
Response: Please contact Customer support.
MON50124 ABCALOG DD OR LOG PARAMETER REQUIRED
Explanation: This message is produced by the ABC host-based ABARS log management program (ABCLM). The COMPRESS command was issued and no log name was specified. Logs can also be specified on the ABCALOG DD statement, but the DD statement was not allocated.
Message Level: E
Response: Use the LOG parameter on the compress command to specify the log name.
MON50125 logname NOT ON VOLUME volser
Explanation: This message is produced by the ABC host-based ABARS log management program (ABCLM). The COMPRESS command was issued, but the logname is no longer found on the volser.
Message Level: E
Response: None
MON50130 EXPAND SUCCESSFUL FOR logname
Explanation: This message is produced by the ABC host-based ABARS log management program (ABCLM). The EXPAND command was issued to extract a member or members from the staging PDS. The EXPAND was successful for the logname.
Message Level: None
Response: None
MON50133 NO MEMBERS MATCHING
Explanation: This message is produced by the ABC host-based ABARS log management program (ABCLM). The EXPAND command was issued to extract a member from the staging PDS. This request is normally performed by the ABC ISPF interface. The requested member (memname) was not found. Note: the member names in the PDS are binary fields. The message displays the EBCDIC representation of the member name. The EXPAND failed.
Message Level: W
Response: Examine the filters specified on the EXPAND command. If you are using the ISPF interface, please contact Customer support.
MON50134 MEMBER NAME NOT FOUND: memname
Explanation: This message is produced by the ABC host-based ABARS log management program (ABCLM). The EXPAND command was issued to extract a member from the staging PDS. This request is normally performed by the ISPF interface. The requested member (memname) was not found. Note: the member names in the PDS are binary fields. The message displays the EBCDIC representation of the member name. The EXPAND failed.
Message Level: A
Response: Please contact Customer support.
MON50135 QUALIFIER SCAN FAIL ON logname
Explanation: This message is produced by the ABC host-based ABARS log management program (ABCLM). The EXPAND and PCUPDTE commands parse the log name to obtain the aggregate name. The log name does not conform to ABARS standards. The EXPAND or PCUPDTE command issued by the user failed.
Message Level: A
Response: Please contact Customer support.
MON50137 SYMBOLIC TABLE OVERFLOW
Explanation: This message is produced by the ABC host-based ABARS log management program (ABCLM). The RECOVER command, but an internal symbol table overflowed. The command cannot complete.
Message Level: E
Response: Please contact Customer support.
MON50140 DELETE SUCCESSFUL FOR n
Explanation: This message is produced by the ABC host-based ABARS log management program (ABCLM). The delete was successful. The number of logs deleted is displayed in the message. For more information, examine “The ABC/ LM Batch Interface” on page 8-40 in the ABC User’s Guide.
Message Level: None
Response: None
MON50141 STOW FAILED WITH RC=rc
Explanation: This message is produced by the ABC host-based ABARS log management program (ABCLM). The user requested a DELETE command, but the STOW macro failed on the delete request. The STOW return code (rc) is displayed in the message. For more information, examine “The ABC/LM Batch Interface” on page 8-40 in the ABC User’s Guide.
Message Level: E
Response: Please contact Customer support.
MON50142 NO LOGS MATCHED DELETE FILTERS
Explanation: This message is produced by the ABC host-based ABARS log management program (ABCLM). The user requested a DELETE command, but the filters requested on the command removed all logs from the candidate list. No ABARS logs were deleted from the staging PDS. For more information, examine “The ABC/LM Batch Interface” on page 8-40 in the ABC User’s Guide.
Message Level: W
Response: Examine the filters specified on the delete command.
MON50160 JCL TABLE OVERFLOW - MAXIMUM nnnn CARDS
Explanation: This message is produced by the ABC host-based ABARS log management program (ABCLM). The user requested an ARECOVER command, but the JCL template used for the recovery JCL overran the available buffer.
Message Level: E
Response: Please contact Customer support.