UPSTREAM Messages

This section contains a full list of all the messages that can be issued by UPSTREAM, and also explains where those messages are issued. Most of the messages listed in this chapter come from the UPSTREAM started task, but some of them may also be issued by UPSTREAM utility programs, such as USTBATCH.

Reporting a Problem#

Should you have any questions regarding the installation, implementation, or use of the UPSTREAM product, please feel free to contact BMC Support.

In the event that you have any difficulty with UPSTREAM, please retain all the error information that you can gather, including:

• UPSTREAM USTLOG file. (See The LOG File (USTLOG).)

• z/OS Console Messages. (See z/OS Console Messages.)

• UPSTREAM USTSUMM file. (See The SUMMARY File (USTSUMM).)

• Any relevant JOBLOG or SYSLOG messages

• UPSTREAM Client logs. (See the UPSTREAM Client Guide)

• Any relevant UPSTREAM configuration information. (See UPSTREAM Configurator.)

Once you have all the information, please contact BMC Support as soon as possible after the error has occurred. We make every effort to resolve the difficulty in the shortest possible time.

The LOG File (USTLOG)#

UPSTREAM maintains a log file (DD statement USTLOG) to record status information and error conditions. This log file is usually directed to SYSOUT and are printed or held when the UPSTREAM started task terminates (depending on the SYSOUT class chosen).

The UPSTREAM log file is one of the primary sources of information if a problem occurs in an UPSTREAM operation. A sample listing from a USTLOG log file is shown below. Each line in the listing contains the following:

• The UPSTREAM message number
  
• The time the message was logged
  
• The UPSTREAM profile name (or LU name) that generated the message
  
• The message text
  

In the sample log on the previous page we can see:

• UPSTREAM was started at 08:51.
• The USTMAINT utility was automatically started to clean up the UPSTREAM repository files.
• The TCP/IP and VTAM APPC interfaces were initialized.
  
• A full merge backup (to sequential tape) was initiated at 09:18 by an Client at TCP/IP address 82324B0B (equivalent to 130.50.75.11) using the backup profile name MERGE1. The backup completed at 09:20 and UPSTREAM has logged the backup completion statistics.
  
• A USTBATCH-initiated backup job was started at 01:03. It is a backup to sequential disk from the Client at VTAM LU T550F6AA using the backup profile name WS0443DL. The z/OS backup data set name has been logged. During the backup process, the Client notified UPSTREAM of four skipped files. The backup completed (with the errors logged) at 01:04:46.
  
• A mainframe-initiated job to backup Client at LU T550F6ZZ was submitted and began execution at 03:39:28. UPSTREAM received an error indication attempting to allocate the LU 6.2 session and conversation to the target LU. The error indicates that the LU was not available at the time the request was made. The submitted batch job was notified and the backup terminated. In this case, had there been a “MAXRETRY” value specified in the USTBATCH job input stream, UPSTREAM would have delayed and then retried the conversation allocation again.
  

z/OS Console Messages

Some UPSTREAM messages, particularly those that indicate initialization errors or other conditions of interest to the system operator, are written to the z/OS system console as well as to USTLOG.

These messages are identified in the message tables in UPSTREAM Message Reference by an asterisk “*” after the message ID.

If the WTOCOMP configuration option has been set, then all “backup started” and “backup completed” messages are written to the z/OS system console as well as to USTLOG.

The SUMMARY File (USTSUMM)#

UPSTREAM also optionally creates a summary file that is enabled by the presence of a USTSUMM DD statement in the UPSTREAM startup PROC. This summary log file, which contains single-line descriptions of each operation performed by UPSTREAM, provides a quick and effective reference to all UPSTREAM activity.

USTSUMM information is usually directed to SYSOUT and is printed or held when the UPSTREAM started task terminates (depending on the SYSOUT class chosen).

Here is a short example of a UPSTREAM USTSUMM summary log. Note that the final entry (operation SHUTDOWN), shows the start/stop time, total elapsed time and CPU (TCB) time used by this execution of UPSTREAM. The # FILES value is the total number of operations that UPSTREAM handled, and COMPCODE is the highest completion code of any operation. See “completion codes” below (20 if any operation abended).

• START DATE/TIME - The date and time that the indicated operation started. For backups, this is also the “version-date” of the backup.
  
• END-TIME - The time that the operation ended. The report is sorted in order of end-time.
  
• PROFILE - The UPSTREAM profile name associated with the operation. For backup inquiries and profile operations, this may be a mask, as in the “M*” profile. For utility operations, such as USTMAINT, this is the utility name.
  
• LUNAME - The TCP/IP network address (in hex) or the VTAM LUNAME of the Client associated with the operation. For utility operations, such as USTMAINT, this is the utility name.• USERID - The security userid entered at the Client, if any. It may be blank if SECLVL=0 is in effect.
• OPERATION - Indicates the operation requested, such as BACKUP, RESTORE, INQUIREV (inquire versions), REMOVE B (remove backups).
  
• TYPE - For some operations, this indicates the type of operation, such as “INCR” for merge incremental backup, “MERG” for merge full backup, and “TAPE” or “DISK” for restores.
  
• COMPCODE - Indicates the completion code. (See Section “UPSTREAM Completion Codes”.)
  
• TIME/CPU - The elapsed time (in minutes and tenths) and the CPU time (in seconds and thousandths) TCB time only.
  
• # FILES - For backups and restores, the number of files processed. For other functions, this value indicates the relevant quantity (e.g., for an INQUIREV it is the number of versions).
  
• PC BLOCKS - The number of transmission records actually sent to/from the Client.
  
• BYTES - The total amount of data (in kilobytes) processed for this request.
  
• PHYBLKS - The total number of blocks read from or written to a backup for this request. For MERGE backups, it is the total blocks read from all sources, including the Client, previous incremental backups, and the previous full backup. This value is the physical blocks on the backup medium, which may differ from the records sent to/from the Client.
  

Managing the USTLOG and USTSUMM Logs#

UPSTREAM console commands can be used to manage the USTLOG and USTSUMM log files. In summary:

• The FLUSHLOG command closes and reopens the log so that the most recent messages are visible.
  
• If the log files are on disk, the SWITCHLOG command switches between the primary log (USTLOG and USTSUMM) and an alternate log (USTLOG2 and USTSUMM2) so that the inactive log file can be read or copied for reporting purposes without shutting down UPSTREAM.
  

UPSTREAM Completion Codes

There is a completion (return) code associated with every sub-task that runs under the main UPSTREAM started task. These codes are displayed in the USTSUMM summary file, and also in many reports produced by USTRPORT (see Chapter 21 “Reporting with USTRPORT”).

The completion code of the UPSTREAM main task, at shutdown, is the highest numeric completion code encountered for any sub-task. UPSTREAM batch utility and reporting programs also set one of the following numeric completion codes.

The possible values are:

• SUSPEND - Backup was suspended.
  
• CANCEL - Canceled by operator.
  
• Ssss - System abend sss.
  
• Uuuuu - User abend uuuu.
  
• 0 - Normal completion.
  
• 4 - Completed with warnings.
  
• 8 - Terminated with error.
  
• 12 - Terminated with severe errors.
  
• 16 - Terminated by operator.
  
• 20 - Terminated by abend.
  

UPSTREAM Message Reference

UPSTREAM messages are in the format USTnnns, where “nnn” is a 3-digit message number, and “s” is one of the following severity codes:

• E - Error message

• W - Warning messages

• T - Internal trace messages (not documented in this manual)

• Blank - Informational messages (so the others stand out)

In general, the messages are posted to the UPSTREAM log (USTLOG). Messages with an asterisk “*” following the message ID may also be written to the system console. For messages that indicate an error condition: if you are unable to resolve the problem, please save all documentation (usually the UPSTREAM log and the system SYSLOG for the time of the problem) and contact BMC Support for assistance.

All UPSTREAM messages are documented in the tables below, and are divided into the following sections:

UST001-UST299 - see UPSTREAM Started Task Messages

UST300-UST399 - see UPSTREAM Configurator Messages

UST400-UST499 - see USTREGEN and USTRPORT Utility Messages

UST500-UST599 - see USTMAINT and USTREORG Utility Messages

UST600-UST699 - see USTMIGRT, USTVAULT, and USTMERGE Messages

UST700-UST799 - see USTBATCH Utility Messages

UST800-UST810 - see USTSCHED Utility Messages

UPSTREAM Started Task Messages

UST001 TO DSN: backup file data set name APPENDING TO PREVIOUS BACKUP VOL=xxxxxx [PC FILE=pcfilename]

Reason: This informational message is issued by the sequential backup processes to log the name of the sequential data set dynamically allocated to contain the backup data for this version. The optional text APPENDING TO PREVIOUS BACKUP indicates that the backup is being added to an existing backup data set. The VOL field indicates the first volume serial that the backup data set has been placed on. For file transfers only, the PC FILE= specifies the name of the Client file that was transferred.

Action: None.

UST002E* OPEN clustername CLUSTER FAILED COMP=rrrr CODE=cccc -- TERMINATING

Reason: The z/OS Storage Server Main task was unable to open the indicated “clustername”, either “CATALOG”, “FILE-INFO”, or “FILE-DATA”. UPSTREAM terminates. “rrrr” is the return code in R15 after the open, and “cccc” is the ACBERFLG error code.

Action: Verify your JCL specification for the “USTCATLG”, “USTFILEI” or “USTFILEC” DD statement. Refer to the IBM VSAM Macro Reference or Macro Instructions for Data Sets manual (depending on the level of your operating system) to understand the OPEN error codes reported.

UST003E* VTAM SETLOGON REQUEST FAILED - SNA DISABLED

Reason: The z/OS Storage Server Main task received a non-zero return code from a VTAM “SETLOGON START” request to begin queuing sessions. This is most likely a temporary VTAM problem. UPSTREAM disables SNA (VTAM) communications; if TCP/IP communications are enabled, it continues, otherwise it terminates.

Action: Verify the VTAM “APPL” and “MODE TABLE” definitions were correctly specified and installed. Stop and restart the UPSTREAM Started Task to attempt to enable VTAM communications again.

UST004E TCP/IP ERROR REQUEST=xx COMP=ccccc reason

Reason: A TCP/IP error during processing “xx” is an internal UPSTREAM request code. “ccccc” is the TCP/IP completion code from register 15 in decimal, and reason is a brief explanation of the error. Common error codes include:

 Code – Description

0042 – PROTOCOL NOT AVAILABLE

Port in use or improper PORT statement in the TCP/IP profile. Can also occur after z/OS Storage Server abend if UPSTREAM is restarted too quickly.

0054 – CONNECTION RESET BY PEER

The connection to the Client was closed by the Client.

0060 – CONNECTION TIMED OUT

UPSTREAM Client not active or wrong IP address specified.

0061 – CONNECTION REFUSED

Wong Client port number specified or UPSTREAM PC not active on Client.

Action: Determine the cause, correct it, and repeat the operation (or restart UPSTREAM).

UST005 function COMPLETED SUCCESSFULLY

Reason: A management function requested from a Client has completed successfully. “function” may be UPDATE OF PROFILE, REFRESH REQUEST, or LOGIN REQUEST.

Action: None.

UST005E function COMPLETED WITH ERRORS - REASON=reason

Reason: A management function from a Client has completed abnormally. “reason”, if present, explains the error.

Action: Verify your JCL specification for the “USTCONFG” DD statement. Review the most recent Configurator output for possible errors which may have made the file unusable.

UST006E OPEN CONFIGURATION-FILE FAILED -- TERMINATING

Reason: The z/OS Storage Server main task, “USTMAIN”, was unable to open the Configuration File, “USTCONFG” DD statement. The UPSTREAM started task terminates.

Action: Determine the cause, correct it, and repeat the request. If necessary, contact BMC Support for assistance.

UST007E OPEN FOR VTAM ACB FAILED -- ACBERFLG=nn - reason

Reason: The z/OS Storage Server main task was unable to open the VTAM “ACB”. UPSTREAM terminates. “reason” indicates the meaning of the ACBERFLG error code.

Action: For certain errors, UPSTREAM retries the OPEN once a minute for up to 5 minutes, in case the error is due to VTAM not being fully initialized. In this case, the message is printed every minute until the OPEN is successful or the 5th attempt fails (which causes UPSTREAM to terminate). If UPSTREAM does fail, correct the error, if possible. Review the VTAM “APPL” definition for z/OS Storage Server to be sure the VTAM “APPLID” (or “ACBNAME” if used) matches the “APPLID=” specification in your Configuration file “MAIN” record. Be sure the VTAM application IDs for UPSTREAM are active.

UST007W OPEN FOR VTAM ACB BYPASSED

Reason: The VTAM ACB was not opened because you specified APPLID=NONE in the z/OS Storage Server configuration. Only TCP/IP connections are supported and note that mainframe-initiated operations via USTBATCH are not possible.

Action: None, if this is as desired. Otherwise, reconfigure the UPSTREAM MAIN options to specify a valid ACBNAME.

UST007W OPEN FOR TCP/IP OR TCPACCESS BYPASSED

Reason: The TCP/IP connection was not established because you specified TCPIP=NONE in the z/OS Storage Server MAIN options configuration, or because the required TCP/IP interface module was not found (probably because TCP/IP is not installed on your system). Only VTAM APPC connections are supported.

Action: None, if this is as desired. Otherwise, reconfigure the UPSTREAM MAIN options to specify a valid TCP/IP Address space name (TCPNAME MAIN options parameter).

UST008 UPSTREAM STOP ACCEPTED -- SHUTDOWN IN PROGRESS

Reason: A P UPSTREAM console command has been entered, requesting an orderly shutdown of the UPSTREAM stated task.

Action: None.

UST009 SESSION STARTED TO luname BIND=bindimage x

Reason: This is an information message only. It is logged only for VTAM LUs at the time the session is initiated to the Client. “bindimage” is the first 16 bytes of the SNA bind, in hex, used for this session. “x” is “L” for dependent LUs and “S” for independent LUs. If the “WTOCOMP” option was selected in the UPSTREAM configuration “MAIN” record, this message is also written to the system log (SYSLOG).

Action: None.

UST010E UNABLE TO ENQUEUE CONTROL FILE

Reason: The UPSTREAM online task detected that a UPSTREAM utility function that updates the UPSTREAM repository files is running. The two cannot execute together.

Action: Wait until the utility job terminates, then start the online task again.

UST010W INQUIRE-FILES MAY NOT BE IN ORDER DUE TO INSUFFICIENT MEMORY

Reason: An inquire-files request that required sorting of UPSTREAM records, such as request against a MERGE backup profile, failed due to insufficient above-the-line storage for the sort. This could be due to multiple such requests running concurrently. The displayed files may not be in the correct order.

Action: If you need the files properly sorted, try the request again. If these requests fail frequently, you may have to increase the REGION= value in the z/OS Storage Server startup JCL (values over 32M increase the above-the-line region size).

UST011E RESTORE-FILES TERMINATED DUE TO INSUFFICIENT MEMORY

Reason: A restore request that required sorting of UPSTREAM records, such as a “restore-to-full” or “restore-as-of” from a MERGE backup, failed due to insufficient above-the-line storage for the sort. This could be due to multiple such requests running concurrently.

Action: Try the request again later. If it still fails, you may have to increase the REGION= value in the z/OS Storage Server startup JCL (values over 32M increase the above-the-line region size).

UST012E UPSTREAM COMMAND NOT RECOGNIZED - command

Reason: A command issued from the system console to z/OS Storage Server was not STOP(P) or MODIFY(F). The command received is shown.

Action: See UPSTREAM Operation for valid commands for UPSTREAM.

UST012E MODIFY REQUEST NOT RECOGNIZED REQ: request

Reason: An z/OS MODIFY(F) command issued from the system console was not recognized by z/OS Storage Server. The invalid request is shown.

Action: Recall the command and check the spelling and syntax. See UPSTREAM Operation for the valid commands for UPSTREAM.

UST013* (PART OF STATUS DISPLAY GROUP)

Reason: This message is issued as part of a message group when a “STATUS” inquiry request is issued from the system console.

Action: None.

UST014* (PART OF STATUS DISPLAY GROUP)

Reason: This message is issued as part of a message group when a “STATUS” inquiry request is issued from the system console.

Action: None.

UST015* (PART OF STATUS DISPLAY GROUP)

Reason: This message is issued as part of a message group when a “STATUS” inquiry request is issued from the system console.

Action: None.

UST016* NO TASKS CURRENTLY ACTIVE Vn.n.n

Reason: This message is issued as part of a message group when a “STATUS” inquiry request is issued from the system console.

Action: None.

UST017E APPCCMD RCVFMH5 REQUEST FAILED

Reason: The z/OS Storage Server main task received an error indication during an “APPC” request to receive the SNA Function Management Header (FMH) type-5 for the conversation allocation.

Action: VTAM error codes are reported in a following message. Consult IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST018E START CONVERSATION RECEIVE FAILED

Reason: The z/OS Storage Server sub-task received an error indication while trying to start a conversation with an UPSTREAM Client.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST019E INITIAL RECEIVE NOT START-CONVERSATION

Reason: The z/OS Storage Server sub-task received an unexpected data type during its conversation initialization.

Action: This is an internal error. Retain the error log and contact BMC Support for assistance.

UST020E PROFILE NAME FAILED CONFIGURATION VERIFICATION

Reason: The z/OS Storage Server sub-task was unable to validate the Client Profile Name received for this conversation.

Action: Verify that the Profile Name sent by the Client is correct and was included in the Configuration file that last time the z/OS Storage Server Configurator was run.

Note: This error may also be posted if the GLOBAL profile has been deleted. Certain internal UPSTREAM functions utilize this profile and post the error when they are called if it is missing.

UST021 COMM. PERFORMANCE TEST (WORKSTATION SEND) REQUESTED

Reason: An UPSTREAM Client has requested the communication performance (WS send) test. This message is informational only.

Action: None.

UST022E RECEIVED STRUCTURE NOT RECOGNIZED

Reason: The z/OS Storage Server sub-task received a data or control structure it did not recognize.

Action: This is an internal error. Retain the error log and contact BMC Support for assistance.

UST023E COMM. PERFORMANCE TEST (M/F SEND) COMPLETED n BYTES PER SECOND

Reason: The communications performance test (M/F send) logic has completed the request and achieved a data rate of “n” bytes per second. This message is informational only.

Action: None.

UST024E SEND FOR BACKUP-STARTED FAILED

Reason: The z/OS Storage Server backup process received a communication error indication trying to send control information to the Client.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST025E RECEIVE ERROR

Reason: The z/OS Storage Server received a communication error indication while receiving data or control information from the Client.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST026E RECEIVED DATA xxxxxxxx UNRECOGNIZED -- EXPECTED FILE-INFORMATION

Reason: The z/OS Storage Server Backup process received an unrecognized data or control structure.

Action: This is an internal error. Retain the error log and contact BMC Support for assistance.

UST027E RECEIVED DATA xxxxxxxx UNRECOGNIZED -- EXPECTED FILE-DATA

Reason: The z/OS Storage Server backup process received an unexpected data or control structure.

Action: This is an internal error. Retain the error log and contact BMC Support for assistance.

UST028E UNEXPECTED DEALLOCATE RECEIVED

Reason: The z/OS Storage Server backup process received an unexpected APPC DEALLOCATE-CONVERSATION request. This is most likely the result of an error having occurred on the Client.

Action: Review the UPSTREAM Client log file for the error.

UST029 COMM. PERFORMANCE TEST (M/F SEND) REQUESTED

Reason: The communications performance test (M/F send) requested by a Client has begun. Message UST023E is logged at its completion. This message is informational only.

Action: None.

UST030E REQUESTED DATA BLOCK-SIZE LESS THAN 10 BYTES

Reason: The communications performance test (M/F send) requested by a Client has found that the requested block size for the test transmission was less than 10 bytes.

Action: Reissue the request from the Client specifying a valid test block size.

UST031E COMMUNICATION RECORD ERROR OR FDRPAS NOT SUPPORTED

Reason: This distribution of UPSTREAM does not support the FDRPAS functionality or an error was encountered in the handshake with the remote connection.

Action: Verify that you are licensed for FDRPAS and using the supplied distribution or contact BMC Support for assistance.

UST032E REQUESTED SEND-COUNT INVALID

Reason: The communications performance test (M/F send) requested by a Client has found that the requested data block send count was invalid.

Action: Reissue the request from the Client specifying a valid send count.

UST033E APPC ERROR ON SEND OF DATA BLOCK

Reason: The communications performance test (M/F send) requested by a Client has received a communication error indication after issuing a SEND-DATA request.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance. Retry the communications performance test.

UST034E ERROR ON CONFIRM TO WORKSTATION

Reason: The communications performance test (M/F send) requested by a Client has received a communication error indication after issuing a CONFIRM request at the completion of the test.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST035 UPSTREAM Vn.n.n INITIALIZATION COMPLETE - CONFIG=member APPLID=applid SECLVL=n

Reason: This is an informational message only. It is issued by the z/OS Storage Server main task when its initialization process has completed. If shows the configuration member name used (if the configuration data set is a PDS), the VTAM application ID used, and the SECLVL in effect.

Action: None.

UST036E CONFIGURATION FILE FORMAT ERROR -- TERMINATING

Reason: During loading the Configuration Table, the z/OS Storage Server main task found the file contained an error. UPSTREAM terminates with a non-zero return code.

Action: Review the most recent output from the z/OS Storage Server Configurator program for errors. Correct them, rerun the Configurator, and restart the task.

UST037E ATTACH FOR SUBTASK FAILED -- SESSION DENIED LU=luname

Reason: The z/OS Storage Server main task was unable to attach a processing sub-task for the indicated logical unit. This may be a result of a storage shortage.

Action: Try increasing the REGION size for the UPSTREAM task, if the problem is memory related and retry the operation.

UST038E VTAM error return codes and sense information

Reason: This message is written by an error processing routine used for VTAM APPC and control-type requests. It contains the VTAM error codes from the “RPL” control block. In most cases it also contains a brief text description of the error, to save you the effort of trying to interpret the error codes manually from VTAM manuals. This message is usually written to the log along with other messages indicating the location of the error.

Action: See the “Action” for the accompanying message.

UST039E PROFILE NAME IS INVALID

Reason: The profile name received from a Client had a length greater than 8.

Action: Insure that the specified profile name is 8 characters or less. Profile names are limited to 1 - 8 alpha, numeric, and national characters. If you are unable to determine the cause of the error, retain the error log and contact BMC Support for assistance.

UST040E LU=luname USERID IS MISSING OR INVALID

Reason: The userid received from a Client had a length of 0 or greater than 8.

Action: This error message may be issued if you have specified a non-zero security level parameter (SECLVL=) in the z/OS Storage Server configuration and the request being processed specified no USERID value. Otherwise, this is internal error; Retain the error log and contact BMC Support for assistance.

UST041E LU=luname PASSWORD IS MISSING OR INVALID

Reason: The password received from a Client had a length of 0 or greater than 8.

Action: This error message may be issued if you have specified a non-zero security level parameter (SECLVL=) in the z/OS Storage Server configuration and no password was specified. Otherwise, this is internal error; Retain the error log and contact BMC Support for assistance.

UST042E RECEIVE-DATA ERROR

Reason: The z/OS Storage Server sub-task received a communication error indication during a RECEIVE-DATA request.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST043E UNEXPECTED DEALLOCATE RECEIVED

Reason: The z/OS Storage Server sub-task received an unexpected DEALLOCATE-CONVERSATION indication. This is most likely the result of an error condition on the UPSTREAM Client.

Action: Review the error log on the UPSTREAM Client to resolve the problem.

UST046E RECEIVE BACKUP-DESC REPEATED STRUCTURE FAILED

Reason: The z/OS Storage Server backup process received an error indication during a RECEIVE-DATA request.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST047E RECEIVE FOR FILE-INFORMATION FAILED

Reason: The z/OS Storage Server backup process received a communication error indication during an RECEIVE-DATA request.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST048E MAIN SUBEND UNABLE TO LOCATE ATB FOR TCB=tcbaddress

Reason: This is an internal error.

Action: Retain all error information and contact BMC Support for assistance.

UST049E SEND CONFIRMED-RESPONSE FAILED

Reason: The z/OS Storage Server backup process received a communication error indication attempting to send an CONFIRMED response.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST050 event information reported from workstation

Reason: This message contains text sent from the Client. It is usually used to report an error condition at the Client.

Action: Review the message and consult the UPSTREAM Client Guide to interpret the error, or contact BMC Support for assistance.

UST051E general VSAM error diagnostic information

Reason: This message is logged by the VSAM error diagnosis routine. It contains specific error codes from the VSAM “RPL” control block. If possible, the message also contains a brief text description of the error. This message is accompanied by others, indicating the location of the error.

Action: If necessary, refer to the IBM VSAM Macro Reference or Macro Instructions for Data Sets manual (depending on the level of your operating system) to understand the error codes reported. Correct the error or contact BMC Support for assistance.

UST052E COMM ERROR ON RECEIVE DATA REQUEST

Reason: The communications performance test (PC send) requested by a Client has received an error indication after issuing a RECEIVE request.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST053E RECEIVE FOR RESTORE-DESC REPEATED STRUCTURE FAILED

Reason: The z/OS Storage Server restore process received a communication error indication during a RECEIVE-DATA request.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST054E SEND OF BACKUP-DESCRIPTION FAILED

Reason: The z/OS Storage Server restore process received a communication error indication during an SEND-DATA request.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST054E SEND OF PROFILE-DESCRIPTION FAILED - reason

Reason: An UPSTREAM Client requested display or update of a profile definition, but the request failed for the reason given.

Action: If possible, correct the error and resubmit the request. If necessary, contact BMC Support for assistance.

UST055 COMM. PERFORMANCE TEST (WORKSTATION SEND) COMPLETED n BYTES PER SECOND

Reason: The communications performance test (PC send) requested by a Client has completed and achieved a data rate of “n” bytes per second. This message is informational only.

Action: None.

UST056W NO CATALOG RECORD FOUND FOR THIS PROFILE NAME

Reason:This message is issued by the z/OS Storage Server restore process. While searching for a Catalog Version record for the supplied Client Profile Name, no record was found. The specified Profile Name has no versions currently recorded. There may have been no prior backup done specifying this name.

Action: Review the available backups and select the proper one. If you need assistance, contact BMC Support.

UST057E NO F-RECORDS FOUND FOR THIS FILENAME

Reason:During the Restore process, z/OS Storage Server was unable to locate a record for the requested filename. The requested filename may not have been backed up in a prior Backup request.

Action:Review the available backups and select the proper one. If you need assistance, contact BMC Support.

UST058E APPC SEND OF F-RECORD FAILED

Reason: The z/OS Storage Server restore process received a communication error indication after requesting an SEND-DATA for control information to the Client.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST0059 SEND OF FILE-DATA RECORD FAILED

Reason:The z/OS Storage Server restore logic received a communication error indication after a SEND-DATA request to send File Data to the Client.

Action:Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST060E UNEXPECTED DEALLOCATE RECEIVED FROM WORKSTATION

Reason: The communications performance test (WS send) requested by a Client has received an unexpected conversation de-allocation indication from the Client.

Action:Use these error codes to determine the cause of the error and correct it. Retry the communications performance test. Review the Client log to determine the cause of the APPC DEALLOCATE request.

UST061E DEALLOCATE-CONFIRM REQUEST FAILED

Reason:The z/OS Storage Server Restore logic attempted to normally terminate the conversation by issuing an DEALLOCATE-CONFIRM request but got a communication error indication.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST062E UNEXPECTED DEALLOCATE RECEIVED FROM WORKSTATION

Reason: The z/OS Storage Server restore logic received an unexpected DEALLOCATE-CONVERSATION request from the Client. This is most likely the result of an error condition having occurred on the Client.

Action:Review the Client error log to determine the reason the DEALLOCATE request was sent. Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST063E* UNABLE TO LOAD CONFIG TABLE -- ENQ FAILED

Reason: The z/OS Storage Server main task was unable to acquire an exclusive ENQ in order to load the Configuration Table.

Action:Ensure that you were not trying to start more than one copy of the UPSTREAM main task. If not, this may be an internal error. Retain all error information and contact BMC Support for assistance.

UST064E* CONFIGURATION TABLE LOAD FAILED - TERMINATING

Reason:The z/OS Storage Server main task was unable to load the Configuration Table, and is terminating as a result.

Action:This is an internal error. Retain all error information and contact BMC Support for assistance.

UST065E INQUIRE-VERSIONS INVALID FLAG BYTE FOUND

Reason: The z/OS Storage Server Version Inquiry logic detected an invalid value in an internal structure.

Action: This is an internal error. Retain all error information and contact BMC Support for assistance.

UST066E INVALID value IN INQUIRE-FILES REQUEST

Reason:The z/OS Storage Server Version Inquiry logic detected an invalid value in an internal structure. “value” is either “LENGTH VALUE” or “DIRECTORY STRUCTURE”.

Action:This is an internal error. Retain all error information and contact BMC Support for assistance.

UST067E SEND OF BACKUP-DESC FAILED -- VERSIONDATE

Reason:The z/OS Storage Server Version Inquiry logic received a communication error indication after issuing an APPC SEND-DATA request.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST068E SEND OF BACKUP-DESC FAILED -- ALL VERSIONS

Reason: The z/OS Storage Server Version Inquiry logic received a communication error indication after issuing an SEND-DATA request.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST069E SEND OF BACKUP-DESC FAILED -- LATESTVERSION

Reason: The z/OS Storage Server Version Inquiry logic received a communication error indication after issuing an SEND-DATA request.

Action:Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST070W NO RECORDS FOUND FOR INQUIRE-VERSIONS REQUEST

Reason: The z/OS Storage Server Version Inquiry logic found no records for the inquiry request.

Action: Verify the Profile Name and the VERSIONDATE requested are valid. Verify that a successful Backup had been performed previously for this Profile.

UST071E SEND FOR FILE-INFORMATION RECORD FAILED

Reason: The z/OS Storage Server File Inquiry logic received a communication error indication after issuing a SEND-DATA for an internal control structure.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST072W NO FILES FOUND FOR VERDATE=versiondate PATH=fileid

Reason: The z/OS Storage Server File Inquiry logic was unable to find a match for the request.

Action: Verify the requested Profile Name and VERSIONDATE are correct and retry the operation.

UST073E ATTNEXIT FOUND function IN PROGRESS -- REJECTED

Reason:The requested conversation initiation was denied due to a z/OS Storage Server having a status that prevents new Client functions from starting. If “function” is SHUTDOWN, then UPSTREAM received a system console STOP request and is waiting for all currently active sub-tasks to terminate. If it is REORG, then one or more of the UPSTREAM files is being reorganized in response to a console REORG request.

Action: The Client can retry the request after z/OS Storage Server is restarted or after the REORG completes.

UST074E ATTNEXIT FMH5 CONV TYPE NOT BASIC - REJECTED

Reason:The z/OS Storage Server main task found an invalid value in the received Function Management Header (FMH) type-5 from the Client.

Action: This is an internal error. Retain all error information and contact BMC Support for assistance.

UST075E ATTNEXIT FMH5 SYNC LEVEL NOT CONFIRM -- REJECTED

Reason: The z/OS Storage Server main task found an invalid value in the received Function Management Header (FMH) type-5 from the Client.

Action: This is an internal error. Retain all error information and contact BMC Support for assistance.

UST076E ROLLOFF -- NO C-RECORDS FOUND FOR ROLLOFF

Reason: This is an internal error.

Action:Retain all error information and contact BMC Support for assistance.

UST077E ROLLOFF -- VSAM ERROR

Reason:The z/OS Storage Server Backup “Version Rolloff” logic encountered an error during a VSAM I/O request. This message is accompanied by message UST051E containing the VSAM error codes as reported.

Action:Retain all error information and contact BMC Support.

UST078 BACKUP STATISTICS (TOTALS RECEIVED):

Reason: This is the first of a three message group. Statistics are logged to the UPSTREAM log file for each backup performed. This message is accompanied by messages UST079 and UST080 containing the statistics for the backup just ended.

Action: None.

UST079 VERSIONDATE: vvvvvvvvvvvv; nnnnnnnnnnnnnn FILES function mmmmmmmmm DIRECTORIES function

Reason:If “function” is RECEIVED, this is the second message of a three-message group (including UST078 and UST080); it shows the “versiondate” used to store the files being backed up as well as the number of files and the number of subdirectories backed up. If “function” is RESTORED, the message is issued with UST080 to show the number of files and subdirectories sent to the Client from the indicated “versiondate” (the Client may not restore all of them).

Action: None.

UST080 nnnnnnnnnnnn DATA-BLOCKS; mmmmmmmmmmm DATA-BYTES RECEIVED

Reason:This is the last of a multi-message group. This message is preceded by messages UST078 and UST079 containing the statistics for the function just ended. This message contains the total count of transmission data blocks and bytes send to or from the UPSTREAM Client.

Action: None.

UST081W RESTORE: VERSION NOT FOUND FOR SPECIFIC VERSIONDATE=versiondate

Reason: During z/OS Storage Server Restore processing, the logic was unable to locate a Repository Catalog record for the specific version requested by the End User.

Action: Use the “INQUIRE VERSIONS” function of the Restore panel to locate the version you are attempting to Restore. If the version is shown, this is an internal error. Otherwise, select a version listed, and retry the Restore request.

UST082E RESTART: MODCB FOR RPL-C FAILED

Reason:During a Restarted Backup, the z/OS Storage Server logic received an error indication from a VSAM “MODCB” request. This message is accompanied by message UST051E containing the VSAM error codes as reported.

Action:Refer to the IBM VSAM Macro Reference or Macro Instructions for Data Sets manual (depending on the level of your operating system) to understand the error codes reported.

UST083E UNABLE TO RESTART BACKUP -- reason

Reason: During a Restarted Backup, z/OS Storage Server could not restart the backup for the reason given. This generally occurs when a Backup is interrupted for any reason prior to z/OS Storage Server having received sufficient data to consider the Backup committed, i.e., the interrupt occurred too early in the Backup process to retain the Backup information.

Action: You need to rerun the Backup -- it is not re-startable.

UST084E RESTART: SEND OF BACKUP-DESC FAILED

Reason: During a Restarted Backup, z/OS Storage Server received a communications error indication, having issued a SEND-DATA request.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST085W WARNING -- FILES BACK TO FULL IGNORED FOR NON-MERGE

Reason: An UPSTREAM Client user requested a “back-to-full” restore, but the backups to be restored were not MERGE backups, so the option was ignored. The restore proceeds.

Action: None.

UST086E COMM RECEIVE REQUEST TIMEOUT -- function TERMINATED

Reason: A function in progress is terminated after a period of ten minutes if no data is received from the Client.

Action:Review the UPSTREAM log on the Client to determine the cause of the timeout

UST087E* LU=luname USERID/PASSWORD OR PROFILE VALIDATION UNSUCCESSFUL

Reason:The SAF (security) call to verify the userid and password or profile name provided by the Client user (as requested by SECLVL=1 or 2 in the UPSTREAM Configuration) has failed. The user may have specified the wrong userid, password or profile name.

Action: Verify the specified userid, password and profile are correct and are defined correctly to your security system.

UST093W RESTORE: CATALOG ARCHIVE-RECORD NOT FOUND

Reason: During z/OS Storage Server restore processing for a specified “versiondate”, no records were found.

Action:Use the “Inquire Versions” request on the Restore menu to list all available versions, to verify your request was correct. If your request was correct, this is an internal error; retain all error information and contact BMC Support for assistance.

UST094E OPEN FOR ARCHOLD DATASET FAILED

Reason: During z/OS Storage Server restore processing, an error indication was received trying to open the Archive data set.

Action: Refer to your system log for any additional messages to resolve the problem.

UST095E DYNALLOC ERROR: reason 

• 
  
  • R15=rrrr CODE=cccc INFO=iiii DSN=dsname

               DYNALLOC MSGS: messages

Reason: This message is issued when the dynamic allocation (SVC 99) request for a tape or disk sequential data set fails with a non-zero return code. If the error code is a common one, a brief explanation of the cause is shown as “reason”. In any case, the return code “rrrr”, return code “cccc” and information code “iiii” returned by SVC 99 are shown, as well as the name of the data set whose allocation failed. If SVC 99 also returned any messages (such as SMS errors) they are also displayed.

Action: If you cannot determine the cause of the error from the messages printed, dynamic allocation error codes are listed in various IBM manuals and are also listed in Appendix A of the IBM ISPF online HELP.

If you are unable to resolve the problem, please retain all error information, including your System log, and contact BMC Support for assistance.

UST096E RESTORE: ARCHIVE VOLUME NOT IN CURRENT SET -- FILE NOT ACCESSIBLE

Reason:During a Restore from the Archive data set, z/OS Storage Server was unable to mount the correct volume.

Action:This indicates an internal error in the Repository Catalog records. Please retain all error information, including your System log, and contact BMC Support for assistance.

UST097W IMMEDIATE SHUTDOWN REQUESTED -- function TERMINATED

Reason:The indicated function was in progress when UPSTREAM z/OS Storage Server received an immediate shutdown request from the System Operator. The function is terminated

Action: None.

UST098E LOGON EXIT - NOT APPC INIT REQUEST

Reason: The indicated function was not received as expected. The function is terminated.

Action: Contact BMC Support for assistance.

UST099 PARM --> parmdata

Reason: If parameters were passed to UPSTREAM via the PARM= JCL operand on the EXEC statement in the UPSTREAM startup PROC, the parameters are shown here. (See Define the UPSTREAM Started Task PROC)

Action: None.

UST099E PARM KEYWORD UNKNOWN [INVALID NUMERIC]

Reason: One of the startup parameters or its specified value shown in the UST099 message is invalid.

Action: See  Configure the MAIN Options for valid parameters.

UST100W 'QUIT' REQUESTED -- INITIATION ABORTED

Reason: A F UPSTREAM,TERM or F UPSTREAM,QUIT console command was entered to request immediate termination of UPSTREAM. This Client was in the process of initiating a conversion; it is terminated.

Action: None.

UST101E typeEXIT--CHECK FOR ACTSESS ERROR

Reason: This message indicates VTAM returned an error indication to an APPC “CHECK” request to activate the pending active session to the Client.

Action: Communication error codes are reported in a following message. Consult IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST102W PROFILE NAME ALREADY IN USE -- DISALLOWED

Reason: A UPSTREAM Client attempted to use a Profile Name that was already in use by another Client currently in conversation with UPSTREAM.

Action: Verify that the same Profile Name has not been accidentally assigned to two Clients, and that the two Clients involved are using the correct Profile Names.

UST102W PROFILE NAME profilename NOT AUTHORIZED -- DISALLOWED

Reason: An UPSTREAM Client user requested display or update of a profile in the UPSTREAM configuration, and SECLVL=2 or 3 was in effect, but the userid entered by the user was not authorized for ALTER access to the profile name requested.

Action: Repeat the request using a userid that is authorized to ALTER the profile name, or update your security system to authorize the userid.

UST103E LOGON EXIT -- INQUIRE SESSPARM ERROR

Reason: The Main Task VTAM LOGON EXIT was unable to issue an INQUIRE request to verify the suggested BIND image. The session request is denied.

Action: Communication error codes are reported in a following message. Consult IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST104W LU=luname - USING DEFAULT BIND

Reason: This message is issued from within the Main Task VTAM LOGON exit. The supplied BIND image failed LU 6.2 standard verification. z/OS Storage Server will attempt to use the internal default Bind image to establish the session.

Action: If you are using the IBM-supplied #INTER log mode table entry for UPSTREAM sessions, this is normal and can be ignored. Otherwise, verify that the specified parameters in the mode table entry you are using are correct for an LU 6.2 session.

UST105E RESTORE: RECEIVE FOR EVENT RECORD FAILED

Reason: The RESTORE logic received a communication error while trying to retrieve a record describing a Client error.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST106 UPSTREAM CUSTOMER NUMBER nnnnnnnn

Reason: This message is informational only. It is issued by the z/OS Storage Server main task during its initialization.

Action: None.

UST107W* nnnn DAYS TO UPSTREAM EXPIRATION

Reason: This message is issued during main task initialization to indicate the z/OS Storage Server product authorization time period is about to expire.

Action: Contact BMC Support if you have any questions.

UST109E AUTHORIZATION FAILED, CODE = nn

Reason: During initialization, the z/OS Storage Server main task found an authorization violation. The “CODE=nn” value indicates the type of authorization failure.

Action: Retain the error log and contact BMC Support for assistance.

UST111E* UPSTREAM USE HAS EXPIRED, CONTACT BMC SUPPORT FOR ASSISTANCE

Reason: This message is issued by the UPSTREAM main task to indicate that the timed use of the product has expired. z/OS Storage Server will not start.

Action: Contact BMC Support for assistance.

UST112 WS FILE SKIPPED: wsfilename

Reason: This message is informational, it is issued during a Backup process to indicate that the Client notified the mainframe it is skipping a file. This is a normal condition and is encountered if the Client finds a file inaccessible during the Backup process.

Action: None.

UST113W CHECKSUM ERROR:checksm1-checksm2 wsfilename

Reason: During a full MERGE backup, the checksum validation option was requested. For files which are already on the backup and do not need to be translated, UPSTREAM will calculate a checksum of each Client file on the Client and also on z/OS (from the backup). This message is issued if the checksum values do not match; “checksm1” is the checksum from z/OS, “checksm2” is the checksum from the Client. This detects files that have changed on the Client since the last backup but were not flagged as requiring backup.

Action: The Client file whose checksum did not match is retransmitted from the Client.

UST114E MAINFRAME VSAM ERROR

Reason: This message is issued during a Backup process along with a group of other messages indicating an error was encountered during a VSAM request. This message is also sent to the Client.

Action: Review the other messages associated with the VSAM error.

UST115E REQUESTED RECORDSIZE EXCEEDS ALLOWED BLKSIZE -- TERMINATING

Reason: The “RECORDSIZE” value specified in the Client backup parameters exceeded the allowable blocksize for the target device.

Action: Verify that a valid “RECORDSIZE” value was specified for the backup request. If the request is for a “sequential DASD” backup, you may increase the “DASDBLK” value in the z/OS Storage Server mainframe configuration to accommodate the request.

UST116E ATTNEXIT: APPC ERROR RCVFMH5 REJECT FAILED

Reason: A FMH5 was received in error; a request to REJECT it did not complete successfully.

Action: Communication error codes are reported in a following message. Consult IBM VTAM manuals to interpret the error, or contact BMC Support for assistance. Review the UPSTREAM log on the Client for information as to the cause of the failure.

UST117E function FAILED

Reason: A communications failure occurred.

Action: Refer to subsequent messages for additional information.

UST117 INQUIRE-VERSIONS PROCESS STARTED

Reason: An inquire-versions request was received from an UPSTREAM Client.

Action: None.

UST118E PRIMARY RECEIVE PACING=ZERO -- SESSION DISALLOWED

Reason: The UPSTREAM main task VTAM logon exit found, during session initiation, that the bind contained a zero value for the primary receive pacing count. Using this value could result in serious mainframe problems. The logon exit instead disallowed the requested session.

Action: Verify that the VTAM APPL definition for z/OS Storage Server contains a valid “VPACING” value. Contact BMC Support for assistance.

UST119E* APF AUTHORIZATION CHECK FAILED -- CANNOT CONTINUE

Reason: During initialization, an z/OS Storage Server component has determined that it is not running as an APF authorized task. UPSTREAM terminates.

Action: Verify that the load library from which z/OS Storage Server is being run is APF authorized in the z/OS system.

UST120E RECEIVE FOR RESTORE-DESC REPEATED STRUCTURE FAILED

Reason: The Sequential Restore process received a communication error indication after issuing an receive request.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST121E UNEXPECTED DEALLOCATE RECEIVED FROM WORKSTATION

Reason: The Sequential Restore process received an unexpected Deallocate indication, terminating the active conversation.

Action: Review the UPSTREAM log file on the Client for an indication as to the error cause. Contact BMC Support for assistance.

UST122W RESTORE: C-RECORD NOT FOUND FOR SPECIFIC VERSIONDATE

Reason: The sequential restore processor was unable to locate a catalog record for the requested “versiondate”. It is possible that the original backup was not committed prior to it's termination.

Action: Perform an “inquire versions” function to verify that you are requesting a valid “versiondate” as recorded in the VSAM repository.

UST123E ARCHIVE RESTORE DISALLOWED -- SECURITY CHECK FAILED

Reason: SECLVL=2 or 3 was specified in the configuration, and the security check for tape restores failed.

Action: See Chapter 4 “Security” for details on authorizing restores from tape.

UST124E SEND OF BACKUP-DESCRIPTION FAILED

Reason: The z/OS Storage Server received an error indication after issuing an Send request.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST125E RESTORE: CATALOG S-RECORD NOT FOUND

Reason: The sequential restore process was unable to locate the catalog record requested. It is possible that the backup was terminated before it was committed.

Action: Perform an “inquire versions” request to determine whether the backup information does exist. Verify that you are using the correct version information in the request. Verify that the sequential backup data set exists and is cataloged in the system.

UST126E DYNALLOC ERROR: R15=rrrrrrrr CODE=cccc INFO=iiii

Reason: The sequential restore process was unable to dynamically allocate the requested sequential backup data set. The additional information fields contain the return codes and information reason codes associated with the failed dynamic allocation request.

Action: Verify that the requested sequential backup data set exists and is cataloged in the system. See message UST095E for information on interpreting the error codes.

UST127E OPEN FOR RESTORE DATASET FAILED

Reason: The sequential restore process was unable to open the sequential data set to perform the restore.

Action: Verify that the requested sequential backup data set exists and is cataloged in the system. Use another system utility to verify that the backup sequential data set is the correct format and has not been altered, copied to a different format, or corrupted in any way.

UST128W NO CATALOG RECORD FOUND FOR THIS PROFILE NAME

Reason: The sequential restore process was unable to locate the z/OS Storage Server catalog record for the requested sequential backup.

Action: Perform an “inquire versions” request to verify that you are requesting the correct Profile Name and “versiondate”.

UST129E SEND FOR F-RECORD FAILED

Reason: The sequential restore process received a communication error indication after issuing a Send-Data request for a File-Information Record.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance. Review the UPSTREAM log on the Client for information as to the cause of the failure.

UST130E INSUFFICIENT STORAGE FOR MERGE BACKUP

Reason: The MERGE BACKUP function requires storage above the 16MB line; the amount varies by the number of files involved and the number of concurrent backups in progress. Insufficient storage was available for the MERGE BACKUP requested by this Client and the backup is terminated.

Action: Increase the above-the-line storage available to z/OS Storage Server by coding a REGION= value on the EXEC statement in the UPSTREAM startup PROC, (see Section “Define the UPSTREAM Started Task PROC”) with a value greater than 32M (32MB is the default above-the-line storage size), or schedule the MERGE BACKUPs so that fewer are running concurrently.

UST131W IMMEDIATE SHUTDOWN REQUESTED -- RESTORE TERMINATED

Reason: The sequential restore process was notified that the system operator requested an immediate UPSTREAM shutdown.

Action: None.

UST132E RESTART: BACKUP ALREADY ARCHIVED -- CANCELLED

Reason: Restart of an interrupted backup was attempted, but UPSTREAM records indicate that the backup was successfully completed.

Action: No restart is required.

UST133E DEALLOCATE-CONFIRM REQUEST FAILED

Reason: The sequential restore process received a communication error indication at the end of the restore process after issuing a Confirm request.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance. Review the UPSTREAM log on the Client for information as to the cause of the failure.

UST134E SEND FILE-DATA RECORD FAILED

Reason: The sequential restore process received a communication error indication after issuing an Send-Data request for a File-Data Record.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance. Review the UPSTREAM log on the Client for information as to the cause of the failure.

UST135E RECEIVE FOR EVENT RECORD FAILED

Reason: The sequential restore process received a communication error indication after issuing a Receive request for a Client event record.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance. Review the UPSTREAM log on the Client for information as to the cause of the failure.

UST136E RESTORE: DATA RECORD NOT FOUND IN BLOCK EXPECTED

Reason: The sequential restore process was unable to locate a data record during the restore in the block in which it was expected.

Action: Verify that you are restoring from the correct data set, that it is not a copy of the current backup data set. You may have to run the USTREGEN utility to make the copied data set current in the VSAM control clusters.

UST137E RESTORE: UNABLE TO LOCATE BACKUP FILE FOR RESTORE

Reason: The sequential restore process was unable to dynamically allocate a sequential disk backup file to perform the restore. It received an indication that the file does not exist or is not cataloged. You may be attempting to restore from a sequential backup file that has been deleted or uncataloged in the system. This message is accompanied by message UST138E containing the data set name z/OS Storage Server was attempting to dynamically allocate.

Action: Verify that the data set exists and is cataloged.

UST138E DSN=dsname

Reason: This message accompanies message UST137E. It contains the data set name z/OS Storage Server was attempting to dynamically allocate.

Action: None.

UST139E UNABLE TO LOCATE BACKUP DATASET FOR RESTORE

Reason: The sequential restore process was unable to dynamically allocate a sequential tape backup file to perform the restore. It received an indication that the file does not exist or is not cataloged. You may be attempting to restore from a sequential backup file that has been deleted or uncataloged in the system. This message is accompanied by message UST159E containing the data set name z/OS Storage Server was attempting to dynamically allocate.

Action: Verify that the data set exists and is cataloged.

UST140E COMMUNICATIONS ERROR

Reason: The sequential backup process received a communication error indication.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance. Review the UPSTREAM log on the Client for information as to the cause of the failure.

UST141 text of a message from the workstation

Reason: This message is issued when a Client in session with z/OS Storage Server sends an error or informational message. This message is a Client message.

Action: None.

UST142W function DISALLOWED BY CONFIGURATION

Reason: The profile in use is not enabled for the function indicated.

Action: Review the z/OS Storage Server configuration file to determine whether this profile should be permitted to perform the requested function.

UST143E RECEIVE FOR BACKUP_DESC_REP FAILED

Reason: The sequential backup process received a communication error.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance. Review the UPSTREAM log on the Client for information as to the cause of the failure.

UST144E RECEIVED UNRECOGNIZED STRUCTURE

Reason: The sequential backup process received an unrecognized structure from the Client. This is most likely an internal UPSTREAM error.

Action: Review the UPSTREAM log on the Client for information as to the cause of the failure.

UST145E DYNALLOC ERROR: R15=rrrrrrrr CODE=cccc INFO=iiii

Reason: The sequential backup process was unable to dynamically allocate the backup sequential backup data set.

Action: Verify that the requested sequential backup data set exists and is cataloged in the system. See message UST095E for information on interpreting the error codes.

UST146E *** OPEN FOR BACKUP DATASET FAILED ***

Reason: The sequential backup process was unable to open the sequential backup output data set.

Action: If you are unable to resolve the problem, contact BMC Support for assistance.

UST147E SEND COMMUNICATION STRUCTURE FAILED

Reason: An error occurred sending the communication record handshake to the FDRPAS partner.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST148E *** MAINFRAME VSAM ERROR ***

Reason: The sequential backup process sends this message to the Client to indicate an error occurred during a mainframe VSAM request.

Action: None.

UST149E DEALLOCATE_CONFIRM ERROR

Reason: The sequential backup process received a communication error indication after issuing an Deallocate request.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance. Review the UPSTREAM log on the Client for information as to the cause of the failure.

UST150E BACKUP_DESC FLAG LENGTH ERROR

Reason: The sequential backup process received an invalid internal structure from the Client. The most probable cause for this problem is that the Client is using an old, unsupported version of UPSTREAM.

Action: If you are unable to resolve the problem, contact BMC Support for assistance.

UST151W DASD BACKUP DISALLOWED BY CONFIGURATION

Reason: The sequential backup process has determined that this Client profile name was not configured to allow sequential backups to mainframe DASD.

Action: Review your mainframe configuration file. Verify that this Profile Name is permitted to perform sequential disk backups.

UST152W TAPE BACKUP DISALLOWED BY CONFIGURATION

Reason: The sequential backup process has determined that this Client profile name was not configured to allow sequential backups to mainframe tape.

Action: Review your mainframe configuration file. Verify that this Profile Name is permitted to perform sequential tape backups.

UST153E REMOVE-FILE NAME MISMATCH -- IGNORED

Reason: The sequential backup process received a REMOVE-FILE request from the Client for a file other than the current file being processed.

Action: This is an internal error. Notify BMC Support as soon as possible.

UST154W CATALOG RECORD NOT FOUND FOR BACKUP RESTART

Reason: The sequential backup process was unable to locate the control record to restart the backup. The prior backup may not have progressed far enough to be committed.

Action: Perform an “inquire versions” process to determine whether you are attempting to restart an interrupted backup and if the backup is present in UPSTREAM.

UST155E ERROR READING CATALOG RECORD -- UNABLE TO RESTART BACKUP

Reason: The sequential backup process was unable to read the required control record to restart the backup. The prior backup may not have progressed far enough to be committed.

Action: Perform an “inquire versions” process to determine whether you are attempting to restart an interrupted backup and if the backup is present in UPSTREAM.

UST156E TAPE BACKUP DISALLOWED -- NO UNIT VALUE SPECIFIED IN CONFIGURATION

Reason: The sequential tape backup process is unable to build the dynamic allocation request because the “TUNIT” value was not specified in the z/OS Storage Server Configurator input “DEFINE” record for this Profile Name.

Action: This may be perfectly valid if you intended to disallow this Client Profile Name from performing sequential tape backups. Otherwise, verify that the configuration “DEFINE” record for this Profile Name contains the “TUNIT” parameter to specify the z/OS “unitname” to be used for the dynamic allocation request.

UST157E MERGE BACKUP ERROR -- REASON=reason text

Reason: A MERGE BACKUP was requested by the Client, but it failed for the reason indicated. Possible reason codes and the actions to be taken are:

1 – PREVIOUS FULL BACKUP NOT FOUND

z/OS Storage Server cannot find a record of a previous full backup taken under this profile. Either it has expired or one was never taken. Take a “first-time full” backup.

2 – ERROR READING CATALOG FOR PREVIOUS BACKUP

z/OS Storage Server could not successfully read its catalog records to locate the previous backup under this profile. Contact BMC Support for assistance. If necessary, take a “first-time full” backup.

3 – PROFILE DOES NOT ALLOW MERGE BACKUP

The profile does not have the MERGE attribute, so MERGE BACKUPs cannot be done. Use a different profile with MERGE, or update the configuration to add MERGE to this profile, or do a “non-MERGE backup”.

4 – OPERATOR CANCELLED MOUNT OF PREVIOUS TAPE -- CALLING FOR SCRATCH

The console operator replied NO to the console messages requesting that a previous backup tape be mounted so that UPSTREAM can append data to it. UPSTREAM will call for the mount of a SCRATCH tape instead.

5 – OPERATOR CANCELLED MOUNT OF MERGE BACKUP

The console operator replied “NO” to the console messages requesting that a previous backup tape be mounted. If message UST157 REASON=Z is issued, UPSTREAM will recover by requesting the missing files from the Client. Otherwise, a “first-time full” backup will have to be done.

6 – PREVIOUS FULL BACKUP FAILED TO OPEN

An OPEN error occurred when trying to open a previous backup. See the z/OS SYSLOG or the UPSTREAM JOBLOG for IBM messages indicating the error. Contact BMC Support for assistance. UPSTREAM will recover by requesting the missing files from the Client.

7 – DYNAMIC ALLOCATE FAILED FOR PREVIOUS FULL BACKUP COMP=cccc DSN=dsn

z/OS Storage Server had an error (completion code “cccc”) trying to dynamically allocate the previous full backup file named “dsn”. See message UST095E for codes. UPSTREAM will recover by requesting the missing files from the Client.

8 – DEBLOCKING ERROR

z/OS Storage Server found an invalidly formatted block when reading a previous backup tape. That backup is probably not usable. UPSTREAM recovers by requesting the missing files from the Client.

9 – NO PREVIOUS BACKUPS WILL REQUEST FILES FROM PC

z/OS Storage Server could not find a catalog record for a previous backup for this profile. Either it has expired or one was never taken. All required files are requested from the Client.

A – FILEDATA WITHOUT FILEINFO

z/OS Storage Server did not find expected file-info records on a previous backup tape. This is probably due to a backup taken with a version of UPSTREAM prior to V2.3.2 after MERGE BACKUPs were taken under this profile. A “first-time full” backup will have to be done. If necessary, contact BMC Support for assistance.

B – FILE=filename

Internal error during MERGE processing. Contact BMC Support for assistance.

C – BAD COUNT

Internal error during MERGE processing. Contact BMC Support for assistance.

D – PREVIOUS BACKUP WAS INTERRUPTED

During MERGE processing, a backup required as input was interrupted and never completed. If possible, complete the backup and rerun MERGE. If this backup can no longer be completed, it might be necessary to exclude it from the MERGE process. Contact BMC Support for assistance if necessary.

E – VSAM ERROR KEY=keyvalue

While writing FILEINFO records to the FILEINFO database file, a VSAM error was encountered. The key of the record in error is displayed. Review additional messages to determine the actual reason for the error. Contact BMC Support for assistance if necessary.

F – COPYINCR DSN=dsname

During MERGE processing, the system was performing the COPYINCR function and encountered a VSAM error updating the UPSTREAM repository with the new information about the location of the COPYINCR data sets. Review additional messages to determine the actual reason for the error. Contact BMC Support for assistance if necessary.

G – SCRATCH ERROR COMP=cccc DSN=dsname

During MERGE processing, an error was encountered when attempting to UNCATALOG/SCRATCH a z/OS data set. Review the COMP field value to determine the actual error code associated with the operation (CATALOG). Contact BMC Support for assistance if necessary.

H – READ I/O ERROR DSN=dsname

While de-blocking records during normal MERGE processing an error was encountered on the backup data set name listed in the error message. Contact BMC Support for assistance if necessary.

J – DUPLICATE MISSING RECORDS KEY=keyvalue

While processing files associated with the DUPLICATE database during MERGE processing an error was encountered on the key listed in the error message. Contact BMC Support for assistance if necessary.

Q – OPERATOR CANCELLED MERGE BACKUP

During MERGE processing, the z/OS system operator (or someone with system operator privileges) requested that this UPSTREAM function be terminated. Review the z/OS Storage Server USTLOG output as well as the z/OS SYSLOG to determine who issued the request and their reasoning.

V – DUPLICATE VSAM ERROR KEY=keyvalue

While processing files associated with the DUPLICATE database during MERGE processing an error was encountered on the key listed in the error message. Contact BMC Support for assistance if necessary.

Y – DUE TO PRIOR ERROR MERGE TERMINATED

A preceding message indicates that an error occurred during a Full Merge Migration. No recovery is possible, so the Merge was terminated. Review the Migration section of this manual for the necessary actions you must take before re-submitting the Migration request.

Z – DUE TO PRIOR ERROR WILL REQUEST MISSED FILES FROM PC

This is an information message that follows another message and indicates that the previous error is one that UPSTREAM can recover from by requesting files from the Client to replace those that it was unable to copy from a previous backup.

Action: Follow the suggested actions contained within the REASON description. Contact BMC Support if you require further assistance.

UST158 aaaaaaaa MERGE FILES: bbbbbbbb COPIED FROM BACKUP

             cccccccc ALREADY ON BACKUP dddddddd FROM PC IN PHASE3

             eeeeeeee DEFERRED MERGE FILES

             ffffffff FILES MIGRATED: gggggggg MIGRATED FILES COPIED

             hhhhhhhh MIGRATED FILES DELETED

             IIIIIIII COPYINCR FILES: mmmmmmmm COPYINCR DIRECTORIES

             nnnnnnnn BACKUPS COPIED TO FULL

             oooooooo FILES COPIED FROM DUPLICATE DATABASE

            pppppppp FILES SAVED IN DUPLICATE DATABASE

Reason: At the end of a successful MERGE BACKUP, this message indicates what work the MERGE had to do. Not all parts of the message shown will appear, depending on what parts of the MERGE BACKUP process were required for this backup.

Action: None.

UST159EDSN=dsname

Reason: This message accompanies message UST139E. It contains the data set name z/OS Storage Server was attempting to dynamically allocate.

Action: None.

UST160W NO RECORDS MATCH RESTORE SPECIFICATION

Reason: The sequential tape restore process was unable to locate any backup records which match the requested restore specification.

Action: Verify that you are using a correct Profile Name and VersionDate value. You should perform an Inquire-Versions to verify that the backup version exists. Also, verify that the Client path name you are requesting was contained in the backup you are attempting to restore. You should perform an Inquire-Files process to verify this.

UST161E SEND OF FILE-INFO RECORD FAILED

Reason: The sequential tape restore process received a communication error indication after issuing a SEND-DATA request to send a File-Information record to the Client.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST162E OPEN FOR SEQUENTIAL BACKUP FILE FAILED

Reason: The sequential tape restore process received an error indication trying to OPEN the sequential tape backup data set.

Action: If you are unable to resolve the problem, retain all error information and contact BMC Support for assistance as soon as possible.

UST163E SEND OF FILE-DATA RECORD FAILED

Reason: The sequential tape restore process received a communication error indication after issuing a SEND-DATA request to send a File-Data record to the Client.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST164E DYNALLOC ERROR: R15=rrrrrrrr CODE=cccc INFO=iiii

Reason: The sequential tape restore process received an error indication trying to dynamically allocate the tape backup data set to perform the restore process.

Action: Verify that the requested sequential backup data set exists and is cataloged in the system. See message UST095E for information on interpreting the error codes.

UST165E GOTEVENT RECEIVE ERROR

Reason: The sequential tape restore process received a communication error indication while attempting to receive an “event” information record from the Client.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST166W NO FILES MEET RESTORE SPECIFICATION versiondate filespec

Reason: The sequential tape restore process was unable to locate any files that match the requested restore specification.

Action: Verify that the Client has specified the correct Profile Name and Versiondate for the restore request; perform an Inquire-Versions request to verify this. Verify that the Client has specified a valid restore file specification path name that is contained in the backup version being requested; run a Inquire-Files request on this version to verify this.

UST167E OPEN FOR SEQUENTIAL BACKUP FILE FAILED

Reason: The sequential tape restore process was unable to OPEN the sequential backup file to perform the restore.

Action: If you are unable to resolve the problem, retain all error information and contact BMC Support for assistance as soon as possible.

UST168E SEND OF FILE-INFO RECORD FAILED

Reason: The sequential tape restore process received a communication error indication while attempting to send a File-Information record to the Client.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST169E SEND OF FILE-DATA RECORD FAILED

Reason: The sequential tape restore process received a communication error indication while attempting to send a File-Data record to the Client.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST170E EVENT HANDLER RECEIVE ERROR

Reason: The sequential tape restore process received a communication error indication while attempting to receive an event record from the Client.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST171E DATA RECORD NOT FOUND FOR RESTORE

Reason: The sequential tape restore process found that the data requested by the Client for restore was not where UPSTREAM records indicate it should be located.

Action: Verify that the correct tape data set is being used for the restore and that it is not a copy of the tape backup. If so, you will need to run the USTREGEN utility to make that tape data set usable for restore processing.

UST172E error type FOR RESTORE OF FILE=file description

Reason: The sequential tape restore process found that the data requested by the Client for restore was not where UPSTREAM records indicate it should be located.
“error type” is:

NO DATA RECORD FOUND

if no records were found at all.

DATA RECORDS MISSING

if some records were found.

VSAM RECORD ERROR

if an error occurred reading the UPSTREAM repository.

PREMATURE END-OF-FILE

if the end of the backup was encountered when not expected.

“file description” includes the data set name, volume serial, and location information describing the backup file where the error occurred.

Action: Verify that the correct tape data set is being used for the restore and that it is not a copy of the tape backup. If so, you need to run the USTREGEN utility to make that tape data set usable for restore processing.

UST173 function COMPLETED SUCCESSFULLY (LU=luname)

Reason: This message is issued by all processes to show that the indicated function has completed successfully. This message may optionally be written to the system log (SYSLOG) if the “WTOCOMP” option was specified in the z/OS Storage Server Configurator “MAIN” record.

Action: None.

UST174W function COMPLETED WITH ERRORS (LU=luname)

Reason: This message is issued by all processes to show that the indicated function has completed with some potential errors. This may simply indicate that one or more of the files requested for backup were not available for one reason or another at the time the backup was performed (“skipped files”). This message may optionally be written to the system log (SYSLOG) if the “WTOCOMP” option was specified in the z/OS Storage Server Configurator “MAIN” record.

Action: None.

UST175E function FAILED reason (LU=luname)

Reason: This message is issued by all processes to indicate the indicated function has failed. This message may optionally be written to the system log (SYSLOG) if the “WTOCOMP” option was specified in the z/OS Storage Server Configurator “MAIN” record. “reason” may be “WAS SUSPENDED” if the Client requested suspension or “COMMUNICATIONS” if the failure was due to a communications error; otherwise it is blank.

Action: Review any preceding messages in the z/OS Storage Server log file, the z/OS system log (SYSLOG), and the Client UPSTREAM log file for the causes of the process failure.

UST176 RESTORE COMPLETED SUCCESSFULLY (LU=luname)

Reason: This message is issued by all restore processes to indicate a restore has completed successfully. This message may optionally be written to the system log (SYSLOG) if the “WTOCOMP” option was specified in the z/OS Storage Server Configurator “MAIN” record.

Action: None.

UST177W RESTORE COMPLETED WITH ERRORS (LU=luname)

Reason: This message is issued by all restore processes to indicate a restore process has encountered errors. This message may optionally be written to the system log (SYSLOG) if the “WTOCOMP” option was specified in the z/OS Storage Server Configurator “MAIN” record.

Action: Review any preceding messages in the z/OS Storage Server log file, the z/OS system log (SYSLOG), and the Client log file for the causes of the process errors.

UST178E RESTORE FAILED reason (LU=luname)

Reason: This message is issued by all restore processes to indicate a restore process has failed. This message may optionally be written to the system log (SYSLOG) if the “WTOCOMP” option was specified in the z/OS Storage Server Configurator “MAIN” record. “reason” may be “WAS CANCELLED” if the Client requested termination or “COMMUNICATIONS” if the failure was due to a communications error; otherwise it is blank.

Action: Review any preceding messages in the z/OS Storage Server log file, the z/OS system log (SYSLOG), and the Client log file for the causes of the process errors.

UST179E FILE-INFO VOL=vvvvvv AND BACKUP CATALOG DO NOT MATCH ON DSN=dsname

Reason: The volume information in the UPSTREAM File-Info data set and that in the system catalog entry for the backup data set do not match.

Action: Attempt to determine the reason for the mismatch. If you can determine which volume list is correct, either recatalog the backup data set (e.g., IDCAMS DEFINE NONVSAM) or run USTREGEN against the backup tapes to update the UPSTREAM information.

UST180E SUBTASK PROCESS FAILED profilename luname COMP=Snnn Unnn

Reason: This message is issued by the z/OS Storage Server main task to indicate that a sub-task process has abnormally terminated; “Snnn” is the z/OS System sub-task completion or abend code if applicable, Unnn is the User completion code. This message may optionally be written to the system log (SYSLOG) if the “WTOCOMP” option was specified in the z/OS Storage Server Configurator “MAIN” record.

Action: Review the z/OS Storage Server JES joblog to determine the cause of the sub-task failure.

UST181W NO FILES FOUND FOR VERDATE=versiondate PATH=fileid

Reason: This message is issued by the z/OS Storage Server sequential restore processes to indicate they were unable to locate any File-Information records that matched the requested restore specification.

Action: Verify that the Client is using the correct Profile Name and VersionDate to perform the restore; perform an Inquire-Versions request to verify this. Verify that the Client is using a valid file path name for the restore that was included in this backup version; perform an Inquire-Files request to verify this.

UST182E CNOS REQUEST FAILED

Reason: During an initiation request an “CNOS” request returned a communication error indication.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST183E SEND-DATA RUN-FUNCTION STRUCTURE FAILED

Reason: During an initiation request an “send data” request returned a communication error indication.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST184E ERROR ON RECEIVE FROM REQUESTOR

Reason: During an initiation request an “receive data” request returned a communication error indication.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST185E ERROR ON SEND-DATA TO WORKSTATION

Reason: During an initiation request an “send-data” request returned a communication error indication.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST186E ERROR ON DEALLOC-CONFIRM TO WORKSTATION

Reason: During an initiation request an “deallocate-confirm” request returned a communication error indication.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST187E ERROR RECEIVING TYPE-90 EVENT RECORD FROM WORKSTATION

Reason: During an initiation request an “receive data” request for an error notification message from the Client returned a communication error indication.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST188E INVALID STRUCTURE RECEIVED FROM WORKSTATION -- EXPECTED TYPE-xx EVENT

Reason: During an initiation request an invalid structure was received from the Client LU. This is most likely an internal UPSTREAM error.

Action: Please retain all the error information and contact BMC Support for assistance.

UST189E SEND-CONFIRMED TO REQUESTOR FAILED

Reason: During an initiation request an “send-confirmed” request to the USTBATCH requester returned a communication error indication.

Action: Communication error codes are reported in a following message. Consult IBM z/OS Communications Server manuals to interpret the error, or contact BMC Support for assistance.

UST190E APPC/TCP ALLOCATE ERROR

Reason: VTAM or TCP/IP returned an error indication as the result of the z/OS Storage Server mainframe-initiator module having issued an “ALLOCATE” request to initialize a conversation to the indicated Client.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST191E UNEXPECTED DEALLOCATE RECEIVED FROM WORKSTATION

Reason: A “deallocate” indication was detected prematurely.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST192E DEALLOCATE RECEIVED FROM REQUESTOR -- REQUEST TERMINATED

Reason: During an initiation request an “deallocate” indication was received from the requester prematurely. The initiation request is being discarded.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST0193E reason -- REQUEST FAILED

Reason: During an remote initiation attempt (USTBATCH), the request could not be initiated due to the reason indicated.

Action: Validate that the target Client name is valid and that the Client is active and eligible for a session and conversation request (for TCP/IP-connected Clients, UPSTREAM may need to started on the Client before the remote initiation is attempted).

UST194E TARGET LU IS INVALID - REQUEST FAILED

Reason: The USTBATCH utility found the specified “TARGLU” value to be invalid. This can also occur if TARGNAME= was specified but the indicated name was not registered.

Action: Verify that the “TARGLU” value specified to USTBATCH is correct. If the target name was not registered, ensure that the name is registered and resubmit the request.

UST195E LOGMODE NAME IS INVALID - REQUEST FAILED

Reason: The USTBATCH utility found the value specified for the “LOGMODE” parameter was invalid.

Action: Verify that the “LOGMODE” parameter value specified to the USTBATCH utility is valid.

UST196E REQUEST PARAMETER ERROR RC='xxxxxxxx'

Reason: The USTBATCH utility found an invalid parameter in the input stream.

Action: Correct the indicated parameter statement.

UST197 REMOTE INITIATION TO lu1 FROM lu2 - USTBATCH JOBNAME=jobname USERID=userid

Reason: This is an informational message indicating a remote initiation is in progress from an LU named “lu2” to an LU named “lu1'. If the request is from USTBATCH, the batch “jobname” or TSO “userid” running USTBATCH is shown. If the security “userid” was successfully extracted from that job or TSO session, it is also shown.

Action: None.

UST198E ERROR RECEIVING RUN_FUNCTION FROM REQUESTOR

Reason: During an initiation request an “receive data” request returned a communication error indication.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST199E INITIATOR UNABLE TO GENERATE A VTAM RPL - POSSIBLE STORAGE SHORTAGE

Reason: During an initiation request the online initiator was unable to generate a VTAM RPL control block. This may indicate a storage shortage.

Action: Communication error codes are reported in a following message. Consult IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST200E RESTORE BACKUP DENIED DUE TO DUMMY (SIMULATE) PROFILE

Reason: A request was received from a Client to restore from a backup taken under a special DUMMYxxx profile used for backup testing and simulation. Such backups do not contain file data and cannot be restored.

Action: None.

UST201E VSAM MODCB/POINT REQUEST FAILED

Reason: The “remove-backup” processor encountered a VSAM error. This message is accompanied by message UST051E containing the VSAM error indicators.

Action: Refer to message UST051E for details on interpreting the error.

UST202E REMOVE BACKUP ERROR REASON=reason

Reason: The 'remove-backup” processor encountered an error for the reason shown.

Action: Based on the reason code, correct the error and resubmit the request.

UST203E VSAM ERASE REQUEST FAILED

Reason: The “remove-backup” processor encountered a VSAM error. This message is accompanied by message UST051E containing the VSAM error indicators.

Action: Refer to message UST051E for details on interpreting the error.

UST204E reqtype REQUEST FAILED -- R15=nnnnnnnn DSN=dsname

Reason: The “remove-backup” processor encountered an error attempting to delete a sequential data set. “reqtype” is LOCATE, SCRATCH, or UNCATALOG. “nnnnnnnn” is the return code in hex.

Action: If you are unable to resolve the problem, please retain all the error information and contact BMC Support for assistance.

UST206E SEND CONFIRMED RESPONSE ERROR

Reason: The “remove-backup” processor encountered a communication error attempting to return an “confirmed” response to the requester.

Action: Communication error codes are reported in a following message. Consult TCP/IP or IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST207 REMOVE-BACKUP ENTERED BY USER username

Reason: The “remove-backup” processor has been entered on request by the user indicated. This message is informational only.

Action: None.

UST208 REMOVING: profile versiondate backup-type - nnnnnnnn FILE RECORDS ERASED

Reason: The “remove-backup” function (REMOVEDSN) has been entered and is deleting the specified backup version. This may also occur during Full Merge Migration as Simple Migration files are copied to the full backup and deleted. “nnnnnnnn” includes both file records and directory records. This message is informational only.

Action: None.

UST209E PREMATURE END-OF-FILE ON DSN=dsname

Reason: The restore processor encountered the end of the tape backup file before finding all expected data. Possibly the catalog entry was corrupted so that not all volumes are recorded.

Action: Verify that the tape data set requested during the restore is the correct one, and that this is not a copy of the original backup file data set.

UST210E TARGET NOT AVAILABLE -- function TIMEOUT

Reason: The z/OS Storage Server mainframe initiator has determined that the target LU is not available to respond to the function noted in the error message.

Action: Verify that the target LU is specified correctly in the batch requester job. Verify that the target LU is available and configured for session and conversation requests. Review the UPSTREAM log on the target LU for error messages.

UST211 ENTERING WAIT FOR RETRY

Reason: The z/OS Storage Server mainframe initiator was unable to allocate the requested conversation with the target UPSTREAM LU. It is entering a 10-minute wait period prior to attempting a retry operation. This message is informational only.

Action: None.

UST212 ATTEMPTING CONVERSATION RETRY

Reason: The z/OS Storage Server mainframe initiator task has completed its wait period and is attempting to retry the conversation initiation to the specified target UPSTREAM LU. This message is informational only.

Action: None.

UST213E TARGET LU NOT AVAILABLE - CONFIRM TIMEOUT

Reason: The z/OS Storage Server mainframe initiator has sent the specified request to the target LU; but, has not received a confirmation response within the 5 minute timeout window.

Action: Verify that the target UPSTREAM LU is still functional. Review the UPSTREAM log on the target LU for errors.

UST214E INVALID STRUCTURE RECEIVED - REQUEST ABORTED

Reason: The z/OS Storage Server mainframe initiator received an invalid response from the target LU. This is most likely an internal UPSTREAM error.

Action: Please retain all the error information and contact BMC Support for assistance.

UST215E IMMEDIATE SHUTDOWN REQUESTED - REQUEST ABORTED

Reason: The z/OS Storage Server mainframe initiator was notified that the system operator requested an immediate z/OS Storage Server shutdown. The indicated process was aborted.

Action: None.

UST216W IMMEDIATE SHUTDOWN REQUESTED - function TERMINATED

Reason: The indicated function was in progress when z/OS Storage Server received an immediate shutdown request from the System Operator. The function is terminated.

Action: None.

UST218E TAPE RESTORE DISALLOWED -- TAPEMOUNT SECURITY CHECK FAILED

Reason: SECLVL=2 or 3 was specified in the configuration, and the security check for tape restores failed.

Action: See Chapter 4 “Security” for details on authorizing restores from tape.

UST219E CATALOG RECORD NOT FOUND FOR RESTORE OF versiondate

Reason: During z/OS Storage Server restore processing for a specified “versiondate”, no records were found.

Action: Use the “Inquire Versions” request on the Restore menu to list all available versions, to verify that your request was correct. If it was correct, this is an internal error.

UST220E SECURITY: INVALID USERID FORMAT

Reason: During security authorization checking, z/OS Storage Server determined there was an invalid format in a control structure containing the specified userid.

Action: This is an internal error. Retain all error information and contact BMC Support for assistance.

UST221E SECURITY: INVALID PASSWORD FORMAT

Reason: During security authorization checking, z/OS Storage Server detected an invalid format item in a received control structure.

Action: This is an internal error. Please retain all error information and contact BMC Support for assistance.

UST222E SECURITY CHECK FAILED SAF COMP=X'ssss', RACF COMP=X'rrrr' CODE=X'cccc' reason

Reason: During security authorization checking, z/OS Storage Server received a non-zero return code from the z/OS SAF Router “ssss” or from your security system (rrrr and cccc). “reason” will have a brief description of the error for common error codes. However, if a check for authority to a given resource failed, “reason” will display the class and entity names, e.g., CLASS=$UPSTRM ENTITY=profile

Action: Verify the specified Userid and Password are correct and defined to your security system. A SAF error may mean that your security system is not functioning.

UST223E SECURITY: LEVEL-2 VERIFICATION FAILED

Reason: The SAF (security) call to verify the user's authority to the UPSTREAM Profile Name (as requested by SECLVL=2 or 3 in the UPSTREAM Configuration) has failed. The user is not authorized.

Action: If appropriate, authorize the user to use the Profile Name.

UST224 profilename ssssss.sss CPU SECONDs USED IN process

Reason: The indicated number of CPU seconds were used in processing the just-completed request for the indicated Profile name.

Action: None.

UST228 CONFIGURATION TABLE [RE]LOADED

Reason: This informational message confirms that the UPSTREAM configuration table has been successfully LOADED during online initialization or successfully RELOADED in response to a F UPSTREAM,REFRESH console command.

Action: None.

UST229 REQUEST USING “profname” CONFIGURATION ENTRY

Reason: The profile name entered at the Client has no entry in the z/OS Storage Server configuration, but there was either a prefix profile defined with WSPREF=prefix that matched the beginning of the entered profile name, or a profile defined with the special name “GLOBAL”. The characteristics of this profile were used for this request.

Action: None.

UST230 INQUIRE-FILES PROCESS STARTED

Reason: An inquire-files request was received from a Client.

Action: None.

UST231 RESTARTED-BACKUP PROCESS ENTERED

Reason: This informational message is issued by the backup “restart” process to indicate it has accepted the Client request and has begun the restart process.

Action: None.

UST232 RESTARTED-BACKUP PROCESS ENDING

Reason: This informational message is issued by the backup “restart” process to indicate it has completed the “backup restart” process. Any errors that may have occurred are indicated by other messages in the log file.

Action: None.

UST233* STARTING BACKUP PROCESS, TYPE=tttt LU=nnnnnnnn[BACKUP=bbbbb]

Reason: This informational message is issued by all backup processes at the time the backup begins. The “type” value “tttt” may be any of the four backup types supported by z/OS Storage Server: “DASD”, or “TAPE”. The LU value contains the network LU name of the Client. If this is a sequential backup, the “backup” value “bbbbb” indicates the type of sequential backup: “FULL” (first-time full), “FULLM” (full merge), “INCR” (incremental merge), “USER” (non-merge under a profile enabled for MERGE) or “NON-M” (non-merge under a non-merge profile). If the “WTOCOMP” option was specified on the z/OS Storage Server Configurator “MAIN” record, this message is also written to the system console and the system log (SYSLOG) via a “WTO”. If this is a simulated backup (using a DUMMYxxx profile name), “STARTING” is changed to “SIMULATE”. For a file transfer, “STARTING” is changed to “TRANSFER”.

Action: None.

UST234 BACKUP DATE: mm/dd/yyyy- ESTIMATED SIZE: kkkkkkkkkkk KB

Reason: All backup processes issue this informational message at the time the backup begins. It indicates the date the backup began on the mainframe and the estimated size in kilobytes.

Action: None.

UST235 STARTING BACKUP NON-I/O TEST

Reason: This informational message indicates that the non-I/O backup test routine has started.

Action: None.

UST236 INQUIRE-VERSIONS PROCESS ENDING

Reason: An inquire-versions request from a Client was completed.

Action: None.

UST237 INQUIRE-FILES PROCESS ENDING nnnnnnnn FILES SENT FROM mmmmmmm VERSIONS

Reason: An inquire-files request from a Client was completed.

Action: None.

UST238 SEQUENTIAL RESTORE PROCESS STARTED

Reason: This informational message indicates that a sequential restore has begun.

Action: None.

UST239* RESTORE PROCESS STARTED, TYPE=tttt LU=nnnnnnnn

Reason: This informational message is issued for all restore processes at the time the restore begins. The TYPE value “tttt” may be any of the three backup types supported by z/OS Storage Server: “ARCH”, “DASD”, or “TAPE”. The LU value contains the network LU name of the Client. If the “WTOCOMP” option was specified on the z/OS Storage Server Configurator “MAIN” record, this message is also written in the system console and the system log (SYSLOG) via a “WTO”.

Action: None.

UST240W* ACTIVE TASK FOUND -REPLY W(AIT)-FOR TASK TERM,TERM ID=NNNN, C(ANCEL),S(TATUS) OR I(GNORE)

Reason: The operator issued a console CANCEL command for the UPSTREAM online task, but UPSTREAM CANCEL protection detected that there were active backup, restore, or utility sub-tasks. This message is preceded by the UST013*, UST014*, and UST015* messages showing the active sub-tasks.

Action: The operator may reply:

WAIT

to wait for all tasks to end naturally before terminating UPSTREAM.

TERM ID=nnnn

to terminate the specified task (“nnnn” is the task ID from the status display).

CANCEL

to process the CANCEL command after closing all open data sets.

STATUS

to redisplay the sub-task status.

IGNORE

to ignore the CANCEL and return to normal operation.

All of the replies (except TERM) can be abbreviated by the first character.

UST240W* ACTIVE TASK FOUND - function AWAITING TASK TERMINATION

Reason: The operator requested termination of UPSTREAM via a STOP (P) console command (function=SHUTDOWN) or via a CANCEL (C) console command (function=CANCEL) but there were active backup/restore/utility tasks in progress. For CANCEL, this message is issued if the operator replies “WAIT” to the preceding UST240W* message.

Action: UPSTREAM terminates when all sub-tasks have completed.

UST241* function NOW ACTIVE

Reason: A trace or utility function has been started. See additional messages for the output and status of the requested function.

Action: None.

UST241* function COMPLETED RC=nn

Reason: A trace or utility function has completed with completion code “nn”.

Action: None.

UST242* QUIT ACCEPTED -- SHUTDOWN IN PROGRESS

Reason: A console command has been entered requesting immediate shutdown of UPSTREAM. See Section “Stop the UPSTREAM z/OS Storage Server” for details on shutting down UPSTREAM.

Action: If there are active backup/restore tasks, they are signaled to interrupt their processing. UPSTREAM terminates when all sub-tasks have terminated.

UST243* QUIT ACCEPTED -- LU=luname TERMINATED

Reason: A console command has been entered requesting immediate termination of the UPSTREAM session with the specified logical unit. The termination was successful.

Action: None.

UST244E* QUIT REJECTED -- LU=luname INVALID OR NOT ACTIVE

Reason: A console command has been entered requesting immediate termination of the UPSTREAM session with the specified logical unit. The “luname” is either not a valid name or is not currently in session with UPSTREAM.

Action: Determine the proper value to specify for LUNAME and resubmit the request.

UST245 STARTING VSAM WRITE TEST PROCESS

Reason: This informational message indicates that the VSAM write test has begun.

Action: None.

UST246 xxxx FILE-DATA, xxxx FILE-INFO

Reason: This informational message indicates the number of records written per second to the File-Data and File-Info files during the VSAM write test.

Action: None.

UST247 luname * SNA SESSION DEACTIVATED *

Reason: The SNA session with the indicated logical unit has been terminated.

Action: None.

UST248 luname profilename function PROCESS DETACHED TASKID=nnnn

Reason: The backup or restore sub-task for the indicated profile name and logical unit has been terminated. The internal task identifier for this process was “nnnn”.

Action: None.

UST249* MODIFY COMMAND ACCEPTED - REQUEST: parms

Reason: An F UPSTREAM command entered on the system console has been completely processed by UPSTREAM.

Action: None.

UST250E DATA RECORD(S) NOT FOUND ON REPOSITORY

Reason: Data records were not found where they were expected.

Action: The UPSTREAM repository may be corrupted. Contact BMC Support for assistance.

UST253E* MAXTASKS EXCEEDED - LU=luname REJECTED

Reason: The z/OS Storage Server received a request to initiate a new conversation, but the maximum number of active UPSTREAM tasks specified in the UPSTREAM configuration has been reached. This conversion request is rejected.

Action: Retry the request at a later time, after some other UPSTREAM tasks have terminated.

UST254W RAW BACKUP FROM versiondate BYPASSED. USE PHYSICAL BACKUP PANEL.

Reason: One or more of the backups selected for restore are either “raw” physical backups. These cannot be restored from the normal restore panels; select the physical backup panel to restore them.

Action: The physical backup is bypassed. If no other backups were selected, the restore is terminated.

UST257 TOO MANY SPACES PRECEEDING INPUT RECORD

              INVALID INPUT RECORD OR NO SUBJECT FOUND

              OPEN INPUT FILE FAILED

              PROBLEM WITH SPECIFIED MAILSERVER

              HELO RECORD TOO LONG

              ERROR IN “FROM:” STATEMENT

              ERROR IN “TO:” STATEMENT

              ERROR IN “SUBJECT:” STATEMENT

              NO MAILSERVER SPECIFIED

              EMPTY INPUT FILE

              NO “FROM:” STATEMENT FOUND

              NO “TO:” STATEMENT FOUND

             NO TCPNAME ACQUIRED

             TCP/IP ERROR API=

             SERVER ERROR API=

Reason: These are informational status messages issued for USTBATCH e-mail notification. They are issued via WTO and are posted to the JES message DD statement of the USTBATCH job.

Action: Correct the syntax within the e-mail notification member referenced by the e-mail control card (EMAILOK, EMAILWRN, or EMAILERR).

UST263* UPSTREAM LOG SWITCH WAS SUCCESSFUL

Reason: A F UPSTREAM,SWITCHLOG console command was successfully executed, to switch the UPSTREAM log to the alternate log file.

UST263E* UPSTREAM LOG SWITCH FAILED

Reason: A F UPSTREAM,SWITCHLOG console command was entered, but the switch to the alternate log file failed, probably due to errors opening the alternate log. Logging to the current log file continues.

Action: Check the UPSTREAM job log for IBM error messages relating to this error. Correct the problem if possible.

UST265E* REORG COMMAND BYPASSED REASON=reason text

Reason: A F UPSTREAM,REORG console command was entered, but the reorganization request was rejected for the reason indicated, which may be:

TASK ACTIVE

a REORG cannot be initiated when another task other than a REORG of another file is already active.

DD NOT FOUND

the DDNAME was not one of the three permitted. (USTCATLG, USTFILEI, USTFILEC).

FILE IS NOT BELOW %FREE

%F=nn was specified and the file has more that nn% free space.

%F KEYWORD INVALID

an invalid value was specified for the “%F=” operand.

Action: Consult the resolution options outlined in the “reason text”.

UST266E OPERATOR CANCELLED MOUNT OF BACKUP VOLUME

Reason: The console operator replied “NO” to the console messages requesting that a previous backup tape be mounted.

Action: The requested restore is terminated. If the tape can be mounted at a later time, resubmit the request at that time.

UST267E C-STRUCTURE NOT FOUND

Reason: A catalog record was not found where expected.

Action: The UPSTREAM repository may be corrupted. Contact BMC Support for assistance.

UST268E INVALID TCP ADDRESS RECEIVED - REQUEST ABORTED

Reason: For a mainframe-initiated request (via USTBATCH) an invalid TCP/IP target address was specified.

Action: Verify and correct the TCPTARG= value and resubmit the USTBATCH job.

UST269E REQUEST CONTROL REJECT FAILED

Reason: For a mainframe-initiated request (via USTBATCH) a VTAM APPC REQUEST-CONTROL request to the Client failed.

Action: Check the Client. Make sure that its APPC software is operating correctly.

UST270E NOTIFY SEND TO USTBATCH FAILED

Reason: The UPSTREAM online initiator attempted to communicate with the USTBATCH job that initiated the request, but the APPC SEND request failed. A UST038E message follows with details.

Action: Check the UPSTREAM job log for IBM error messages relating to this error. Correct the problem if possible.

UST280 TCP type CONNECT TO SOCKET=sssss,PORT=pppp,IPA=aaa.bbb.ccc.ddd

Reason: A connection has been made between UPSTREAM and IBM's TCP/IP. The socket number and port number used, and the network address (in dotted decimal format) are displayed. If “type” is MAIN, this is the UPSTREAM connecting to TCP/IP during initialization and the IPA is UPSTREAM's primary address (there may be others if your z/OS Storage Server has multiple TCP/IP connections to the network). If “type” is USER, this is a Client connecting to UPSTREAM and the address is that of the Client.

Action: None.

UST283 BYTES PER SECOND

Reason: An UPSTREAM performance test was requested from a Client. This message is the header on a histogram that shows the range of instantaneous data rates that were measured during that test.

Action: None.

UST284 BACKUP EXCEEDS MAXIMUM VOLUMES - BACKUP TERMINATED

Reason: A single tape backup file has required more than 255 tape volumes.

Action: The backup is terminated. To rerun the backup, you must reduce the number of tapes required. If the hardware supports it, you might use larger capacity tapes. If necessary, change the backup file specifications to reduce the amount of data to be backed up (you may need to break the backup into 2 pieces, under different profile names).

UST285 TARGET pcversion NAME=targname IS REGISTERED TO netname

Reason: A Client has used the z/OS Storage Server “Registered Name Service” to report that it has been configured with Client name “targname” (up to 16 characters). “netname” is “LU=luname” for VTAM/SNA Clients and is “IP=nnn.nnn.nnn.nnn..port” for TCP/IP-connected Clients. “pcversion” displays the version of UPSTREAM in use on the Client, if available. The target name can now be used with the TARGNAME= parameter of USTBATCH.

If the target name is being deleted from the table due to a request from the Client or from the z/OS Storage Server ISPF dialog, the additional text “ WAS DELETED” appears at the end of the message. The target name is no longer usable unless it is registered again. If the target name is marked for automatic UPSTREAM software updates, the additional text “AUTO-UPDATE” appears.

Action: None.

UST287* UPSTREAM TAPE UNIT NOT AVAILABLE, VARY ONE ONLINE OR REPLY 'RETRY', 'WAIT', CANCEL' OR 'DISPLAY'

Reason: To avoid allocation interlocks, UPSTREAM does dynamic allocation of tape drives with a flag indicating it is not to wait if no drives are available. An allocation received an error indicating that all eligible tape drives are offline or in use. This message is displayed on the system console as a WTOR.

Action: If the operator does not reply to the message, UPSTREAM retries the allocation at five second intervals; if the operator varies a drive online or a drive is de-allocated by another task, the allocation will succeed and the message is deleted. The operator may also reply:

RETRY

retry the allocation. The message is reissued if there are still no available drives.

WAIT

same as not replying except that the message is deleted.

CANCEL

fail the allocation, which will fail the backup.

DISPLAY

retry the allocation, allowing z/OS allocation recovery to take place. z/OS messages on the console will indicate which offline tape drives are eligible.

Warning: If you reply “DISPLAY” you must reply to the z/OS allocation messages promptly to avoid potential allocation interlocks.

UST288E I/O ERROR type BACKUP FILE CHECK z/OS LOG

Reason: A sequential backup or restore has encountered an I/O error on the backup file. “type” is either “WRITING TO” or “READING THE”. The backup or restore is interrupted.

Action: Check the z/OS job log of the z/OS Storage Server tasks for z/OS messages which may indicate the type of I/O error that occurred. It will probably not be possible to restart the backup, but you should be able to restore any files which were successfully written and recorded. If necessary, contact BMC Support for assistance.

UST289E ERROR DURING POINT TO A BACKUP FILE

Reason: A sequential restore has encountered an error issuing a POINT to position to a record in the backup file. The restore is interrupted. This may be due to an invalid pointer in the UPSTREAM repository.

Action: Execute the USTREGEN utility against this backup to refresh the pointers in the repository. If necessary, contact BMC Support for assistance.

UST290W HISTORY RECORD BYPASSED reason

Reason: An UPSTREAM history record was not recorded in the UPSTREAM catalog file for the reason indicated, which may be:

CATALOG NOT OPEN probably because it is being reorganized.

DUE TO CATALOG ERROR COMP=xxxxxxxx the “comp” is the VSAM RPL feedback word.

Action: The operation completed, only the history record was lost. If multiple catalog errors occur, you may need to reorganize the catalog file. If necessary, contact BMC Support for assistance.

UST291W ACQUIRING THE USERID OF USTBATCH BYPASSED REASON=reason

Reason: UPSTREAM attempted to extract the security userid from the address space of a USTBATCH job which has requested an UPSTREAM function, but the attempt was unsuccessful. Reason codes are:

1 – CROSS-MEMORY ALREADY SETUP indicates an internal error.

2 – AXSET MACRO ERROR indicates an internal error.

3 – ERROR FINDING USTBATCH TCB indicates that could not locate a TCB (Task Control Block) in the other address space. May indicate that the indicated address space was not really a batch job or TSO user.

4 – JOB PACK QUEUE ERROR indicates that the list of programs loaded in the address space could not be located. May indicate that the indicated address space was not really executing a batch job.

5 - PROGRAM NAME NOT USTBATCH indicates that UPSTREAM could not find a program called USTBATCH in the address space. May indicate that the address space was not really executing USTBATCH.

6 - USTBATCH IS NOT AUTHORIZED indicates that the USTBATCH program in the address space is not an authorized program. When USTBATCH is executed directly under TSO, this will occur unless USTBATCH is added to the list of authorized TSO programs.

7 - MISMATCH ON INTERNAL FIELD indicates a validation check failed.

8 - NO ACEE (SECURITY) POINTER indicates there was no ACEE (security control block) associated with the address space, so no userid could be extracted.

9 - NO USERID ON USTBATCH JOB indicates that there was no security userid stored in the ACEE.

A - USTBATCH NOT ON SAME CPU indicates that the USTBATCH job was not executing on the same z/OS image as the UPSTREAM online task, so the userid could not be extracted.

Action: Since a validated userid could not be extracted from the USTBATCH job, UPSTREAM requires that a security password be provided (as well as a userid) for validation. This security information could be specified at the Client or could be in the USTBATCH parameters. If a validated userid was extracted and it matched the userid associated with the USTBATCH request, no password would be necessary.

If necessary, contract BMC Support for assistance. Existing USTBATCH users might get this message and the resulting return code 4 in jobstreams that used to get RC=0.

UST292 BACKUP SIZE EXCEEDS DASD MAX SIZE - SWITCHING TO TAPE

Reason: An incremental MERGE backup was directed to sequential DASD, but the estimated size of the backup exceeded the DASDMAXSIZE= value in the profile, so the backup was directed to tape instead.

Action: None.

UPSTREAM Configurator Messages

UST301E NO APPLID FOUND IN “MAIN” RECORD - TERMINATING

Reason: While parsing the configuration input file “MAIN” record, the z/OS Storage Server Configurator, USTCONFG, was unable to locate the “APPLID=” parameter. The “APPLID” parameter is required in the configuration input file “MAIN” record.

Action: Add the “APPLID” parameter and rerun the z/OS Storage Server Configurator.

UST305W WSNAME/WSPREF MISSING IN COMMAND - RECORD BYPASSED:

Reason: While parsing a DEFINE/MODIFY/COPY statement, the z/OS Storage Server Configurator, USTCONFG, found no WSNAME= or WSPREF= parameter in the listed record.

Action: Correct the input configuration source file and rerun the z/OS Storage Server Configurator.

UST306W NEWNAME/NEWPREF MISSING IN COMMAND - RECORD BYPASSED:

Reason: While parsing a COPY statement, the z/OS Storage Server Configurator, USTCONFG, found no NEWNAME= or NEWPREF= parameter in the listed record.

Action: Correct the input configuration source file and rerun the z/OS Storage Server Configurator.

UST313E CONTINUATION STATEMENT EXPECTED - NOT FOUND

Reason: The previous statement indicated that it should continue on the next statement (trailing comma) but a valid continuation statement was not found.

Action: Correct the continuation syntax and rerun the z/OS Storage Server Configurator.

UST319W SUBSYS PARAMETER NOT FOUND - DEFAULTED TO UPSTREAM

Reason: This is a warning message. The z/OS Storage Server Configurator, USTCONFG, did not find a “SUBSYS=” parameter in the input configuration “MAIN” record. The “SUBSYS” parameter value has been defaulted to “UPSTREAM”.

Action: None.

UST322E NO CONFIGURATION RECORD GENERATED - FILE IS NOT USABLE

Reason: Due to catastrophic errors, the z/OS Storage Server Configurator, USTCONFG, was unable to generate the configuration table.

Action: Review the Configurator output log for errors, correct them, and rerun the z/OS Storage Server Configurator

UST323E VAULT CANNOT BE SPECIFIED ON RESERVED PROFILES

Reason: A DEFINE/MODIFY/COPY for one of the reserved profile names contained the VAULT parameter. This is not valid.

Action: Remove VAULT, and rerun the z/OS Storage Server Configurator.

UST324E DASDPREF/TAPEPREF MUST CONTAIN “?” MASK WITH VAULT OPTION

Reason: For profiles with the VAULT parameter specified, the DASDPREF= and TAPEPREF= parameters must contain a question mark “?” somewhere within the name, anywhere except as the first character of an index level. This is replaced with the copy number (1 to 9).

Action: Correct the prefix, or specify NOVAULT, and rerun the z/OS Storage Server Configurator.

UST325 nnnnnnnn PROFILE ENTRIES IN CONFIG ON mm/dd/yy AT hh:mm:ss

Reason: This in a informational message issued at the conclusion of a Configurator run. This message contains the count of profile entries in the configuration table after applying all updates from your current z/OS Storage Server Configurator input.

Action: None.

UST326E OPEN FOR CONFIGURATION FILE FAILED - ABEND IN PROGRESS

Reason: The z/OS Storage Server Configurator, USTCONFG, was unable to open the output configuration file.

Action: Review your JCL specifications and DCB attributes for the output configuration file, correct any errors, and re-run the z/OS Storage Server Configurator.

UST327E OPEN FOR INPUT SOURCE FILE FAILED - ABEND IN PROGRESS

Reason: The z/OS Storage Server Configurator, USTCONFG, was unable to open the input source configuration file.

Action: Review your JCL specifications and DCB attributes for the input source configuration file, correct any errors, and rerun the z/OS Storage Server Configurator.

UST328E UNABLE TO FIND “MAIN” RECORD - CONFIGURATOR TERMINATING

Reason: The z/OS Storage Server Configurator, USTCONFG, found the first input record was not a configuration “MAIN” record. It cannot continue.

Action: Correct the error and rerun the z/OS Storage Server Configurator.

UST329E CONFIGURATION FILE DEFINITION ERROR - LRECL MUST BE DEFINED AS 120

The configuration data set does not have proper DCB characteristics. It must be RECFM=FB and LRECL=120 (any blocksize a multiple of 120 is acceptable).

Action: Define a new configuration data set with proper characteristics.

Recommendation: Use the UPSTREAM ISPF dialog.

UST330W/E UNABLE TO OPEN DDNAME=ddname - MISSING OR MISSPECIFIED

Reason: USTCONFG was unable to open the indicated DDNAME. It may have been omitted or misspelled. If the file is required, this is an Error message, otherwise it is a Warning.

Action: If necessary, correct the USTCONFG JCL and resubmit.

UST331 ddname=dsname,VOL=volser

Reason: This informational message documents that the indicated DDNAME points to the indicated data set name, on the indicated volume.

Action: None.

UST332 BACKUP OF P=profilename COPY=n IS ENCRYPTED TYPE=encrypt_level KEY=key

Reason: This message is issued at the completion of an encrypted VAULT output operation. It indicates the copy of the backup data set produced in the prior UST655 message was encrypted using the specified encryption level.

Action: This message is informational only. It corresponds to an FDR178 message.

UST333E ** ENCRYPT ERROR REASON=

               ** DECRYPT ERROR REASON=

Reason: An error occurred during the encryption or decryption of a data set. The REASON code indicates the cause of the problem:

0

USTCRYPT NOT FOUND

1

DECRYPT KEY NOT SPECIFIED

2

NOT AUTHORIZED

3

UNSUPPORTED ENCRYPTTYPE

4

MASTERKEY IS INVALID

5

DECRYPT KEY IS INVALID/MISSING

6

DUPLICATE BYTE GENERATED

7

KEYFILE OPEN ERROR

8

KEYFILE NOT FORMATTED BLKSIZ=0

9

KEYFILE IS FULL

A

KEYFILE INTERNAL ID INVALID

B

KEYFILE READ/WRITE I/O ERROR

C

USTCRYPT PROGRAM HAS EXPIRED

D

KEYFILE NOT DEFINED

E

BACKUP NOT RECORDED IN KEYFILE

F

KEYFILE DYNALLOC ERROR

G

MASTERKEYID NOT FOUND

H

MASTERKEYID INVALID

M

MUST BE DECRYPTED WITH FDRCAMS

P

PUBLIC KEY ERROR - ERROR CODE=

Z

UNKNOWN REASON CODE

Action: Correct the problem indicated by the provided REASON code and retry the operation.

UST334E UNABLE TO CREATE KEYFILE ACEE - SAF RC=xx RACF RC=xx

                MISSING MASTERKEY

                INCOMPATIBLE KEYWORD(S) SPECIFIED

                SUBKEY VALUE NOT HEXADECIMAL OR KEY LENGTH NOT EXACTLY 32 BYTES

                CIPHERKEY VALUE NOT HEXADECIMAL OR KEY LENGTH NOT EXACTLY 32 BYTES

                AESKEY VALUE NOT HEXADECIMAL OR KEY LENGTH NOT EXACTLY 32, 48, OR 64 BYTES

                USTCRYPT DD MISSING OR OPEN ERROR

                INCOMPLETE CONTROL CARD - MISSING REQUIRED KEYWORD OPERAND

                INVALID KEY VALUE – ZERO

                KEY LENGTH MUST BE 48 BYTES WHEN ENCRYPTTYPE=AES192 IS SPECIFIED

                KEY LENGTH MUST BE 64 BYTES WHEN ENCRYPTTYPE=AES256 IS SPECIFIED

                KEY LENGTH MUST BE 32 BYTES WHEN ENCRYPTTYPE=AESES128/AESFAST IS SPECIFIED

                MASTERKEY LENGTH MUST BE EXACTLY 32 BYTES

Reason: This message is issued for the error conditions shown above.

Action: Correct the error situation according to the message content and retry the operation.

UST335E CONTROL STATEMENT ERROR NEAR REL LOCATION nn - REASON r - JOB TERMINATED

Reason: An error was found while reading a control statement from the USTCRYPT input. The REASON code below indicates the error found:

1

NO OPERANDS

3

INVALID OPERAND

6

MISSING CONTINUATION

8

BLANK OR COMMA AFTER =

9

VOLSER > 6 CHRS

A

REASON=A - MAXVOLS EXCEEDED

I

KEYWORD INVALID FOR OPERATION

J

BLANK STATEMENT

S

DUPLICATE KEYWORD

Action: Correct the input control statement and restart the facility.

UST336 CARD IMAGE – input statement

Reason: This message logs one input record in the USTCRYPT DD input stream.

Action: This message is informational only.

UST337E DYNAMIC ALLOCATION ERROR FOR KEYFILE COMP=cccc, CODE=nnnn,

INFO= iiii, DDNAME= name
Reason: This message indicates that the encryption/decryption module could not access the keyfile.

Action: Be sure the correct name is specified for the keyfile in the USTOPT table or in the USTCRYPT DD input stream. This file must be preformatted using the USTCRYFM utility and periodically reorganized.

UST338 ENCRYPTION INITIALIZATION SUCCESSFUL

Reason: This message is issued by the UPSTREAM main task during initialization to indicate that the encryption facility has been successfully established.

Action: This message is informational only. The absence of this message may indicate a problem.

UST339E PROFILE=aaaaaaaa REQUESTED ENCRYPTION WAS BYPASSED DUE TO SERVICE NOT ACTIVE OR FAILURE

               ENCRYPTION STARTUP FAILED - ENCRYPTION DISABLED

               ENCRYPTION STARTUP FAILED - ENCRYPTION MODULES NOT PRESENT

Reason: Encryption could not be enabled because the encryption facility was not available or not initialized by the UPSTREAM main task at start up.

Action: Make sure that message UST338 ENCRYPTION INITIALIZTION SUCCESSFUL was issued when the UPSTREAM started task initialized. Look for other messages in the USTLOG indicative of the problem.

UST342W DSNAME TOO LONG WITHOUT “GDG” SPECIFIED - RECORD BYPASSED:

Reason: The z/OS Storage Server Configurator, USTCONFG, found an invalid value specified for the “DASDPREF=” or “TAPEPREF=” parameter in the listed DEFINE/MODIFY/COPY record. The value specified exceeded the 19 allowable characters without the “DASDGDG” or “TAPEGDG” parameter also being specified.

Action: Correct the value or specify the appropriate GDG parameter, and rerun the z/OS Storage Server Configurator.

UST343W WARNING: “DASDBLK” NOT FOUND IN “MAIN” RECORD - DEFAULTING TO 27998

Reason: The z/OS Storage Server Configurator, USTCONFG, was unable to locate the “DASDBLK” keyword parameter in the configuration “MAIN” record. This message warns that when appropriate, the “DASDBLK” value will default to 27998.

Action: If this is not appropriate for your installation, add the DASDBLK parameter with the correct value and rerun the z/OS Storage Server Configurator.

UST344W DSNAME TOO LONG FOR RESERVED PROFILE - RECORD BYPASSED

Reason: On a DEFINE/MODIFY/COPY statement specifying a WSNAME= of one of the reserved profiles, the DASDGDG or TAPEGDG option was not specified, and the data set name prefix (DASDPREF= or TAPEPREF=) specified exceeds 26 characters.

Action: Correct the data set name and rerun the z/OS Storage Server Configurator.

UST345E “DASDPREF” REQUIRES “DASD” - RECORD BYPASSED

Reason: On a DEFINE/MODIFY/COPY statement, DASDPREF= was specified without DASD.

Action: Correct the parameters and rerun the z/OS Storage Server Configurator.

UST346E “DASDGDG” REQUIRES “DASDPREF=” AND “DASD” - RECORD BYPASSED

Reason: On a DEFINE/MODIFY/COPY statement, DASDGDG was specified without DASD and DASDPREF=.

Action: Correct the parameters and rerun the z/OS Storage Server Configurator.

UST347E INVALID VALUE SPECIFIED FOR xxxxxxxx - RECORD BYPASSED

Reason: An invalid value was specified for the parameter “xxxxxxxx”.

Action: See Section “USTCONFG Control Statements” for valid values. Correct the parameters and rerun the z/OS Storage Server Configurator.

UST348E “WSNAME/WSPREF” SPECIFIED IS A RESERVED NAME - ENTRY NOT ADDED

Reason: A DEFINE/MODIFY was entered which specified a profile name that may not be used.

Action: See Section “USTCONFG Control Statements” for valid values. Correct the parameters and rerun the z/OS Storage Server Configurator.

UST349E “DASDBLK” REQUIRES “DASD” AND “DSNPREF” - RECORD BYPASSED:

Reason: The z/OS Storage Server Configurator, USTCONFG, found the “DASDBLK” parameter in the listed record, but was unable to find the “DASD” and/or “DASDPREF” additional required parameters.

Action: Correct the parameters and rerun the z/OS Storage Server Configurator.

UST350E “GROUPID” MUST BE EXACTLY 2 ALPHA-NUMERIC CHARACTERS - RECORD BYPASSED:

Reason: The z/OS Storage Server Configurator, USTCONFG, found that the “GROUPID” parameter in the listed record did not have the correct syntax.

Action: Correct the parameters and rerun the z/OS Storage Server Configurator.

UST351E “DUNIT” REQUIRES “DASD” AND “DSNPREF” - RECORD BYPASSED:

Reason: The z/OS Storage Server Configurator, USTCONFG, found the “DUNIT” parameter in the listed DEFINE/MODIFY/COPY record, but was unable to find additional required parameters.

Action: Correct the “DEFINE” record definition and rerun the z/OS Storage Server Configurator.

UST352E “TUNIT” REQUIRES “TAPE” AND “DSNPREF” - RECORD BYPASSED:

Reason: The z/OS Storage Server Configurator, USTCONFG, found the “TUNIT” parameter in the listed DEFINE/MODIFY/COPY record, but was unable to find additional required parameters.

Action: Correct the parameters and rerun the z/OS Storage Server Configurator.

UST353E “TAPE” REQUIRES “TUNIT” AND “DSNPREF” - RECORD BYPASSED:

Reason: The z/OS Storage Server Configurator, USTCONFG, found the “TAPE” parameter in the listed record, but was unable to find additional required parameters.

Action: Correct the parameters and rerun the z/OS Storage Server Configurator.

UST354E “DASD” REQUIRES “DSNPREF/DASDPREF” - RECORD BYPASSED:

Reason: The z/OS Storage Server Configurator, USTCONFG, found the “DASD” parameter in the listed record, but was unable to find the “DSNPREF” or “DASDPREF” required parameter.

Action: Correct the parameters and rerun the z/OS Storage Server Configurator.

UST355E “DSNPREF” REQUIRES “TAPE” OR “DASD” - RECORD BYPASSED:

Reason: The z/OS Storage Server Configurator, USTCONFG, found the “DSNPREF” parameter in the listed DEFINE/MODIFY/COPY record, but was unable to find additional required parameters.

Action: Correct the parameters and rerun the z/OS Storage Server Configurator.

UST356E “GDG” REQUIRES “DSNPREF” AND “TAPE” OR “DASD” - RECORD BYPASSED:

Reason: The z/OS Storage Server Configurator, USTCONFG, found the “GDG” parameter in the listed DEFINE/MODIFY/COPY record, but was unable to find additional required parameters.

Action: Correct the parameters and rerun the z/OS Storage Server Configurator.

UST357E “STORCLAS” REQUIRES “DASD” - RECORD BYPASSED:

Reason: The z/OS Storage Server Configurator, USTCONFG, found the “STORCLAS” parameter in the listed record, but was unable to find additional required parameters.

Action: Correct the parameters and rerun the z/OS Storage Server Configurator.

UST358E “MGMTCLAS” REQUIRES “DASD” - RECORD BYPASSED:

Reason: The z/OS Storage Server Configurator, USTCONFG, found the “MGMTCLAS” parameter in the listed DEFINE/MODIFY/COPY record, but was unable to find additional required parameters.

Action: Correct the parameters and rerun the z/OS Storage Server Configurator.

UST359W “SORTUNIT” NOT FOUND IN MAIN RECORD - DEFAULTING TO “SYSDA”

Reason: The z/OS Storage Server Configurator was unable to find the “SORTUNIT” keyword parameter in the listed configuration “MAIN” record. The sort unitname is defaulted to “SYSDA” for any sequential tape restores performed.

Action: This message is mostly informational. If you do not intend doing any sequential tape backups and restores, or if the unitname of “SYSDA” is acceptable for temporary sort work data sets, you can safely ignore this message.

UST360E PROFILE NOT IN CONFIGURATION - CAN NOT UPDATE

Reason: A MODIFY/COPY statement was entered, but the WSNAME= or WSPREF= parameter specified a profile name that does not exist in the input configuration, so it cannot be processed.

Action: Change the MODIFY/COPY to a DEFINE or remove it and rerun the z/OS Storage Server Configurator.

UST361E ENQ CONTENTION FOR THE CONFIGURATION FILE. TRY AGAIN LATER.

Reason: The z/OS Storage Server Configurator, USTCONFG, found online UPSTREAM held the ENQ on the UPSTREAM configuration file and did not release it within a reasonable period of time. UPSTREAM only holds the ENQ while it is actually reading the configuration file, so this indicates that something is wrong.

Action: Rerun the z/OS Storage Server Configurator at a later time. If it still fails, you may have to terminate the UPSTREAM online task before running the z/OS Storage Server Configurator.

UST362E EXPDT= MUST BE 5 DIGIT NUMERIC - RECORD BYPASSED

Reason: EXPDT= did not have a 5-digit value in the format “yyddd”.

Action: Correct the parameter and rerun the z/OS Storage Server Configurator.

UST363E MEMBER DOES NOT EXIST IN CONFIGURATION DATASET

Reason: The member name specified on the USTCFGIN DD statement does not exist in the configuration PDS.

Action: Correct the USTCFGIN member name and rerun the z/OS Storage Server Configurator.

UST364W ONLY ONE “GLOBAL” DEFINE PERMITTED IN CONFIGURATION FILE

Reason: The z/OS Storage Server Configurator found multiple configuration entries with the reserved profile name “WSNAME=GLOBAL”.

Action: Correct your configuration input to contain only one “GLOBAL” definition record and rerun the z/OS Storage Server Configurator.

UST365E “GLOBAL” RECORD MUST BE FIRST IN CONFIGURATION

Reason: The z/OS Storage Server Configurator found the “WSNAME=GLOBAL” definition record was not the first record in the configuration file.

Action: Correct your configuration input file placing the “GLOBAL” definition record as the first “DEFINE” record of the file and rerun the z/OS Storage Server Configurator.

UST366 “GLOBAL” RECORD INCLUDED IN CONFIGURATION

Reason: This informational message documents that a DEFINE record with “WSNAME=GLOBAL” was found in the configuration file.

Action: None.

UST367W WARNING: NO “GLOBAL” RECORD FOUND IN CONFIGURATION

Reason: The z/OS Storage Server Configurator found no “GLOBAL” definition record in your input configuration file. This message is a warning only.

Action: None.

UST368 NO CHANGES MADE TO CONFIGURATION. FILE NOT REWRITTEN

Reason: The input configuration was not altered (perhaps because of syntax errors in configuration statements) so the output configuration was not written to DD statement name USTCONFG.

Action: None.

UST369E PROFILE ALREADY EXISTS CANNOT ADD TO CONFIGURATION

Reason: A DEFINE statement specified a WSNAME= or WSPREF= name that already exists in the input configuration

Action: None.

UST370 MAIN STATEMENT ACCEPTED. MAIN WILL BE ADDED TO CONFIGURATION

Reason: The MAIN statement passed syntax checking. The options are added to the output configuration.

Action: None.

UST371W DELETE “ALL” REQUEST INVALID. STATEMENT IGNORED

Reason: The DELETE statement specified “ALL” instead of a specific WSNAME= Client profile name. This is not allowed.

Action: Remove or correct the DELETE statement. If your intention is to delete the entire configuration file, delete the configuration data set or (if it is a PDS) delete the desired member.

UST372 DELETE REQUEST ACCEPTED. PROFILE WILL BE DROPPED FROM CONFIGURATION

Reason: This informational message indicates that the requested Client profile is deleted from the configuration.

Action: None.

UST373W DELETE FUNCTION FAILED. WORKSTATION NOT FOUND IN CONFIGURATION

Reason: The Client profile specified by WSNAME= was not found in the existing configuration and could not be deleted.

Action: Correct the Client profile name and resubmit. If necessary, use the PRINT function to display existing profile names.

UST374 REQUEST ACCEPTED. PROFILE WILL BE ADDED TO THE CONFIGURATION

Reason: This informational message indicates that the specified Client profile name is added to the configuration.

UST375W WARNING: WORKSTATION ALREADY DEFINED. PROFILE WILL BE REPLACED

Reason: The Client profile name specified on a DEFINE statement by WSNAME= already exists. The existing profile is deleted and redefined as specified by the DEFINE statement.

Action: If your intention was to replace the profile, no action is required. If you intended to modify an existing profile, but neglected to use the MODIFY statement instead of DEFINE, review the profile to be sure that all required options have been specified.

UST376W PRINT FUNCTION FAILED. WORKSTATION NOT FOUND IN CONFIGURATION

Reason: A PRINT statement specified a Client profile name which does not exist in the configuration.

Action: Correct the WSNAME= and resubmit.

UST377 PRINT FUNCTION COMPLETED

Reason: This informational message indicates that a PRINT function has completed successfully.

Action: None.

UST378W WARNING: “MAIN” RECORD ALREADY IN FILE. ABOVE STATEMENT IGNORED.

Reason: A MAIN statement was encountered in the USTCONFG input, and the configuration file is not NEW, i.e., an existing configuration is being modified. The MAIN statement is ignored.

Action: If your intention was to modify an existing configuration, you can ignore the message or remove the MAIN statement and resubmit. If you intended to create a new configuration, change your JCL to specify a new configuration data set or member and resubmit.

UST379W WARNING: MAIN STATEMENT ALREADY IN CONFIG - REPLACING MAIN STATEMENT

Reason: A MAIN statement was entered for an update to an existing configuration. All the original MAIN options are replaced by options (and defaults) on the new MAIN statement.

Action: None.

UST380W WARNING: NOTHING TO MODIFY - RECORD BYPASSED:

Reason: A MODIFY statement did not contain any operands indicating which attributes of the Client profile to modify. The MODIFY is ignored.

Action: If necessary, correct the MODIFY statement and resubmit.

UST381W WARNING: RECORD NOT FOUND IN CONFIG FILE CHANGING TO DEFINE

Reason: The Client profile name specified by WSNAME= on a MODIFY statement was not found in the configuration. The MODIFY is treated as a DEFINE and the profile is added to the configuration.

Action: Verify that the profile name is correct and that all required attributes have been specified. If necessary, DELETE the incorrect profile name and MODIFY the correct one.

UST382W DELETE 'GLOBAL' INVALID. STATEMENT IGNORED

Reason: A DELETE WSNAME=GLOBAL statement was encountered. You cannot delete the GLOBAL profile. The statement is ignored.

Action: If necessary, correct the input and resubmit.

UST383W WARNING: “GLOBAL” RECORD ALREADY IN FILE - ABOVE STATEMENT IGNORED

Reason: A DEFINE WSNAME=GLOBAL statement was encountered, and the GLOBAL profile already exists in the configuration. This DEFINE was ignored.

Action: Remove the DEFINE, or change the DEFINE to a MODIFY if you intend to change the attributes of the GLOBAL profile, and resubmit.

UST384W MODIFY REQUEST ACCEPTED. PROFILE WILL BE CHANGED IN CONFIGURATION

Reason: This informational message indicates that a MODIFY statement was successfully processed.

Action: None.

UST385W REQUEST FAILED. PROFILE NOT UPDATED IN THE OUTPUT CONFIGURATION

Reason: A MODIFY statement was rejected for some reason. The Client profile is not updated.

Action: Correct the MODIFY and resubmit.

UST386W PRINT REQUEST FAILED. CONFIGURATION FILE IS EMPTY.

Reason: A PRINT statement could not be executed because the configuration file does not contain a configuration definition.

Action: None.

UST387E INVALID MEMBER NAME, CONFIG FILE IS NOT A PDS

Reason: A member name was specified for the output configuration, but the configuration file is not a PDS.

Action: Specify a PDS for the output configuration or omit the member name.

UST388E PC DRIVEN CONFIGURATION UPDATE ERROR

Reason: The configuration was being updated from UPSTREAM at a Client, but an error occurred. The configuration was not updated.

Action: Correct the error, if possible, and update the configuration again.

UST389E CONFIGURATION ERROR - reason

Reason: An invalid parameter or another error was encountered. “reason” is a short description of the error.

Action: Correct the error and rerun the Configurator.

UST390 ACCEPTED CHANGES NOW APPLIED. CONFIGURATION FILE UPDATED SUCCESSFULLY

Reason: One or more changes have been successfully applied to the configuration and the configuration file has been rewritten with the new configuration.

UST391E SERIOUS CONFIGURATION PROCESSOR CHAIN ERROR. ABEND IN PROGRESS

Reason: A serious error in the configuration file format has been detected.

Action: Save the abend dump and contact BMC Support for assistance.

UST392E SERIOUS ERROR DURING PRINT PROCESSING. ABEND IN PROGRESS

Reason: A serious error in the configuration file format has been detected.

Action: Save the abend dump and contact BMC Support for assistance.

UST399E error text from control statement processor

Reason: The z/OS Storage Server control statement processor detected a syntax or usage error in a USTCONFG or USTRPORT control statement. The text indicates the error and where on the control statement it occurred. The job is terminated.

Action: Correct the control statement and resubmit. See Section “USTCONFG Control Statements” for details on syntax and usage of USTCONFG control statements or Chapter 21 “Reporting with USTRPORT” for Reporting on details of USTRPORT control statements.

USTREGEN and USTRPORT Utility Messages

UST400E* *** ONLINE UPSTREAM IS ACTIVE - CANNOT CONTINUE ***

Reason: The USTREGEN utility found the online UPSTREAM component active upon starting.

Action: Stop Online UPSTREAM while the REGEN utility is run or run REGEN under the Started Task.

UST401E* USTREGEN UNABLE TO OPEN LOG FILE - TERMINATING

Reason: The USTREGEN utility was unable to open the Log File (DD statement USTLOG). For obvious reasons, this is written as a WTO to the system console only.

Action: Verify that the USTLOG DD statement is correctly specified.

UST402E* USTREGEN APF AUTHORIZATION CHECK FAILED - CANNOT CONTINUE

Reason: The USTREGEN utility detected it was not being run as an z/OS APF authorized program.

Action: Verify that the load library containing the USTREGEN utility is currently APF authorized.

UST403E* OPEN FOR CATALOG CLUSTER FAILED - TERMINATING

Reason: USTREGEN was unable to open the VSAM UPSTREAM Catalog cluster.

Action: Review your JCL to be sure it is correct. Review the USTREGEN job log for error messages that may indicate the cause of the problem.

UST404E* OPEN FOR FILE-INFO CLUSTER FAILED - TERMINATING

Reason: USTREGEN was unable to open the VSAM UPSTREAM File-Information cluster.

Action: Review your JCL to be sure it is correct. Review the USTREGEN job log for error messages that may indicate the cause of the problem.

UST405E DYNAMIC ALLOCATION ERROR R15=rr CODE=cccc INFO=iiii

Reason: USTREGEN encountered an error trying to dynamically allocate the backup file to be read.

Action: See message UST095E for details on the error codes and possible actions.

UST406E* OPEN FOR ARCHOLD DD FAILED - TERMINATING

Reason: USTREGEN was unable to open the ARCHOLD file.

Action: Review your JCL to be sure it is correct. Review the USTREGEN job log for error messages that may indicate the cause of the problem.

UST407E BACKUP DATASET NOT FOUND DSN=dsname

Reason: USTREGEN was executing as a sub-task of the UPSTREAM online task, as the result of a console command. The backup data set specified in that command was not cataloged.

Action: Verify that the backup data set name was properly specified, and that the name is currently cataloged in the z/OS catalogs.

UST408E* VSAM ERROR - SNAP-002 TAKEN

Reason: USTREGEN encountered an error on one of the VSAM clusters. A diagnostic SNAP dump with ID 002 was taken to the USTSNAP DD, if present. It is accompanied by message UST409E with VSAM diagnostic codes.

Action: See message UST409E.

UST409E VSAM error indicators

Reason: This message is logged by the VSAM error diagnosis routine. It contains specific error codes from the VSAM “RPL” control block and also indicates the location in USTREGEN of the error.

Action: Refer to the IBM VSAM Macro Reference or Macro Instructions for Data Sets manual (depending on the level of your operating system) to understand the error codes reported. The job log or SYSLOG may contain additional diagnostic messages. If you are unable to resolve the problem, contact BMC Support.

UST410 UPSTREAM REGEN PROCESS STARTED

Reason: This informational message indicates that the USTREGEN process has begun.

Action: None.

UST411 ARCHOLD DSN: dsname

Reason: This informational message indicates the “dsname” of the ARCHOLD data set.

Action: None.

UST412 ARCHOLD VOL: volser

Reason: This informational message indicates the volume serial of the ARCHOLD data set.

Action: None.

UST413 FILE INFORMATION RECORDS UPDATED: nnnnnnn ADDED: mmmmmmmm

Reason: This informational message indicates the number of records in the FILE-INFO data set that were updated and added during this execution of USTREGEN.

Action: None.

UST414 FILE DATA RECORDS READ: nnnnnnnn

Reason: This informational message indicates the number of data records read from the ARCHOLD data set.

Action: None.

UST415 UPDATE FILE-INFO: profilename versiondate filename

Reason: The FILE-INFO record for the indicated profilename, versiondate, and filename has been updated with data from the ARCHOLD data set.

Action: None.

UST416E MISSING FILE-INFO RECORD FOR PROFILE=profilename locator

Reason: File descriptors were not found on the backup tape for the indicated profilename.

Action: Contact BMC Support for assistance.

UST417E C-RECORD MISSING ON BACKUP

Reason: A catalog record was not found on the backup tape.

Action: Contact BMC Support for assistance.

UST418E C-RECORD ERROR IN CONTROL FILE

Reason: USTREGEN had an error reading a control record from the online repository.

Action: Contact BMC Support for assistance.

UST419E F-RECORD IN CONTROL FILE MISSED UPDATE FILE=filename

Reason: A file record was not updated properly.

Action: Contact BMC Support for assistance.

UST420E F-RECORD GET PREVIOUS VERSION NOT FOUND FILE=filename

Reason: An expected file record was not found.

Action: Contact BMC Support for assistance.

UST421 USTREGEN COMPLETED SUCCESSFULLY

Reason: USTREGEN completed with no errors.

Action: None.

UST422W USTREGEN COMPLETED WITH ERRORS

Reason: USTREGEN completed with warnings or errors.

Action: Review the USTREGEN messages for the specific error.

UST423E F-RECORD TIMESTAMP NOT FOUND ON BACKUP FILE=filename

Reason: An expected file record was not found.

Action: Contact BMC Support for assistance.

UST424 VAULT REGEN STARTED FOR DSN=dsname

Reason: USTREGEN determined that the backup data set being read was the control file for a vault tape created by USTVAULT. The UPSTREAM control records are updated to point to the secondary (vault) copy of the backups, as recorded in that control file.

Action: None.

UST425 UPSTREAM REGENED nnnnnn BACKUP VERSIONS

Reason: USTREGEN updated the control records for the indicated number of versiondates.

Action: None.

UST426E UNKNOWN RECORD TYPE data

Reason: USTREGEN found a record that it could not identify in the backup data set being read. Part of the record is displayed.

Action: Contact BMC Support for assistance.

UST427E VAULT BACKUP DATA SET NOT CATALOGED VOL=vvvvvv DSN=dsname

Reason: USTREGEN was reading a vault control file created by USTVAULT but a backup data set pointed to by the control records was no longer cataloged in the system catalog. The backup would not be usable.

Action: USTREGEN does not add the records for that backup to the online repository. If the backup file still exists, you may be able to manually re-catalog it and run USTREGEN again.

UST428W BACKUP CATALOGED TO ANOTHER VOLUME - REGEN FROM LASTEST COPY ONLY CATALOGED TO cccccc VAULT COPY IS vvvvvv DSN=dsname

Reason: USTREGEN was reading a vault control file created by USTVAULT but a backup data set pointed to by the control records is currently cataloged in the system catalog to a different tape volume. “cccccc” is the volser in the catalog, while “vvvvvv” is the volser in the vault records. This probably occurred because you vaulted a copy of the same backup file multiple times. For example, an incremental MERGE BACKUP normally appends data to the previous incremental. If you vault that backup every day, you have multiple vaulted copies with each copy containing an additional day's data. You only need to REGEN the most recent vault copy of that backup.

Action: None.

UST429 VAULT BACKUP REGENED PROF=profile DATE=versiondate DSN=dsname

Reason: USTREGEN was reading a vault control file created by USTVAULT. The records for the indicated backup (profile, versiondate, and backup dsname) have been successfully updated in the UPSTREAM repository.

Action: None.

UST430 UPSTREAM BACKUP REGENED PROF=profile VERDATE=versiondate FLAGS=X'xxxx'

Reason: USTREGEN was reading an UPSTREAM backup. The records for the indicated backup (profile and versiondate) have been successfully updated in the UPSTREAM repository.

Action: None.

UST480E FILEINFO POINT FAILED KEY=kkkkkkkkkkkkkkkk

Reason: A VSAM POINT in the FILE-INFO data set for the specified key failed.

Action: Contact BMC Support for assistance.

UST481E FILEINFO GET FAILED KEY=kkkkkkkkkkkkkkkk

Reason: A VSAM GET in the FILE-INFO data set for the specified key failed.

Action: Contact BMC Support for assistance.

UST482E CATALOG CLUSTER POINT FAILED KEY=kkkkkkkkkkkkkkkk

Reason: A VSAM POINT in the catalog data set for the specified key failed.

Action: Contact BMC Support for assistance.

UST483E CATALOG CLUSTER GET FAILED KEY=kkkkkkkkkkkkkkkk

Reason: A VSAM GET in the catalog data set for the specified key failed.

Action: Contact BMC Support for assistance.

UST488E* error text

Reason: USTRPORT encountered an error opening or processing some data set that made it impossible to continue. This may be due to missing DD statements. The text indicates the error.

Action: Correct the error and resubmit the USTRPORT job.

UST494 USTRPTPC - REPORT STARTED

Reason: A USTRPORT request was received from a Client.

Action: None.

UST495 USTRPTPC - REPORT ENDED

Reason: A USTRPORT request from a Client was completed.

Action: None.

UST496 USTRPTPC - REPORT CANCELED BY USER OR SEND ERROR

Reason: A USTRPORT request from a Client was terminated because of user request at the Client or because of a transmission error.

Action: None.

UST498E NO ENTRIES FOUND MATCHING SELECTION CRITERIA

Reason: USTRPORT did not find any records which met the criteria specified on SELECT statements.

Action: Correct the SELECT statements and resubmit your USTRPORT request.

UST499 TOTAL HISTORY RECORDS READ: nnnnnnnn TOTAL RECORDS SELECTED: mmmmmmm

Reason: For RPTYPE=HISTORY or BACKUP, shows the total records read and the total records selected for reporting.

Action: None.

USTMAINT and USTREORG Utility Messages

UST500 *** UPSTREAM USTMAINT PROCESS STARTED ***

Reason: This informational message indicates that USTMAINT has begun execution.

Action: None.

UST501E* USTMAINT UNABLE TO OPEN LOG FILE - TERMINATING

Reason: The USTMAINT utility was unable to open the USTLOG data set. It does not continue processing. For obvious reasons, this message is issued as a WTO to the system console only.

Action: Verify that you have correctly specified the USTLOG data set in your UPSTREAM JCL.

UST503E* OPEN FOR CATALOG CLUSTER FAILED - TERMINATING

Reason: USTMAINT was unable to open the VSAM UPSTREAM Catalog cluster.

Action: Review your UPSTREAM JCL to be sure it is correct. Review the UPSTREAM job log for error messages which may indicate the cause of the problem.

UST504E* OPEN FOR FILE-INFO CLUSTER FAILED - TERMINATING

Reason: USTMAINT was unable to open the VSAM UPSTREAM File-Information cluster.

Action: Review your UPSTREAM JCL to be sure it is correct. Review the UPSTREAM job log for error messages which may indicate the cause of the problem.

UST505 PURGING: PROFILE=profilename DATE/TIME=versiondate

Reason: USTMAINT is purging a backup version with the indicated profilename and versiondate. This message is informational only.

Action: None.

UST506 DSN: data set name WAS DELETED - nnnnnnnn FILE RECORDS ERASED

Reason: USTMAINT is purging a backup version having found the preceding named data set is no longer cataloged on the z/OS system. This message is issued along with message UST505 and is informational only.

Action: None.

UST507 nnnnnnnn OF nnnnnnnn HISTORY RECORDS ERASED FOR DATES EARLIER THAN mm/dd/yy

Reason: History records are being kept in the UPSTREAM catalog data set (MAXHIST= was specified or default other than 0 in the configuration). USTMAINT has deleted obsolete history records older than MAXHIST days, calculated as “mm/dd/yy”.

Action: None.

UST508E* VSAM ERROR - SNAP 002 TAKEN

Reason: USTMAINT encountered an error on one of the VSAM clusters. A diagnostic SNAP dump with ID 002 was taken to the USTSNAP DD, if present. It is accompanied by message UST509E with VSAM diagnostic codes.

Action: See message UST509E.

UST509E VSAM error indicators

Reason: This message is logged by the VSAM error diagnosis routine. It contains specific error codes from the VSAM “RPL” control block and also indicates the location in USTREGEN of the error.

Action: Refer to the IBM VSAM Macro Reference or Macro Instructions for Data Sets manual (depending on the level of your operating system) to understand the error codes reported. The job log or SYSLOG may contain additional diagnostic messages. If you are unable to resolve the problem, contact BMC Support.

UST510 UPSTREAM MAINT COMPLETED -- nnnnnnnn VERSION RECORDS ERASED mmmmmmmm FILE RECORDS ERASED

Reason: This informational message indicates the number of records erased from the UPSTREAM catalog due to USTMAINT processing.

Action: None.

UST511E UPSTREAM LOCATE ERROR COMP=cccc DSN=dsname

Reason: UPSTREAM issued a catalog LOCATE for a backup data set, and the return code was other than 0 (successful) and 8 (not found).

Action: Investigate the catalog entry for the indicated data set; correct or delete it as appropriate.

UST512 n OF m REGISTERED NAME RECORDS ERASED FOR DATES EARLIER THAN mm/dd/yy

Reason: This informational message indicates that of the “m” records in the Registered Name table, “n” of them have not been referenced or updated in the last 90 days and have been deleted.

Action: None.

UST550 REORG BEGUN FOR DDNAME ddname

Reason: A F UPSTREAM,REORG DD=ddname console command was entered to request dynamic reorganization of the UPSTREAM data set referenced by the indicated DDNAME. No other tasks were active (except possibly other reorganizations), so the requested reorganization was initiated.

Action: None.

UST551W REORG BYPASSED -- DDNAME ddname NOT FOUND

Reason: The ddname indicated on a F UPSTREAM,REORG DD=ddname console command is not one of the ddnames that can be reorganized.

Action: Re-enter the command, specifying DD=USTCATLG, USTFILEI, or USTFILEC.

UST524W REORG BYPASSED -- PROFILE ddname NOT IN CONFIGURATION

Reason: A profile whose name matches the ddname to be reorganized was not found in the UPSTREAM configuration currently active. The reorganization is not done.

Action: Update the configuration to specify a profile with a name matching the ddname to be reorganized. It must specify DASD or TAPE/TAPECOMP and is used to dynamically allocate a backup file for the reorganization.

UST553W REORG BYPASSED -- PROFILE ddname DOES NOT ALLOW SEQUENTIAL BACKUP

Reason: The profile named “ddname” in the currently active UPSTREAM configuration is not enabled for either DASD or TAPE/TAPECOMP, so the backup file for the reorganization could not be allocated. The reorganization is not done.

Action: Update the named profile in the configuration to specify either DASD or TAPE or TAPECOMP, along with an appropriate DSNPREF.

UST554E DYNALLOC ERROR: R15=rrrrrrrr CODE=cccc INFO=iiii

Reason: USTREORG received an error indication trying to dynamically allocate the backup file for a data set reorganization.

Action: Verify that the specifications for DASDPREF/TAPEPREF and DUNIT/TUNIT in the profile used for the reorganization are correct. If DASD, verify that the unit or volser specified by DUNIT have enough space for the data set. See message UST095E for information on interpreting these error codes.

UST555 BACKUP DATA SET ALLOCATED, DSN=dsname

Reason: USTREORG has successfully dynamically allocated the named backup file, which is used to backup the data from the UPSTREAM data set being reorganized. It may be on tape or disk.

Action: If the reload of the UPSTREAM data set fails, you probably need to delete and redefine the data set (possibly with more space) and manually REPRO this backup file back into the data set using the USTCAMS utility. This file is retained until deleted by your DASD or tape management software, or until manually deleted.

UST556E OUTPUT OPEN FOR BACKUP DATA SET FAILED

Reason: The OPEN for OUTPUT on the backup file by USTREORG has failed. The UPSTREAM data set being reorganized has not been modified.

Action: Check the joblog of the UPSTREAM online task for IBM error messages. Correct the cause if possible.

UST557E INPUT OPEN FOR BACKUP DATA SET FAILED

Reason: USTREORG has completed the backup of the UPSTREAM data set being reorganized, and has closed the backup file, but the reOPEN of the backup file for input has failed. The data set being reorganized has not been modified.

Action: Check the joblog of the UPSTREAM online task for IBM error messages. Correct the cause if possible.

UST558E general VSAM error diagnostic information

Reason: USTREORG has received an error reading or writing the UPSTREAM data set being reorganized. The message contains specific error indicators from the VSAM RPL. If REQ=00 is displayed, this was a read error; the backup was not completed and the data set has not been modified; however, there is probably an error in that data set which should be corrected. If REQ=01, this was a write error and the data set is probably unusable.

Action: You probably need to shutdown UPSTREAM and correct the error. If this was a write error, the backup file contains a backup of the data set. See IBM manual VSAM Macro Reference or Macro Instructions for Data Sets (depending on the level of your operating system) to understand the error codes.

UST559E OPEN OR CLOSE OF CLUSTER FAILED

Reason: An OPEN or CLOSE of the UPSTREAM data set being reorganized by USTREORG has failed. The data set is probably unusable.

Action: You probably need to shutdown UPSTREAM and correct the error. Check the joblog of the UPSTREAM online task for IBM error. Check the joblog of the UPSTREAM online task for IBM error messages.

UST560E I/O ERROR ON BACKUP DATA SET

Reason: An I/O error (input or output) has occurred on the backup file being used by USTREORG during the reorganization of a UPSTREAM data set. If this is followed by message UST565E*, then this was a READ error during the RELOAD and the data set being reorganized is probably unusable.

Action: You probably need to shutdown UPSTREAM and correct the error. Check the joblog of the UPSTREAM online task for IBM error messages.

UST562* REORG SUCCESSFUL FOR DDNAME ddname -- RELOADED WITH:

Reason: The reorganization of the UPSTREAM data set pointed to by the named ddname has been successfully reorganized by USTREORG. It is now reOPENed by the main task, and UPSTREAM again accepts requests for backups and restores (unless another reorganization is still running).

Action: None.

UST563 nnnnnnnnnnnnnnn DATA-BLOCKS; nnnnnnnnnnnnnnn DATA-BYTES

Reason: This message follows message UST562* on the UPSTREAM log and indicates the number of blocks and bytes rewritten to the data set that was reorganized.

Action: None.

UST564W* REORG UNSUCCESSFUL FOR DDNAME ddname -- UPSTREAM FILE STILL USABLE

Reason: An error occurred during the reorganization of the UPSTREAM data set indicated, but it was before USTREORG began reloading the data set, so it is still usable, and UPSTREAM continues.

Action: Re-execute the reorganization after correcting the error, if possible.

UST565E* REORG UNSUCCESSFUL FOR DDNAME ddname -- UPSTREAM FILE NOT USABLE - MUST BE RELOADED

Reason: An error occurred during the reorganization of the UPSTREAM data set indicated, while USTREORG was reloading the data set. The data set is probably not usable. This is displayed on the console as a non-scrollable message to ensure that the operator does not overlook it.

Action: You probably need to shutdown UPSTREAM and correct the error. You may be able to correct it by manually reloading the file from the backup just created by USTREORG. You may also need to redefine the failing data set with more space.

UST566W IMMEDIATE SHUTDOWN REQUESTED - REORG TERMINATED

Reason: The operator has requested an immediate shutdown of UPSTREAM. The USTREORG operation in progress was terminated. The file being reorganized may or may not be usable.

Action: Determine by looking at subsequent UST564W* or UST565E* messages whether or not the file being reorganized is still usable. If it is not usable, reload the file from you most current backup of that file.

UST567 BACKUP DATASET SUCCESSFULLY CREATED

Reason: USTREORG has successfully created its backup data set. The reload of the file being reorganized now begins.

Action: None.

UST568E* REORG FAILED WITH SYSTEM ABEND Ssss

Reason: The USTREORG task has failed with the indicated system abend.

Action: USTREORG terminates. If the abend code is other than a Sx37, an abend dump is taken before termination. If the failure occurred during the reload phase, message UST565E* is issued (indicating that the file has become unusable); otherwise message UST564W* is issued.

UST570E* USTBKPRT UNABLE TO OPEN REPORT FILE - TERMINATING

Reason: USTBKPRT had a failure opening its report file (USTRPRT). Probably the DD statement was missing or incorrectly specified.

Action: Correct the JCL and resubmit.

UST571E BSAM ERROR: USTBKUP DATASET - synad info

Reason: An I/O error occurred reading the USTBKUP data set in the USTBKPRT backup report utility. The “synad info” is the description of the error generated by the IBM SYNADEF macro. This may be accompanied by an IBM message in the joblog of the USTBKPRT job. The sequential backup data set may be damaged or unusable.

Action: If this is a sequential tape backup, try a different tape drive. It the error cannot be corrected, the backup is not usable.

UST572E* ERROR READING USTBKUP DATASET - MAY BE EMPTY

Reason: An I/O error or end of file occurred reading the first block of the USTBKUP data set in the USTBKPRT backup report utility. This may mean that the data set was created but was never written into due to some error during the backup.

Action: If this is a sequential tape backup, try a different tape drive. It the error cannot be corrected, the backup is not usable.

UST573E *** ERROR OPENING USTBKUP DATASET - TERMINATING ***

Reason: An error occurred opening the USTBKUP data set in the USTBKPRT backup report utility. This is probably accompanied by an IBM message in the joblog of the USTBKPRT job. This may mean that the USTBKUP DD statement was omitted or the DD statement name misspelled, or that the dsname of the backup data set was misspelled.

Action: Determine the error from the IBM message, and correct the error is possible.

USTMIGRT, USTVAULT, and USTMERGE Messages

UST602E ONLINE UPSTREAM IS ACTIVE - OPERATOR REPLIED xxxxxx

Reason: This message is printed after the operator replies to the UST602E message on the console. “xxxxxx” is either “GO” or “CANCEL”. If CANCEL, USTARCH terminates.

Action: None.

UST603E* OPEN FOR CATALOG CLUSTER FAILED - TERMINATING

Reason: The Archive Utility, USTARCH, was unable to open the Repository Catalog Cluster.

Action: Review your JCL to be sure it is correct. Review the job log for error messages that may indicate the cause of the problem.

UST604E* OPEN FOR FILE-INFO CLUSTER FAILED - TERMINATING

Reason: The Archive Utility, USTARCH, was unable to open the Repository File-Information Cluster.

Action: Review your JCL to be sure it is correct. Review the job log for error messages that may indicate the cause of the problem.

UST605E* OPEN FOR FILE-DATA CLUSTER FAILED - TERMINATING

Reason: The Archive Utility, USTARCH, was unable to open the Repository File-Data Cluster.

Action: Review your JCL to be sure it is correct. Review the job log for error messages that may indicate the cause of the problem.

UST606E* OPEN FOR ARCHOLD DD FAILED - TERMINATING

Reason: The Archive Utility was unable to open the prior Archive data set, “ARCHOLD” DD statement. This message can be issued only if USTARCH is operating in MERGE mode.

Action: Review your JCL to be sure it is correct. Review the USTARCH job log for error messages that may indicate the cause of the problem.

UST607E* OPEN FOR OUTPUT ARCHNEW DD FAILED - TERMINATING

Reason: The z/OS Storage Server Archive Utility, USTARCH, was unable to open the new Archive data set, “ARCHNEW” DD statement.

Action: Review your JCL to be sure it is correct. Review the USTARCH job log for error messages that may indicate the cause of the problem.

UST608E* VSAM ERROR

Reason: The utility received a VSAM error indication. This message is accompanied by message UST609E containing the VSAM error codes.

Action: None.

UST609E VSAM error indicators

Reason: This message is logged by the VSAM error diagnosis routine. It contains specific error codes from the VSAM “RPL” control block and also indicates the location in the utility of the error.

Action: Refer to the IBM VSAM Macro Reference or Macro Instructions for Data Sets manual (depending on the level of your operating system) to understand the error codes reported. The job log or SYSLOG may contain additional diagnostic messages. If you are unable to resolve the problem, contact BMC Support.

UST610E* DEVTYPE CHECK FOR ddname DD FAILED - TERMINATING

Reason: The DEVTYPE macro for ARCHNEW or ARCHOLD, to determine the device type, has failed.

Action: Be sure that the DD statements for ARCHNEW and ARCHOLD are correct.

UST611E* ARCHNEW DEVICE IS NOT TAPE - TERMINATING

Reason: The z/OS Storage Server Archive utility, USTARCH, has determined the device for the “ARCHNEW” DD statement is not a TAPE device.

Action: Change your JCL to specify a valid TAPE device to contain the new Archive data set and rerun the USTARCH job.

UST612E* APF AUTHORIZATION CHECK FAILED - TERMINATING

Reason: The z/OS Storage Server Archive utility, USTARCH, has determined it is not running as an z/OS APF authorized program.

Action: Verify that the load library containing the USTARCH utility is currently z/OS APF authorized.

UST613E* UNABLE TO MOUNT CORRECT ARCHOLD TAPE - ARCHIVE ABORTED

Reason: The z/OS Storage Server Archive utility, USTARCH, had an error reading the ARCHOLD tape volume. It is not possible for it to continue. This message can occur only if USTARCH is operating in MERGE mode.

Action: Be sure that the ARCHOLD DD statement points to the correct old archive tape. Contact BMC Support if required.

UST614E FEOV VOLUME SWITCH - ARCHOLD DATASET

Reason: The z/OS Storage Server Archive utility, USTARCH, is issuing the FEOV request to switch to the next volume in the ARCHOLD DD statement tape set. This message is informational only.

UST615W* WARNING: ARCHOLD DEVICE IS NOT TAPE

Reason: The z/OS Storage Server Archive utility, USTARCH, has determined that the ARCHOLD DD statement in it's execution JCL does not indicate a tape device. ARCHOLD must be either a tape or DUMMY. If it is not DUMMY, message UST616E* is also issued. This message can occur only if USTARCH is operating in MERGE mode.

Action: If the ARCHOLD DD statement is specified as DUMMY, USTARCH runs without reading ARCHOLD. This is correct if this is the first time you have run USTARCH. Otherwise, correct the ARCHOLD DD statement and rerun USTARCH.

UST616E* ARCHOLD DEVICE IS NOT DUMMY - TERMINATING

Reason: The z/OS Storage Server Archive utility, USTARCH, has determined that the device specified in the ARCHOLD DD statement is not a tape device and is not specified as “DUMMY”. USTARCH does not continue with the archival process. This message can occur only if USTARCH is operating in MERGE mode.

Action: Correct your JCL and rerun USTARCH.

UST618E* LOCATE FAILED FOR ARCHOLD DD - TERMINATING

Reason: The z/OS Storage Server Archive utility, USTARCH, was unable to issue an z/OS catalog “LOCATE” request for the specified data set name in the ARCHOLD DD statement. This message can occur only if USTARCH is operating in MERGE mode.

Action: Review your execution JCL to be sure you have specified the correct data set name in the ARCHOLD DD statement. Correct your JCL and rerun USTARCH.

UST619E UNABLE TO LOCATE FILE DATA RECORDS:

Reason: This is the first in a series of error messages from the archive utility, USTARCH. It indicates that the archive utility was unable to find the file data records in the ARCHOLD file. This may be the result of a prior BSAM I/O error encountered reading or writing this ARCHOLD tape volume. The archive process continues, but the file data for this file is no longer accessible.

Action: None.

UST620E profilename versiondate filename

Reason: This message contains additional information for message UST619E.

Action: None.

UST621E ARCHNEW BSAM WRITE ERROR - ABEND U0609

Reason: The z/OS Storage Server Archive utility, USTARCH, detected an unrecoverable BSAM write error while attempting to write a block to the ARCHNEW DD. It is not possible for it to continue. USTARCH abends with a U0609 abend. There are additional z/OS BSAM error messages in the UPSTREAM z/OS Storage Server job log.

Action: Contact BMC Support.

UST622E ARCHNEW BSAM WRITE ERROR - ABEND U0610

Reason: The z/OS Storage Server Archive utility, USTARCH, detected an unrecoverable BSAM write error while attempting to write a block to the ARCHNEW DD. It is not possible for it to continue. USTARCH abends with a U0610 abend. There are additional z/OS BSAM error messages in the z/OS Storage Server job log.

Action: Contact BMC Support.

UST623E BSAM ERROR: ddname DATASET dsname I/O ERROR text, DSN=datasetname

Reason: The utility detected a fatal BSAM error accessing the data set in the DD statement named. It is not possible for it to continue. There are additional z/OS BSAM error messages in the z/OS Storage Server job log.

Action: Contact BMC Support.

UST624E REPOSITION ARCHOLD TAPE VOL

Reason: An error occurring positioning the “old” Archive Data set. The Archived file being processed is skipped, and the ARCHOLD data set is repositioned to the beginning.

Action: This is an internal error; contact BMC Support.

UST625E UNABLE TO FIND THE cccccccc CONFIGURATION ENTRY

Reason: The utility was being run as a sub-task of the z/OS Storage Server online task, and the current configuration did not contain a profile with the appropriate name (USTARCH, USTMIGxx, USTMERxx, or USTVLTxx).

Action: Update the configuration with an appropriate reserved profile and re-submit the request.

UST626E UNIT NAME INVALID IN cccccccc CONFIGURATION ENTRY

Reason: No value was specified for TUNIT= in the reserved profile used for this utility operation.

Action: Update the reserved profile in the configuration and re-submit the request.

UST627E DYNALLOC ERROR: R15=rrrrrrrr CODE=cccc INFO=iiii

Reason: The utility received an error indication trying to dynamically allocate the output tape when executing as a sub-task of the z/OS Storage Server online task.

Action: Verify that the specifications for TAPEPREF and TUNIT in the associated reserved profile are correct. See message UST095E for information on interpreting these error codes.

UST628W INTERRUPTED BACKUP BYPASSED: profile versiondate

Reason: The indicated backup was interrupted, and is not archived until it is restarted and successfully completed.

Action: None.

UST630 program process STARTED

Reason: This informational message indicates that the indicated program has started the indicated process, for example, “USTARCH ARCHIVE” or “USTMIGRT MIGRATE”.

Action: None.

UST633 ED: nnnnnnnnnnn VERSION(S) BYPASS

Reason: Indicates the number of version records that were bypassed because they were flagged as “DELETE VERSION”.

Action: None.

UST634 ARCHIVED: nnnnnnnnnnn type

Reason: Indicates the number of versions, files, and data records moved to the ARCHNEW data set during USTARCH processing.

Action: None.

UST635 ERASED: nnnnnnnn DATA RECORDS

Reason: Indicates the number of data records erased from the UPSTREAM online repository during USTARCH processing.

Action: None.

UST636 ARCHNEW DSN: dsname

Reason: Indicates the data set name of the ARCHNEW data set.

Action: None.

UST637 ARCHNEW VOL: volser

Reason: Indicates the volume serial of the ARCHNEW data set.

Action: None.

UST638 ARCHOLD DSN: dsname

Reason: Indicates the data set name of the ARCHOLD data set.

Action: None.

UST639 ARCHOLD VOL: volser

Reason: Indicates the volume serial of the ARCHOLD data set.

Action: None.

UST649E function REQUEST INVALID REASON=reason REQ: request

Reason: The request to start USTMIGRT, USTMERGE, USTVAULT, or USTSCHED could not be processed for the reason indicated by “reason” that consists of brief explanatory text, including:

GROUP ID NOT SPECIFIED indicates that the MODIFY command parameter did not contain a valid 2-character group ID, such as VAULTxx.

BYTE AFTER COMMAND NOT BLANK that the MODIFY command parameter (MIGRTxx, MERGExx, or VAULTxx) was not followed by a blank.

KEYWORD IS INVALID indicates the MODIFY command parameter (MIGRTxx, MERGExx, or VAULTxx) was followed by an unrecognized keyword.

KEYWORD EXCEEDS MAXIMUM LENGTH indicates the MODIFY command parameter (MIGRTxx, MERGExx, or VAULTxx) was followed by a keyword longer than the maximum permitted.

KEYWORD VALUE IS BLANK indicates the MODIFY command parameter (MIGRTxx, MERGExx, or VAULTxx) was followed by a keyword with no value after it.

KEYWORD AREA EXCEEDS MAX indicates the MODIFY command parameter (MIGRTxx, MERGExx, or VAULTxx) was followed by a keyword with value longer than the maximum permitted.

COPY= VALUE CANNOT BE 1 indicates that COPY=1 was specified on a VAULTxx command. The copy 1 backup is the original backup, COPY= must have some other value (usually 2 through 9).

Action: Correct the syntax of the command and reissue it.

UST650E function BYPASSED REASON=reason DSN=backupdsn

Reason: USTMIGRT, USTMERGE, or USTVAULT bypassed processing of the backup data set indicated by “backupdsn” for the reason indicated by “reason” that consists of a reason number and brief explanatory text. Many of these reasons indicate an I/O error or inconsistency in the UPSTREAM repository data sets and are usually accompanied by additional messages detailing the error. Reason codes are:

1 – C-RECORD DOES NOT EXIST

indicates an internal error.

2 – C-RECORD NOT TYPE 81

indicates an internal error.

3 – BACKUP CATALOGED TO TAPE

indicates that UPSTREAM's records indicated the backup was on disk but the z/OS catalog shows it on tape. The backup may have been copied to tape with IEBGENER or some other copy utility outside of UPSTREAM.

4 – C-RECORD PUT VSAM ERROR

see VSAM error message.

5 – BACKUP WAS INTERRUPTED

indicates that USTMIGRT bypassed a restartable-interrupted backup.

6 – BACKUP IS NOT CATALOGED

indicates a backup recorded by UPSTREAM is not in the z/OS catalog. This might occur if the backup was expired and uncataloged recently but USTMAINT has not yet been run to delete it from UPSTREAM.

7 – LOCATE ERROR COMP=X'cccc'

indicates that a catalog locate has failed.

8 – FILE CATALOGED TO MIGRAT

indicates that the disk backup has been archived by ABR or HSM; the backup is not recalled to disk.

9 – C-RECORD GET VSAM ERROR

see VSAM error message.

A – C-REC GET-UPDATE VSAM ERR

see VSAM error message.

B – S-REC GET-UPDATE VSAM ERR

see VSAM error message.

C – S-RECORD PUT VSAM ERROR

see VSAM error message.

D – F-REC GET-UPDATE VSAM ERR

see VSAM error message.

E – F-RECORD PUT VSAM ERROR

see VSAM error message.

F – I/O ERROR ON BACKUP FILE

indicates an I/O error on the output. See the UST623E message.

G – MORE THAN 254 BACKUP VOLUMES

indicates that a single tape file created required more than 254 tape volumes, which cannot be handled.

H – DEBLOCKING ERROR ON BACKUP

indicates a corrupted backup data set.

I – INSUFFICIENT STORAGE

indicates there is not sufficient free memory in the UPSTREAM online region to complete this operation. Increase the region if possible, restart UPSTREAM, and try again, or run the request at a time when fewer UPSTREAM operations are active.

J – MULTIPLE VERSION BACKUP

indicates that the utility encountered a disk backup data set that contained backups from multiple versiondates; this should occur only if a full MERGE BACKUP was done to disk with COPYINCR. Change the profile to remove COPYINCR, since USTMIGRT combines the backups into one file.

K – NAME MISSING COPY MASK “?”

indicates that although the associated profile is enabled for vaulting, the backup data set name in the profile does not contain a question mark “?” for the copy number.

L – COPY VALUE NOT 1 AT OFFSET

indicates that the copy number in the data set name of the input backup (at the position reserved by a “?” in the profile) is not “1”. Contact BMC Support for assistance.

M – BACKUP IS A DEFERRED MERGE

indicates that the backup is not processed by USTMIGRT or USTVAULT because it is a full MERGE BACKUP taken with DEFER=MERGE and USTMERGE has not yet been run against it.

N – INSUFFICIENT STORAGE

see reason I.

O – DEFER BACKUP OVER 20 VOLUMES

indicates that when USTMERGE was trying to add deferred files to the end of a deferred MERGE BACKUP already on tape, that backup was cataloged to over 20 tape volumes.

P – DEFER BACKUP NOT 1ST FILE

indicates that when USTMERGE was trying to add deferred files to the end of a deferred MERGE BACKUP already on tape, that backup was not cataloged as file 1 on the tape.

Q – OVER nn VERSIONS IN BACKUP

indicates that the input backup file contains backups for more than “nn” unique versiondates. The utility cannot handle this backup.

R – INVALID RECORD LENGTH

indicates that an invalid record was encountered.

T – FILE TRANSFER BACKUP

indicates that a backup selected was actually a file transfer, not a backup.

U – ONLY VAULTED COPY EXISTS

indicates that only a vault copy of the backup was found.

Action: If necessary, contact BMC Support for assistance.

UST651 BACKUP SELECTED FOR operation PROFILE=profilename DSN=backupdsn

Reason: The indicated disk backup under the indicated profile was selected for “migration”, “merging” or “vaulting” to tape.

Action: None.

UST652E ALLOCATE/OPEN FOR BACKUP FAILED DSN=backupdsn

Reason: An error occurred dynamically allocating or opening the indicated disk backup data set. There may be additional UPSTREAM or IBM messages indicating the specific cause.

Action: If the problem can be corrected, rerun the utility. If necessary, contact BMC Support for assistance.

UST653E action FOR file FAILED DSN=backupdsn

Reason: An error occurred on the indicated tape backup data set. “action” may be ALLOCATE/OPEN, CLOSE, or ADD S-RECORD. “file” may be OUTPUT TAPE or CONTROL FILE (the latter for USTVAULT only). There may be additional UPSTREAM or IBM messages indicating the specific cause.

Action: If the problem can be corrected, rerun the utility. If necessary, contact BMC Support for assistance.

UST654 BACKUP WAS SCRATCHED FROM source PROFILE=profile DSN=backupdsn

Reason: If “source” is DASD, a disk backup was successfully copied to tape and the disk backup data set named was scratched from disk. If “source” is TAPE, a tape backup was copied onto a new tape by USTMIGRT and the input tape backup data set named was uncataloged.

Action: None.

UST655 BACKUP PROF=profile D=versiondate operation TO DSN=tapebackupdsn

Reason: The utility has successfully completed the indicated operation on the backup described by “profile” and “versiondate”. The input backup data set is identified in the UST651 message. It was copied to the tape backup data set indicated. UPSTREAM records have been updated to point to the new backup data set.

Action: None.

UST656E type REQUEST FAILED COMP=X'ffff00001111' PROF=profile DSN=backupdsn

Reason: An operation against the indicated backup data set, under the indicated profile, failed. “type” may be SCRATCH (delete disk backup data set), CATALOG (catalog tape data set), or RECATLG (update tape data set catalog). COMP contains the contents of R15 “ffff”, R0 “0000” and R1 “1111”. There may also be an IBM message in the UPSTREAM job log with more information on the error. If you get this message for SCRATCH on a given data set, but not for CATALOG or RECATLG, the migration was successful but the backup is left on disk. If a CATALOG/RECATLG error occurs, the z/OS catalog was not updated to point to the tape, and a USTMAINT execution might delete the records of this backup. These errors are NOT likely to occur

Action: For a SCRATCH error, try to manually delete the data set from disk (IEHPROGM SCRATCH). For a CATALOG/RECATLG error, try to manually catalog the tape data set (IDCAMS DEFINE NONVSAM) using the information from the UST660 message (check the UPSTREAM joblog to see if the tape backup data set extended to additional tape volumes). If you need assistance, contact BMC Support.

UST657E operation TERMINATED DUE TO VSAM ERROR

Reason: An error has occurred reading or updating the UPSTREAM online repository data sets. Message UST609E is also printed detailing the error. The repository may be damaged.

Action: Contact BMC Support.

UST658E utility CANNOT BE EXECUTED AS A BATCH PROGRAM - USE command UNDER USTMAIN

Reason: You attempted to execute PGM=USTMIGRT, USTMERGE, or USTVAULT in a batch job or under TSO.

Action: Use the F UPSTREAM command to initiate the utility.

UST659E type NOT ENABLED IN profile CONFIGURATION ENTRY

Reason: The reserved configuration profile, USTMIGxx, USTMERxx, or USTVLTxx, was not properly enabled for tape backups. The tape parameters in that profile are used to allocate the tape drive and create a dummy (empty) file at the beginning of that tape, followed by the migrated or vaulted backups. For USTVAULT, “type” may also be DASD, since vaulting requires that the profile be enabled for both tape and disk backups.

Action: Update the profile entry in the configuration.

UST660 operation TO type BACKUP VOL=volser FILESEQ=filsq DSN=tapebackupdsn

Reason: The utility has successfully opened the tape backup data set named. “volser” is the first (or only) tape volume serial, and “filsq” is the file sequence number. If “type” is TAPE, then it has created a new tape data set; if it is PREV, it added data to the previously created tape data set.

Action: None.

UST661 NEW type TAPE MOUNTED VOL=volser FILESEQ=filsq DSN=tapebackupdsn

Reason: The utility filled the previous output tape. The indicated tape volume was mounted to continue the output of the indicated tape backup data set.

Action: None.

UST662E operation MISSED UPDATE FILE=filespec

Reason: The utility has copied a disk backup to tape, but while updating UPSTREAM's records for the backup, it discovered that the named file is recorded as being in that backup, yet the file was not encountered while copying the backup. In other words, UPSTREAM has a record of a file that is not in the backup. The utility continues updating the rest of the records.

Action: This error should not occur, but if it does, contact BMC Support for assistance.

UST663 operation: vvvvvvv VERSION(S) fffffffff FILES ddddddd DIRS rrrrrrrrrr DATA BLOCKS kkkkkkkkkk KBYTES wwwwwww FORWARD

Reason: The utility copied this total number of versiondates, files, directories, blocks, and kilobytes. FORWARD is the number of backups merged forward and appears only for USTMERGE.

Action: None.

UST664 type BACKUP TAPE NAME IS backupdsn

Reason: USTMIGRT, USTVAULT, or USTMERGE has successfully written the dummy (empty) data set as file 1 on the output tape, using the tape name specification in the corresponding special profile entry in the UPSTREAM configuration. The actual name is “backupdsn”. You may need to use this name in your tape management system for vaulting or retention purposes.

Action: None.

UST665 CONTROL FILE DATA SET NAME IS dsn

Reason: USTVAULT created the vaulting control file on disk with the indicated data set name. At the end of the vaulting operation, this control file is copied to the vault tape.

Action: None.

UST666E CONTROL FILE FAILED TO GET PUT ON TAPE REASON=reason

Reason: USTVAULT had an error copying the vault control file to the vault tape, for the reason indicated.

Action: Contact BMC Support for assistance.

UST667 CONTROL FILE COPIED TO TAPE FILE=ffff VOL=vvvvvv

Reason: USTVAULT has successfully copied the vault control file to the vault tape, as file “ffff” on tape volser “vvvvvv”.

Action: None.

UST668 CONTROL FILE LEFT ON DASD BY REQUEST

Reason: USTVAULT has left a copy of its control file on DASD, as requested by an option.

Action: None.

UST669 OPERATOR CANCELLED MOUNT FOR VAULT

Reason: The operator replied “CANCEL” to a request to mount a tape for USTVAULT. An UST652E message is also issued, and the vaulting operation is terminated.

Action: None.

UST670E I/O OR LOGICAL ERROR FOR BACKUP FILE - CHECK z/OS LOG DSN=backupdsn

Reason: An error occurred opening or reading the indicated backup data set. There may be additional UPSTREAM or IBM messages indicating the specific cause.

Action: If the problem can be corrected, rerun the utility. If necessary, contact BMC Support for assistance.

UST671 MERGED: bbb BACKUPS fff FILES ddd DIRS bbb DATA BLOCKS eee DEFER FILES

Reason: USTMERGE has completed processing. These are statistics about the total data processed.

Action: None.

UST672E MERGE PREVIOUS BACKUPS MISSING FOR DEFERRED PROFILE=profile

Reason: USTMERGE found records for the named profile, indicating that deferred files should be found in previous backups for that profile, but the indicated previous backups cannot be found in the UPSTREAM repository. They have expired or been deleted.

Action: None.

UST673 MIGRATE FORWARD ENDED FOR PROFILE DUE TO FULL BACKUP

Reason: USTMIGRT was copying incremental backups from a backup file but encountered a full backup at the end of that file. Since this is the end of the data required, processing for that profile was completed.

Action: None.

UST674 HI-SPEED LOCATE VOL=volume FROM=blocknum TO=blocknum IN seconds SECONDS

Reason: An informational message. To expedite processing USTMERGE skipped to the starting location of the next client file to be processed.

Action: None.

HI-SPEED LOCATE VOL=volume FROM=blocknum TO=blocknum IN seconds SECONDS FAILED

Reason: An error message. USTMERGE posted an error when skipping forward to the starting location of the next client file to be processed.

Action: Review any preceding messages in the z/OS Storage Server log file and the z/OS system log (SYSLOG) to determine the actual reason for the error. Contact BMC Support for assistance if necessary.

HI-SPEED LOCATE SKIPPED tapeblocks TAPE BLOCKS IN seconds SECONDS

Reason: An informational message. To expedite processing USTMERGE skipped forward to the next block required for processing.

Action: None.

UST675W OPEN/CLOSE/EOV ERROR - CHECK MVS LOG DSN=dsn

Reason: Utility processing (USTMERGE MIGRATE VAULT) posted an error processing a tape volume for the named data set.

Action: Review any preceding messages in the z/OS Storage Server log file and the z/OS system log (SYSLOG) to determine the actual reason for the error. Contact BMC Support for assistance if necessary.

UST676E MISSING DATA RECORDS BLK=blknum1 blknum2

Reason: USTVAULT Backup data set is corrupted. This may be due to an I/O error or hardware malfunction when the data was written. Where blknum1 is the block number as recorded in the UPSTREAM repository, and blknum2 is the block number indicated in the record on tape.

Action: To work around this issue, do a first time full backup of the profile that was being processed and vault the new backup. Should the error reoccur, contact BMC Support.

UST677W WARNING CONTROL FILE ENCRYPTION BYPASSED DUE TO PROFILE NOT SET

Reason: USTVAULT posts this warning if at least one profile in the vault was encrypted but encryption was NOT enabled for the Vault Control File.

Action: None.

UST678 PROFILE=profile BYTES=kilobytes KBYTES files=FILES

Reason: Utility processing (USTMERGE MIGRATE VAULT) posted the number of KB and files processed for the named profile.

Action: None.

UST679W dupfiles DUP FILES directory_structure

Reason: USTMERGE. This is an informational message for diagnostic purposes. It represents the number of duplicate directory structures transmitted in the backup. There is at least one duplicate for each higher-level directory for directories having two or more sub-directories.

Action: None.

UST680 profile INDEX SORT sortsec SEC mergesec SEC files FILES

Reason: This is an informational message for diagnostic purposes. MERGE processing posts the amount of CPU time used in the sort logic of the Merge, the amount of CPU time used processing the merge portion of the backup, and the number of files.

Action: None.

USTBATCH Utility Messages

UST700E INITIALIZATION FAILED - REASON = text

                [OPEN INPUT FILE USTPARM FAILED]|

                [APF AUTHORIZATION CHECK FAILED]'

Reason: USTBATCH was unable to initialize due to one of the reasons specified in text. The job terminates with a non-zero return code.

Action: Verify that your batch JCL is correct, that the USTPARM data set is of the correct type, and that the UPSTREAM STEPLIB is APF authorized and execute USTBATCH again.

UST701E VALUE FOR “APPLPREF” MUST BE 5 CHARACTERS

Reason: USTBATCH found an invalid value for the “APPLPREF” parameter in the input stream. The job terminates with a non-zero return code.

Action: Verify that the APPLPREF parameter value is 5 characters long and execute USTBATCH again.

UST702E VALUE FOR “USAPPL” INVALID

Reason: USTBATCH found an invalid value specified for the USAPPL parameter in the input stream. The job terminates with a non-zero return code.

Action: Verify that the USAPPL parameter value is 8 characters long or less, and execute USTBATCH again.

UST703E TASKLIM VALUE ERROR

Reason: USTBATCH found an invalid value specified for the TASKLIM parameter in the input stream. The job terminates with a non-zero return code.

Action: Correct the TASKLIM parameter and execute USTBATCH again.

UST704E VALUE FOR “TARGLU” EXCEEDS 8 CHARACTERS

Reason: USTBATCH found an invalid value specified for the TARGLU parameter in the input stream. The parameter is ignored and USTBATCH continues looking for valid parameters.

Action: Correct the TARGLU parameter and execute USTBATCH again.

UST705E VALUE FOR “TARGLU” INVALID

Reason: USTBATCH found an invalid value specified for the TARGLU parameter in the input stream. The parameter is ignored and USTBATCH continues looking for valid parameters.

Action: Correct the TARGLU parameter and execute USTBATCH again.

UST706E PREVIOUS RETRY VALUE TOO LONG

Reason: USTBATCH found an invalid value specified for the MAXRETRY, APPLRETRY or TMAXRETRY parameter in the input stream. The parameter is ignored and USTBATCH continues looking for valid parameters.

Action: Correct the retry parameter and execute USTBATCH again.

UST707E PREVIOUS RETRY VALUE INVALID

Reason: USTBATCH found an invalid value specified for the MAXRETRY, APPLRETRY or TMAXRETRY parameter in the input stream. The parameter is ignored and USTBATCH continues looking for valid parameters.

Action: Correct the retry parameter and execute USTBATCH again.

UST708W WARNING: “APPLPREF” DEFAULTED TO “UPSTR”

Reason: USTBATCH was unable to locate a value for the “APPLPREF” parameter in the input stream. The parameter takes its default value of “UPSTR”.

Action: If this is incorrect, specify the APPLPREF parameter and execute USTBATCH again.

UST709W WARNING: “USAPPL” DEFAULTED TO “UPSTREAM”

Reason: USTBATCH was unable to locate a value for the “USAPPL” parameter in the input stream. The parameter takes its default value of “UPSTREAM”.

Action: If this is incorrect, specify the USAPPL parameter and execute USTBATCH again.

UST710E “TARGLU”, “TARGNAME”, “TCPTARG”, OR DNSNAME PARAMETER NOT FOUND

Reason: USTBATCH was unable to locate any “TARGLU”, “TCPTARG” or “TARGNAME” required parameter in the input stream and is terminating.

Action: Add the TARGLU, TCPTARG, TARGNAME, or DNSNAME parameter and execute USTBATCH again.

UST711W WARNING: “TPNAME” NOT VALID FOLLOWING A TCPIP TARGET - IGNORED

Reason: The TPNAME= parameter is only valid following a TARGLU= parameter for a VTAM APPC target Client. It is ignored if it follows a TCPTARG= for a TCP/IP Client.

Action: None.

UST712E TARGET OR DNSNAME MUST PRECEED WSPARM

Reason: The TARGNAME, DNSNAME OR TCPTARG parameter must precede the WSPARM parameter in the USTBATCH input stream.

Action: Correct the positioning of the input parameters and execute USTBATCH again.

UST713E “WSPARM” VALUE INVALID

Reason: USTBATCH has detected an invalid value specified for the “WSPARM” parameter in the input stream. The parameter is ignored and USTBATCH continues looking for valid parameters.

Action: Correct the WSPARM parameter and execute USTBATCH again.

UST714E UNABLE TO LOCATE AN AVAILABLE VTAM ACB NAME

Reason: The application name built by USTBATCH from APPLPREF plus “nnn” (e.g., UPSTR001) was either not defined to VTAM or already in use by another application.

Action: Verify that your “APPLPREF” parameter specifies a valid prefix in agreement with your definitions in the VTAM APPL definition member for z/OS Storage Server. If not, correct the value and resubmit the USTBATCH job. You may need to increase the number of VTAM application definitions available for use with USTBATCH.

UST715E VTAM SETLOGON REQUEST FAILED

Reason: USTBATCH has received an error indication after issuing the VTAM “SETLOGON” request to enable session setup. This message is followed by message UST719E containing the applicable VTAM error codes.

Action: Use these error codes to resolve the problem.

UST716W* USTBATCH COMPLETED WITH WARNINGS

Reason: The USTBATCH job has completed with warning-level errors.

Action: Review the USTBATCH log file to determine the warnings issued, and whether they were acceptable.

UST717E* USTBATCH COMPLETED WITH ERRORS

Reason: The USTBATCH job has completed with errors.

Action: Review with USTBATCH log file to determine the errors that have occurred.

UST718* USTBATCH COMPLETED SUCCESSFULLY

Reason: The USTBATCH job has completed successfully.

Action: None.

UST719E VTAM error codes and indicators

Reason: This message follows a descriptive error message and contains the applicable VTAM error codes relating the error described.

Action: Consult IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST720E ALLOCATION FAILURE - BE SURE UPSTREAM TASK IS ACTIVE

Reason: USTBATCH has received a VTAM allocation failure while attempting to connect to the UPSTREAM online task. For errors other than an allocation failure, the text of the message is “APPC CNOS ERROR”.

Action: Be sure that the UPSTREAM online task is active.

UST721E APPC ALLOCATE TO APPL aaaaaaaa REQUEST FAILED

Reason: USTBATCH has received a VTAM error indication after issuing the APPC ALLOCATE request to the online UPSTREAM started task.

Action: Communication error codes are reported in a following message. Consult IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST722E APPC SEND-DATA RUN-FUNCTION REQUEST FAILED

Reason: USTBATCH has received a VTAM error indication after issuing the APPC SEND-DATA request to the online UPSTREAM started task.

Action: Communication error codes are reported in a following message. Consult IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST723E APPC SEND-DATA RUN-FUNCTION-PARAM REQUEST FAILED

Reason: USTBATCH has received a VTAM error indication after issuing the APPC ALLOCATE request to the online UPSTREAM started task.

Action: Communication error codes are reported in a following message. Consult IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST724E APPC CONFIRM REQUEST FAILED

Reason: USTBATCH has received a VTAM error indication after issuing the APPC CONFIRM request to the online UPSTREAM started task.

Action: Communication error codes are reported in a following message. Consult IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST725E RECEIVE FOR EVENT TYPE-90 FAILED

Reason: USTBATCH has received a VTAM error indication after issuing the APPC RECEIVE-DATA request to the online UPSTREAM started task.

Action: Communication error codes are reported in a following message. Consult IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST726E RECEIVE FOR EVENT TYPE-91 FAILED

Reason: USTBATCH has received a VTAM error indication after issuing the APPC RECEIVE-DATA request to the online UPSTREAM started task.

Action: Communication error codes are reported in a following message. Consult IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST727 message text from the target workstation

Reason: This message contains message text sent by the target Client LU. This message is actually issued by the UPSTREAM LU.

Action: If it indicates an error, review the UPSTREAM log on the Client for additional information as to the cause of the error.

UST728 ACB aaaaaaaa OPENED TO VTAM

Reason: USTBATCH has successfully located and opened an ACB to VTAM, using application name “aaaaaaaa”. This message is informational only.

Action: None.

UST729 APPC ALLOCATE TO aaaaaaaa SUCCESSFUL

Reason: USTBATCH has successfully allocated its LU 6.2 conversation to the online z/OS Storage Server started task using application name “aaaaaaaa”. This message is informational only.

Action: None.

UST730E PREVIOUS RETRY VALUE INVALID

Reason: USTBATCH found the MAXRETRY, APPLRETRY or TMAXRETRY value specified in the input stream was not numeric. The parameter is ignored and USTBATCH continues looking for valid parameters.

Action: Correct the retry parameter and execute USTBATCH again.

UST731E - REASON=nnn, text [, R=RETRY/RERUN, C=CANCEL]

Reason: USTBATCH encountered a processing error and issues this message in response to a user having specified an ERRWTO or ERRWTOR keyword in the input parameters. The values for the REASON field are defined as follows:

4

USTBATCH cannot establish or maintain communications between itself and the UPSTREAM Started Task.

8

The UPSTREAM Started Task cannot establish or maintain communications between itself and the specified UPSTREAM remote Client.

12

This reason code occurs if any error is encountered on the connection

Action: Evaluate the reason code supplied in the message, take appropriate corrective action, and optionally reply “R” to RETRY or “C” to CANCEL the pending request.

UST732E LOGMODE VALUE INVALID

Reason: USTBATCH found an invalid value specified for the LOGMODE parameter in the input stream. The job terminates with a non-zero return code.

Action: Correct the LOGMODE parameter and execute USTBATCH again.

UST733W WARNING: USING DEFAULT LOGMODE NAME “#INTER”

Reason: USTBATCH was unable to locate the LOGMODE parameter in the input stream, and is defaulting the value to “#INTER”. This message is informational.

Action: If this is not correct, specify the LOGMODE= parameter and execute USTBATCH again.

UST734 REQUEST SENT TO ONLINE INITIATOR FOR targetname

Reason: The USTBATCH job has completed sending one request for the Client address or name indicated to the z/OS Storage Server online initiator. It has requested confirmation. This message is informational only.

Action: None.

UST735 REQUEST CONFIRMED BY ONLINE INITIATOR

Reason: USTBATCH has received positive confirmation to the request last sent to the z/OS Storage Server online initiator. This message is informational only.

Action: None.

UST736E REQUEST NOT CONFIRMED (MESSAGE FOLLOWS):

Reason: USTBATCH has received a negative indication to its confirmation request. This message is followed by an indicative message from the z/OS Storage Server online initiator or from the Client itself.

Action: None.

UST737E TPNAME FOUND, BUT NO TARGET ID SPECIFIED

Reason: USTBATCH found a value specified for the TPNAME parameter in the input stream; but no TARGLU parameter was found preceding it. The parameter is ignored and USTBATCH continues looking for valid parameters.

Action: Correct the values and resubmit the USTBATCH job.

UST738E TPNAME VALUE TOO LONG

Reason: USTBATCH found an invalid value specified for the TPNAME parameter in the input stream. The associated TARGLU= parameter is ignored and USTBATCH continues looking for valid parameters.

Action: Correct the TPNAME parameter and execute USTBATCH again.

UST739E INVALID TPNAME VALUE FOUND

Reason: USTBATCH found an invalid value specified for the TPNAME parameter in the input stream. The associated TARGLU= parameter is ignored and USTBATCH continues looking for valid parameters.

Action: Correct the TPNAME parameter and execute USTBATCH again.

UST740E INVALID TCP ADDRESS AND/OR PORT SPECIFIED

Reason: USTBATCH found an invalid value specified for the TCPTARG parameter in the input stream. The parameter is ignored and USTBATCH continues looking for valid parameters.

Action: Correct the TCPTARG parameter and execute USTBATCH again.

UST741E INVALID VALUE FOUND FOR “CONV=”, NOWAIT,NOKEEP USED

Reason:USTBATCH found an invalid value specified for the CONV= parameter in the input stream. The parameter is ignored and USTBATCH continues looking for valid parameters.

Action: Correct the CONV parameter and execute USTBATCH again.

UST742I CONTINUED STATEMENT TOO LONG

Reason: USTBATCH encountered continuation statements that exceeded it maximum length. The parameter is ignored and USTBATCH continues looking for valid parameters.

Action: Correct the continued statement.

UST743E INVALID “TARGNAME” PARAMETER FOUND

Reason: USTBATCH found an invalid value specified for the TARGNAME parameter in the input stream. The parameter is ignored and USTBATCH continues looking for valid parameters.

Action:Correct the TARGNAME parameter and execute USTBATCH again.

UST744W NO AVAILABLE VTAM ACBNAMES - ENTERING RETRY

Reason:USTBATCH attempted to find a free VTAM application name starting with the prefix specified by APPLPREF (or the default of UPSTR), but all such application names defined to VTAM are in use and APPLRETRY=0 was not specified.

Action: USTBATCH attempts to find an available VTAM application every 5 seconds until the retry limit specified by APPLRETRY is reached (default is 240).

UST745E UPSTREAM TASK AT “MAXTASKS” - INITIATING RETRIES

Reason: USTBATCH connected to the UPSTREAM online tasks but UPSTREAM reported that it is already at its maximum task limit and TMAXRETRY= was specified.

Action: USTBATCH tries to initiated its request every 5 minutes until it is accepted or until the retry limit specified by TMAXRETRY is reached.

UST746E RETRY COUNT EXHAUSTED

Reason: One of the USTBATCH retry parameters (indicated by a preceding message) was exceeded. The requested operation was not initiated.

Action:None.

UST746E NO RETRIES SPECIFIED

Reason:One of the USTBATCH retry parameters (indicated by a preceding message) was specified as or defaulted to zero (0). The requested operation was not initiated.

Action: None.

UST747[E]* PROCESS COMPLETED - RETURN CODE=nnn,TARGET=target

Reason: The requested operation at the target Client “target” completed with the indicated return code. If the return code is non-zero, the message number is UST747E, otherwise it is UST747. This message is issued only if CONV=WAIT is specified in the USTBATCH parameters. If WTOCOMP is also in the USTBATCH parameters, it is also printed on the system console by a WTO.

Action: None.

UST748E INVALID RECORD BYPASSED:

Reason:A control statement was input to USTBATCH which was not recognized. The invalid record, printed after the message, is ignored.

Action: None.

UST749 status display

Reason: A “F jobname,STA” console command was issued to a USTBATCH job. This message indicates the requests currently queued or active in that job.

Action:None.

UST750E* USTBATCH COMMAND INVALID OR CANNOT BE ACCEPTED AT THIS TIME

Reason:A STOP(P) or MODIFY(F) console command was issued to a USTBATCH job, but either the parameter was invalid or USTBATCH is not accepting console commands. Commands can only be accepted if CONV=WAIT was specified in the USTBATCH parameters.

Action: None.

UST751* TERMINATING REQUEST ID = nnnn

Reason:A “F jobname,TERM ID=nnnn” console command was issued to a USTBATCH job. The request with ID number “nnnn” is being terminated.

Action: None.

UST752* STOP SCHEDULED - CONFIRM IN PROGRESS

Reason:A “P jobname” console command was issued to a USTBATCH job, but USTBATCH is currently waiting for UPSTREAM to confirm a request. USTBATCH terminates as soon as the request is confirmed.

Action:None.

UST753* STOP REQUEST RECEIVED

Reason:A “P jobname” console command was issued to a USTBATCH job. USTBATCH terminates.

Action: None.

UST754E* ID VALUE FOR TERM REQUEST INVALID OR NOT FOUND

Reason:A “F jobname,TERM ID=nnnn” console command was issued to a USTBATCH job, but either the parameter “nnnn” was not a valid 4-digit number, or no USTBATCH request was found with that ID number.

Action: None.

UST755 USTBATCH Vn.n.n STARTED

Reason:The USTBATCH job running the indicated version has started.

Action:None.

UST756 REQUEST COMPLETED, REQ=request

Reason: An “F jobname,request” console command was issued to a USTBATCH job. The request has been processed.

Action: None.

UST757W WARNING: NO KEYWORD VERIFICATION WILL BE PERFORMED

Reason:VERIFY=NO was specified; invalid Client parameter names are not detected.

Action: None.

UST758E PREVIOUS RECORD KEYWORD INVALID - REQUEST BYPASSED

Reason:An invalid Client parameter name was encountered. The current Client request is bypassed. Other requests in the same jobstream are still processed.

Action: None.

UST759E USERID NOT SPECIFIED ON JOB - REQUEST BYPASSED

Reason: A “USERID &JOB” statement was present in the USTBATCH input, but no security userid was associated with this job. The statement is bypassed. If a userid is required for UPSTREAM operation (a SECLVL= value greater than 0 in the UPSTREAM configuration), the requested function may fail when it is initiated by the Client.

Action: None.

UST760 RESTART IS/NOT ENABLED - COUNT=cccc DELAY=dddd

Reason: This message documents that automatic restart of USTBATCH operations is or is not enabled. “cccc” is the retry limit, and “dddd” is the minutes between restart attempts. This is controlled by the RESTART operand of USTBATCH.

Action:None.

UST761* ATTEMPTING type RESTART FOR target, REMAINING RETRIES=nnnn

Reason:This message documents that an automatic restart of a USTBATCH operation is being attempted. “type” is BACKUP or RESTORE, “target” is the target Client, and “nnnn” is the number of retries remaining.

Action: None.

UST762* type INTERRUPTED - WAITING nnn MINUTES FOR RESTART TO target

Reason:This message documents that a USTBATCH operation was interrupted, and is restarted in “nnn” minutes. “type” is BACKUP or RESTORE, and “target” is the target Client.

Action:None.

UST763E RESTART REQUIRES CONV=WAIT

Reason: The USTBATCH parameter RESTART= was specified without also specifying CONV=WAIT.

Action: Specify CONV=WAIT or remove the RESTART control card from your request. Then resubmit your request.

UST764E RECEIVE OF STARTED TASK MESSAGES FAILED

Reason: A VTAM error occurred while USTBATCH was reading messages from the UPSTREAM z/OS Storage Server main task.

Action: Communication error codes are reported in a following message. Consult IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST765E ALLOCATE FOR STARTED TASK MESSAGES FAILED

Reason:A VTAM allocation error occurred while USTBATCH was reading messages from the z/OS Storage Server main task.

Action: None.

UST766E SEND OF “xx” STRUCTURE FOR LOG MESSAGES FAILED

Reason: A VTAM error occurred while USTBATCH was requesting messages from the z/OS Storage Server main task. “xx” is the ID of the structure being transmitted.

Action: Communication error codes are reported in a following message. Consult IBM VTAM manuals to interpret the error, or contact BMC Support for assistance.

UST767E RECORD INVALID AFTER “ENDPARM” STATEMENT

Reason: An ENDPARM statement must be followed by a TARGLU=, TARGNAME=, or TCPTARG= statement, or another ENDPARM. The invalid statement is ignored.

Action: None.

UST768E INVALID COMMAND REQUEST

Reason: The specified “COMMAND=” value is invalid.

Action:Specify a valid UPSTREAM command.

UST769E UPSTREAM STARTED TASK TERMINATED

Reason: The UPSTREAM Started Task has ended.

Action: If this is the result of a shutdown request, no action is required. If this is an abnormal event, consult previous messages to determine the reason for shutdown.

UST770E HPNS TCP/IP ERROR - OP=‘xxxxxxxx’,RC=nnnn,ERRNO=nnnn, text

Reason: A TCP/IP error has occurred. Possible “OP=” values are: GETHOSTN, INITAPI, SOCKET, CONNECT, WRITERFS, WRITEZ, WRITECFM, READCFMD, DEALLOC-CLOSE, MSOCKET, MCONNECT, DEALLOC, CLOSE, AND SENDRECV. The text field provides a short description of the error.

Action: Investigate possible causes for the TCP/IP error and contact BMC Support for additional assistance, if necessary.

UST771E INVALID IP ADDRESS SPECIFIED

Reason: The format of the specified IP address is incorrect.

Action: Correct the specified IP address and resubmit the request.

UST772E INVALID TIMEOUT= VALUE SPECIFIED

Reason:More than 4 digits or non-numeric characters were specified for the TIMEOUT value.

Action:Correct the specified TIMEOUT value and resubmit the request.

UST773E PROCESS TIMED OUT: xxxxxxxxxxxxxxxxxxxxxxxx

Reason: The TIMEOUT value was exceeded while processing this request.

Action: Increase the “TIMEOUT” value or determine why the process is taking so long to complete.

UST774E TIMER SET ERROR=nnnn- NO TIMEOUT IN EFFECT

Reason: Error attempting to set a timer via z/OS API call.

Action: Internal error, contact BMC Support for further assistance.

UST775E COMMAND VALUE EXCEEDS 44 CHARACTERS

Reason: Value specified via the USTBATCH COMMAND parameter exceeded 44 characters in length.

Action:Shorten the value in question or consider using the USTCMD alternative utility program to issue the command.

UST776W WARNING: “TCPPORT” PARAMETER ONLY VALID FOR TCP/IP REQUESTS - PARAMETER IGNORED

Reason: The TCPPORT parameter, used only for TCP/IP communications with remote Clients, was specified for a SNA request.

Action: Remove the TCPPORT parameter specification. This is only a warning, the request should have been processed anyway after ignoring the specification of this parameter.

UST777E UNABLE TO RESOLVE SPECIFIED DNS NAME OR NAME INVALID

Reason: Format of specified DNSNAME parameter is invalid.

Action: Correct the specified DNSNAME to be valid and resubmit the corrected request.

UST778W WARNING: TCP/IP PORT DEFAULTED TO 1972

Reason:The TCPPORT control card was not specified for a request that required it.

Action: The processing of this request continues after the issuing of this error message. Specify the TCPPORT parameter in the next invocation of this request if the default value of 1972 is incorrect.

UST779W INVALID VOL=REF DATASET NAME

Reason: The format of the data set name specified in the VOL=REF parameter is incorrect.

Action: Code the correct format data set name and resubmit the request.

UST780W XM VALIDATION T/O

Reason: When running a CONV=WAIT connection with the “xxx” keyword specified, USTBATCH determined that the specified timeout (T/O) interval was exceeded without a cross memory (XM) post occurring from the z/OS Storage Server Started Task.

Action: Determine why the Started Task has not responded and resubmit the request if applicable. Contact BMC Support for further assistance.

UST781 USTEMAIL DD FOUND

             EMAIL MESSAGE SENT

             NO EMAIL REQUESTED

Reason:These are informational status messages issued for USTBATCH e-mail notification. They are posted to the USTLOG DD statement of the USTBATCH job.

USTEMAIL DD FOUND

The USTEMAIL DD statement was present in the JCL

EMAIL MESSAGE SENT

An e-mail was sent to the specified SMTP e-mail server

NO EMAIL REQUESTED

The USTEMAIL DD statement is present in the JCL but the e-mail control card corresponding to the job step completion code (EMAILOK, EMAILWRN, or EMAILERR) is not present in the “multiple use” input parameters of the batch job.

Action: If you have further questions concerning USTBATCH e-mail notification, please contact BMC Support for assistance

USTSCHED Utility Messages

UST800E* OPEN FOR USTSCHED DDNAME FAILED

Reason: Either the DD statement for USTSCHED was omitted from the Section “Define the UPSTREAM Started Task PROC” for the z/OS Storage Server started task, or another error occurred trying to open it.

Action: Check the joblog of the UPSTREAM task for IBM messages.

UST801E* SCHEDULE RECORD DESCRIPTOR IS INVALID

Reason:Schedule data in the USTSCHED data set is not in the format expected by the USTSCHED utility. Either the data set was never properly initialized with a schedule by the UPSTREAM ISPF dialogs, or the data has been corrupted.

Action: Rebuild the schedule data set or correct the z/OS Storage Server started task JCL to point to the correct data set.

UST802E* SCHEDULE DATA SET IS EMPTY

Reason: The USTSCHED data set is empty. Either the data set was never properly initialized with a schedule by the UPSTREAM ISPF dialogs, or the data has been corrupted.

Action: Build the schedule data set or correct the z/OS Storage Server started task JCL to point to the correct data set.

UST803* SCHEDULE type DATE=mm/dd/yyyy DSN=datasetname(membername)

Reason: The schedule in the schedule data set name has either been STARTED or REFRESHED.

UST805 SCHEDULE TIME=hh:ss SELECTION ID: selection event ID

Reason: A scheduled event has been executed. One of the two additional form of the UST805 shown below is also issued.

Reason: A scheduled SUBMIT event has been executed. The jobstream in the data set named has been submitted for batch execution through the internal reader (INTRDR).

SCHEDULE ISSUED THE z/OS COMMAND: console command

Reason:A scheduled event has been executed. The indicated z/OS console command was issued.

UST806* NO ACTIVITY SCHEDULED FOR TODAY

Reason: There are no scheduled events that execute today.

Action: Check the schedule if you think this is incorrect.

UST807E* SCHEDULE SUBMIT ERROR: error description

Reason: A SUB event was scheduled, but USTSCHED had an error either reading from the input data set named in the SUB event or writing to the INTRDR DD statement used to submit jobs. The error description identifies the error.

Action: Make sure that the data set named in the SUB event contains LRECL=80 jobstreams. If a member name was given on the SUB event, the data set must be a PDS or PDSE. If the member name is omitted, it must be sequential (DSORG=PS).

UST808W* IMMEDIATE SHUTDOWN REQUESTED - SCHEDULING TERMINATED

Reason: The operator has requested shutdown of UPSTREAM or has done a TERM of USTSCHED. USTSCHED terminates immediately.

Action: Check the schedule if you think this is incorrect.

UST990 USTTAPEM MOUNTED VOL='nnnnnn' RC=nnnn RS=nnnn FLAGS=nnnn DSN=<data_set_name>

Reason:A mount request for a specific (non-scratch) tape volume has been satisfied or failed. VOL=<volume_name>, RC=<the dynalloc return code>, RS=<the dynalloc reason code>, FLAGS=<the dynalloc flag bytes used>.

Action:If the mount request was successful, no action is necessary. If the mount request failed, review the JES Syslog and investigate possible causes for the failure. If necessary, contact BMC Support for additional assistance.

UST999 UPSTREAM SHUTDOWN COMPLETED

Reason: The UPSTREAM Started Task has shutdown as requested.