1. Release Notes
  2. Documentation Updates
  3. New or Modified HSC/VTCS Messages

New or Modified HSC/VTCS Messages

ELS 7.2 includes the following new or modified HSC/VTCS system messages:

Note:

These updates supersede the information found in the ELS Messages and Codes Guide, Chapter 2, HSC, VTCS, and CDRT Messages.

SLS5079E

SLS5079E MOUNT of VVVVVV on DDDD - Failed (RC) - ERRTEXT

Explanation: The mount of volume VVVVVV on VIRTUAL drive DDDD failed. The reason for the failure is defined in the ERRTEXT portion of the message. RC is the return code from HSC/VTCS.

Explanations, System Actions and User Responses for the various Error Texts are presented below. The context in which the message is issued should always be determined, as the text for a given Reason describes the most likely case and may not match the specific case in which it was output.

Error Text (ERRTEXT) Values

Message SLS5079E adds the following error text values:

  • VTV mount suppressed by subsequent Mount/Dismount request
  • Recall from tapeplex TTTTTTTT failed
  • SMC comms error (RC=RRR)
  • VTV is mounted or in-use for Migrate or Recall

For reference, all error text values are described in the following listing:

Drive already has a VTV mounted

Explanation: A Mount was requested of Volume VVVVVV on device DDDD. VTCS determined that the device already has a VTV mounted on it.

System Action: The Mount fails.

User Response: Determine which VTV is Mounted on the device. If it should not be Mounted, attempt to Unload/Dismount it using the MSP Unload command and the HSC Dismount command.
  • If the Mount is still required, re-drive it.
  • If the reason for the failure is not understood, contact Oracle StorageTek Software Support.
Internal error occurred RC=RRRRRRRR

Explanation: A mount was requested of volume VVVVVV on device DDDD. VTCS suffered an internal error (Return Code X'RRRRRRRR') while processing the Mount.

System Action: The Mount fails.

User Response: Contact Oracle StorageTek Software Support. 

Invalid virtual subpool PPPPPPPP

Explanation: A Mount was requested of Scratch volume VVVVVV on device DDDD. The Scratch volume was associated with Subpool PPPPPPPP (for example, TAPEREQ statement), but the Subpool was found to be invalid. To be valid, the Subpool must exist and contain Scratch volumes.

System Action: The Mount fails.

User Response: Determine how the Subpool was selected (for example, TAPEREQ statement). Check that PPPPPPPP is the name of a Subpool and that it contains scratch volumes. Make any necessary corrections.
  • If the Mount is still required, re-drive it.
  • If the reason for the failure is not understood, contact Oracle StorageTek Software Support.
Invalid VTD address SSSSSSSS for VTV.

Explanation: A Mount was requested of volume VVVVVV on device DDDD. VTCS failed to find the internal control block for device (VTD) DDDD which is in VTSS SSSSSSSS.

System Action:The Mount fails.

User Response: Contact Oracle StorageTek Software Support. 

MVC: MMMMMM canceled by operator

Explanation: A Mount was requested of migrated volume VVVVVV on device DDDD. Before the Recall and Mount were complete, the request was canceled by the operator, using the VT CANCEL command to cancel the Recall.

System Action: The Mount fails.

User Response:
  • If the Mount is still required, re-drive it.
  • If the reason for the failure is not understood, contact Oracle StorageTek Software Support.
MVC: MMMMMM MVC could not be mounted

Explanation: A Mount was requested of Migrated volume VVVVVV on device DDDD. VTCS initiated a Recall of the VTV from MVC MMMMMM, but the MVC could not be mounted.

System Action: The Mount fails.

User Response: Review specific error messages to determine why the MVC Mount failed. Correct any problems found.
  • If the Mount is still required, re-drive it.
  • If the reason for the failure is not understood, contact Oracle StorageTek Software Support.
MVC: MMMMMM No access to VTSS SSSSSSSS to verify VTV location

Explanation: A Mount was requested of Migrated volume VVVVVV on device DDDD. The VTV had previously been resident in VTSS SSSSSSSS. The VTSS could not be accessed by this host to determine if it contains a copy of the VTV.

System Action: The Mount fails.

User Response: Check that VTSS SSSSSS can be accessed by, and is Online to, this Host.
  • If the Mount is still required, re-drive it.
  • If the reason for the failure is not understood, contact Oracle StorageTek Software Support.
MVC: MMMMMM No RTDs for requested media and ACS

Explanation: A mount was requested of migrated volume VVVVVV on device DDDD. During recall processing, it was determined that there were no RTDs in the ACS that could mount the requested media type.

System Action: The Mount fails.

User Response: This is probably due to a configuration change. Determine the MVC media type and ACS location of the volume, or if other MVCs are available to access the VTV.
  • If the mount is still required, move the MVC to an ACS with RTDs of the correct type and re-drive the mount -or- make other MVC copies available to use for recalling the VTV.
  • If the reason for the failure is not understood, contact Oracle StorageTek Software Support.
MVC: MMMMMM VTD status changed during Recall/Mount

Explanation: A Mount was requested of volume VVVVVV on device DDDD.

In the case of a Migrated VTV the message will contain MVC:MMMMMM to show the MVC containing the VTV and indicates a change of VTD status during Recall. When the Recall from MVC MMMMMM was complete, VTCS found that the device was associated with a different VTCS request. A common scenario that gives this message is:
  • A Batch Job requests VTV VVVVVV be mounted on a device DDDD.
  • As the VTV is migrated, VTCS initiates a Recall.
  • The Batch Job is canceled.
  • A second job requests a different VTV be Mounted on device DDDD.
  • The Recall of VTV VVVVVV completes.
  • VTCS attempts to satisfy the original Mount, but finds the device is no longer processing volume VVVVVV.

If the VTV was Resident, the message will not contain MVC:MMMMMM and indicates a change of VTD status during Mount.

System Action: The Mount fails.

User Response:
  • If the Mount is still required, re-drive it.
  • If the reason for the failure is not understood, contact Oracle StorageTek Software Support.
No MVCs available

Explanation: A Mount was requested of volume VVVVVV on device DDDD. Because the VTV was Resident in a different VTSS from the one that contains device DDDD, a VTV transfer was initiated. The transfer is achieved by Migrating the VTV from the other VTSS and Recalling it into the VTSS containing device DDDD.

The VTV could not be Migrated from the other VTSS because no MVCs were available.

System Action: The Mount fails.

User Response: Determine where VTV VVVVVV is Resident. Then, either:
  • Change the JCL to select a device in that VTSS, or
  • Investigate why no MVCs could be selected for Migration. Correct any problems found.

If the Mount is still required, re-drive it. If the reason for the failure is not understood, contact Oracle StorageTek Software Support.

Problem decoding VCI request

Explanation: A Mount was requested of volume VVVVVV on device DDDD. An internal error occurred within VTCS while processing the Mount.

System Action: The Mount fails.

User Response: Contact Oracle StorageTek Software Support. 

Subsystem terminating

Explanation: A Mount was requested of volume VVVVVV on device DDDD. VTCS could not process the Mount as the Task for the VTSS containing device DDDD was terminating/had terminated, for example, as the result of a VT VARY VTSS(SSSSSSSS) OFFLINE command.

System Action: The Mount fails.

User Response: Check the status of the VTSS containing device DDDD. If it should be Online but is not, issue VT VARY VTSS(SSSSSSSS) ONLINE. VTCS will process the Mount when the VTSS comes Online.

If the reason for the failure is not understood, contact Oracle StorageTek Software Support.

VTV contents suspect

Explanation: A Mount was requested of volume VVVVVV on device DDDD. The VTV was found to be "fenced".

System Action:The Mount fails.

User Response: As for message SLS6657E, contact Oracle StorageTek Software Support. 

VTV mount suppressed by subsequent Mount/Dismount request

Explanation: A Mount was requested of volume VVVVVV on device DDDDDD.

If (MVC:VVVVVV) appears in the message it means that after a successful VTV recall from MVC VVVVVV, a different VTV was now required to be mounted on VTD DDDDDD.

A common scenario that gives this message is:
  1. A job requests VTV VVVVVV be mounted on VTD DDDDDD.
  2. As volume VVVVVV is found to be migrated, the VTCS initiates a recall of VTD VVVVVV from MVC VVVVVV.
  3. The batch job requesting VTV VVVVVV is canceled.
  4. A second job requests a different VTV and is assigned the same VTD DDDDDD.
  5. The recall of VVVVVV initiated by the canceled job completes.
  6. VTCS attempts to complete the mount of VTV VVVVVV but finds that VTD DDDDDD is no longer processing VTV VVVVVV.

If (MVC:VVVVVV) does not appear it means that requests received from different SMC clients were received in an illogical order by the HSC/VTCS server.

A common scenario that gives this message is:
  1. A job from host 1 requests mount of VTV VVVVVV on VTD DDDDDD.
  2. A mount request is sent from the SMC on host 1 to the HSC/VTCS server but due to network delays is not immediately received.
  3. The job on host 1 is canceled. A dismount request is sent from the SMC on host 2 to the HSC/VTCS server.
  4. A job from host 2 requests mount of VTV and is assigned VTD DDDDDD.
  5. A mount request is sent from the SMC on host 2 to the HSC/VTCS server and is received before the mount and dismount requests from host 1.

System Action: The Mount fails.

User Response: If the failed mount is still required, redrive it. If the reason for the failure is not understood, contact Oracle StorageTek Software Support. 

VTV: VVVVVV Inaccessible/bad VTSS SSSSSSSS referenced
Explanation: A Mount was requested of volume VVVVVV on device DDDD in VTSS SSSSSSSS. VTV VVVVVV could not be Mounted due to either:
  • The state of the VTSS. The VTSS could not be accessed by this Host or was not Online.
  • In the case of a Scratch Mount, the Mount failing and being re-tried too many times. This can happen if another product repeatedly rejects the VTV as not being in Scratch status.

System Action: The Mount fails.

User Response: In the case of a specific (non-scratch) Mount, check that VTSS SSSSSSSS can be accessed by, and is Online to, this Host. Correct any problems found.

In the case of a Scratch Mount, determine if another product is rejecting the Mount, for example, because its scratch definitions are not synchronized with those of VTCS.

Make any necessary changes.
  • If the Mount is still required, re-drive it.
  • If the reason for the failure is not understood, contact Oracle StorageTek Software Support.
VTV: VVVVVV Attempts to select a scratch VTV have been exhausted

Explanation: A scratch mount was requested on device DDDD in VTSS SSSSSSSS. The mount request failed after an internally specified number of VTVs were selected as a scratch and then found to not be a qualified scratch.

Volume VVVVVV, which is listed in the message, is the last VTV found in this state. This error can occur if another product repeatedly rejects each VTV as not being in scratch status or if the VTV scratch status in the CDS is not synchronized with the VTCS internal scratch counts.

System Action: The VTV scratch mount request will be retried later.

User Response: Determine if another product is rejecting the mount, for example, because its scratch definitions are not synchronized with those of VTCS.

Make any necessary changes. If the reason for the failure is not understood, contact Oracle StorageTek Software Support.

VTV: VVVVVV is still mounted

Explanation: A Mount was requested of volume VVVVVV on device DDDD. VTCS determined that the VTV is still Mounted from a previous Mount.

System Action: The Mount fails, though VTCS will attempt to re-drive it.

User Response: Determine whether the previous Mount of VTV VVVVVV was on a different Host to the current Mount. If it was, check that SYSZVOLS ENQueues are being correctly propagated across Hosts.
  • If the previous Mount was on the same Host, attempt to determine if there was any reason for the Dismount to have failed. Correct any problems found.
  • If the reason for the failure is not understood, contact Oracle StorageTek Software Support.
VVVVVV is not a valid VTV

Explanation: A Mount was requested of volume VVVVVV on device DDDD.

VTCS determined that VVVVVV is not defined in the VTCS Configuration, via a VTVVOL statement, as being Virtual.

System Action: The Mount fails.

User Response: Determine why a non-virtual allocation was directed to virtual device (VTD) DDDD. Esoterics, JCL, TAPEREQ statements, ACS routines and User Exits influence allocation and should be reviewed.

Make any necessary corrections.
  • If the Mount is still required, re-drive it.
  • If the reason for the failure is not understood, contact Oracle StorageTek Software Support.
VTV: VVVVVV ECAM error CC=CCC RC=RRR

Explanation: VTV VVVVVV failed to mount due to an ECAM error. The ECAM completion code is CCC and the return code is RRR.

System Action: The Mount fails.

User Response: Consult the appropriate ELS publication. If the reason for the failure is not understood, contact Oracle StorageTek Software Support. 

VTV: VVVVVV Volume access control gave RC=RRRRRRRR
Explanation: VTV VVVVVV was selected to satisfy a scratch mount, but the mount was rejected because of User Exit 14:
  • Set Return Code UX14RJCT (reject).
  • Set Return Code UX14PWRD (password check) and the password check performed by HSC failed.
  • Set Return Code UX14RACF/UX14RACL (RACROUTE check) and the RACROUTE check performed by HSC indicated the requestor does not have access to VTV VVVVVV.
  • Set Return Code UX14RACF/UX14RACL (RACROUTE check) and the RACROUTE check performed by HSC indicated the requestor has READ, but not UPDATE, access to VTV VVVVVV. HSC therefore requested VTV VVVVVV be mounted as write-protected.
  • Set Return Code UX14NWRT (write-protect).

This message may be preceded by one or more of messages SLS2978A, SLS2979I, SLS2980I, SLS2985I or SLS2986I.

X'RRRRRRRR' is the Return Code passed to VTCS by HSC after invoking User Exit 14 and performing any processing requested by User Exit 14.
  • X'91309130' indicates the request to mount VTV VVVVVV was denied by User Exit 14 or by HSC as a result of a password/RACROUTE check failing.
  • X'91319131' indicates that VTCS was requested to mount VTV VVVVVV as write-protected. This was rejected by VTCS because the VTV selected to satisfy a scratch mount must be mounted write-enabled.

System Action: The Mount fails.

User Response: Look for any preceding message SLS2978A, SLS2979I, SLS2980I, SLS2985I or SLS2986I. Determine why VTCS received Return Code X'RRRRRRRR' and whether this was the correct response for VTV VVVVVV given the details (for example, jobname) of the address space requesting the mount.

If the mount is still required, make any changes that are needed so that the mount does not fail again, then re-drive the mount.

VTV is import blocked

Explanation: VTV VVVVVV is not accessible as it is still pending completion of an IMPORT request.

System Action: The Mount fails.

User Response: Determine if there was an error condition during IMPORT processing. A possible cause of this would be having LOGPOL=REQUIRED specified, but logging is not active at the time of the IMPORT. This condition can be cleared by first correcting the problem that caused the failure and taking the following steps:
  1. Issue a Display VTV VVVVVV and note the line:

    Importing: NNNN (VTD address)

  2. Issue Dismount VVVVVV NNNN

Attempt to mount the VTV again. If the reason for the failure is not understood, contact Oracle StorageTek Software Support.

MVC:MMMMMMMM MMMMMMMM Partition map not found

Explanation: VTV VVVVVV has a migrated copy on MVC MMMMMM, which has been written in partitioned mode. Each partitioned mode MVC should have a record in the CDS that describes the usage of the partitions. This record is known as the partition (allocation) map. VTCS was unable to read the partition map for MVC MMMMMM.

System Action: The Mount fails.

User Response: Drain or audit MVC MMMMMM, then attempt the mount again. 

Recall from tapeplex TTTTTTTT failed

Explanation: In order to mount VTV VVVVVV, VTCS had to recall the VTV from tapeplex TTTTTTTT. The recall failed.

System Action: The Mount fails.

User Response: Message SLS7540E will also be issued to give details of the recall failure. Investigate and correct the cause of the failure. 

SMC comms error (RC=RRR)

Explanation: In order to mount VTV VVVVVV, VTCS had to issue an internal request to SMC. This command failed due to an SMC communications error. If output, RC=RRR is the non-zero Return Code.

System Action: The Mount fails.

User Response: Check the status of SMC on the local tapeplex.
  • If message SLS6884E was issued, investigate and correct any errors reported.
  • If message SLS7540E was also issued, indicating a failure to recall VTV VVVVVV from another tapeplex (TTT), perform the same checks on tapeplex TTT as well. 
VTV is mounted or in-use for Migrate or Recall

Explanation: A mount was requested of volume VVVVVV on device DDDD. The VTV is currently active with a Migrate or Recall request and is unavailable until that process completes.

System Action: The Mount fails.

User Response:
  • If the Mount is still required, re-drive it.
  • If the reason for the failure is not understood, contact Oracle StorageTek software Support.

SLS6751I

CLINK vtssname/clinkid iftype ifaddr RETURNED ECAM ERROR CC=ccc RC=rrr

Explanation: VTCS encountered an ECAM error on Clustered VTSS link clinkid with iftype ifaddr on VTSS vtssnam. The command terminated with completion code ccc and reason code rrr. This may be caused by a hardware or software error, or some other unresolvable condition.

System Action: Depending on the nature of the error, the failing request may be re-tried on a different Clink.

User Response: Check the SYSLOG for other messages which may indicate the nature of the error.

SLS9004I

SLS9004I COMMPATH XXXXXXXX is ignored under MSP

Explanation: The METHOD=VTAM and VTAMPATH= are not supported under MSP and are ignored.

System Action: None.

User Response: Respecify the COMMPATH command with METHOD=CDS or METHOD=LMU.

SLS9005E

SLS9005E Global module YYYY error, RC=XXXX
Explanation: The MSP global load routine failed to YYYY (load/delete) a module. XXXX is the return code set.
  • 90A1 invalid LVT pointer
  • 90A2 invalid @@VT pointer
  • 90A3 invalid @@GETAB pointer in @@VT
  • 90A4 unable to get lock for routine
  • 90A5 unable to free lock for routine
  • 90A6 unable to obtain global load table
  • 90A7 BLDL failed
  • 90A8 load failed
  • 90A9 GETMAIN of CSA failed

System Action: Load or delete fails for specified module.

User Response: HSC may fail because of this error. If so, determine the cause of the problem and restart HSC after the problem is corrected. If message persists, contact your Oracle StorageTek Systems Support Representative (SSR).

SLS9006I

SLS9006I MSP@GCT subtable release error, RC=XXXX
Explanation: During MSP component termination processing, an error occurred when attempting to release a @GCT subtable. The return code (RC) can be used to identify this error. XXXX is the return code set.
  • 90A1 invalid LVT pointer
  • 90A3 invalid @@GETAB pointer in @@VT
  • 90A4 unable to get lock for routine
  • 90A5 unable to free lock for routine
  • 90Aa CSA FREEMAIN error
  • 90Ab error while releasing storage for an entry in the @GCT
  • 90Ac FREEMAIN of GCT failed

System Action: None.

User Response: Some CSA storage may not be released at completion of task. If message persists contact your Oracle StorageTek Systems Support Representative (SSR).

SLS9007I

SLS9007I SSAT table has XX free slots remaining

Explanation: The MSP subsystem affinity table is nearly full, only XX slots remain.

System Action: HSC operations continue normally.

User Response: Attempt to reduce concurrent usage of HSC commands and facilities.

Note:

If the table is completely full then an abend U448 reason code 940-003 will occur. If this abend persists, contact your Oracle StorageTek Systems Support Representative (SSR).

SLS9008I

SLS9008I MMMM from NNNN to YYYY

Explanation: The LSM is in manual mode and volume MMMM from location NNNN will need to be mounted on drive YYYY.

System Action: None.

User Response: Manual mount the volume on the nominated drive.

SLS9050I

SLS9050I Clean-up of @GCT load table successful

Explanation: Debug message indicating clean-up by SLS@DEL completed successfully.

System Action: None.

User Response: None.

SLS9051I

SLS9051I Module XXXXXXXX is in problem state for global load request

Explanation: The MSP load routine was called while in problem state for a global load request.

System Action: Load continues.

User Response: Warning message only, HSC continues. If message persists, contact your Oracle StorageTek Support Representative (SSR).

SLS9052I

SLS9052I EP NNNN at AAAA length LLLL has been MMMM
Explanation: Indicates that a module has been loaded or deleted.
  • NNNN is the entry point name.
  • AAAA is the entry point address.
  • LLLL is the module length.
  • MMMM is deleted or loaded.

System Action: None.

User Response: None.

SLS9053I

SLS9053I No journal datasets defined

Explanation: HSC was started without journal datasets defined and the JOURNAL operator command was issued.

System Action: None.

User Response: Warning message only, HSC continues.

SLS9054I

SLS9054I SYNCH GETMAIN for user exit failed

Explanation: HSC was unable to GETMAIN the memory required to load a user exit.

System Action: Load fails for specified user exit.

User Response: Warning message only, HSC continues. Check that the region parameter for the job is large enough. If the message persists, contact your Oracle StorageTek Systems Support Representative (SSR).

SLS9055I

SLS9055I No free QWRK task for ASCOMM, waiting for a while

Explanation: MSP has a TCB limitation of 256 active TCBs. To avoid an attach failure abend, HSC will wait for the number of active TCBs to drop below the 256 limit before attempting to attach a new ASCOMM QWRK task.

System Action: None.

User Response: None.

SLS9056E

SLS9056E MSP does not support CF(LOCKSTR parameter in VTCS config), VTCS terminating

Explanation: VTCS/MSP does not support a coupling facility structure. It is available for only VTCS/MVS.

System Action: VTCS terminates.

User Response: Configure CDS without LOCKSTR parameter.