Receiving SARTPO42 Device allocation error - ERR=9700, INFO=0000 in View
Article ID: 200978
Updated On:
Products
Issue/Introduction
While executing our standard backup process on a disaster recovery system, we are receiving dynamic allocation errors.
Below are the messages being seen in the View started task:
IGD306I UNEXPECTED ERROR DURING CBRXLCS PROCESSING
RETURN CODE 12 REASON CODE 56
THE MODULE THAT DETECTED THE ERROR IS IGDIDMUS
SMS MODULE TRACE BACK - IDMUS IDMSU IDM00 SSIRT
SYMPTOM RECORD CREATED, PROBLEM ID IS IGD00009
* SARTPO42 Device allocation error - ERR=9700, INFO=0000
* SARTPO42 DSNAME=your.viewdb.SARTAPE.T0000410
* 260 SARTPO42 Reply Y/N to continue processing with new tape
How can we get the SARSTC functioning again and suppress issuing of the WTOS associated to the SARTPO42 message?
Environment
Release : 14.0
Component : View
SMS
Dynamic allocation
Cause
Allocations for your backup tapes are initially set by the SARINIT STORGRP0 initialization parameter.
Based on the ERR=9700, SMS is intercepting View's dynamic allocation, which then results in SMS issuing the device allocation error.
The SARTP042 error is documented, in part, as follows:
SARTPO42
Device allocation error - ERR=xxxxx, INFO=xxxx DSNAME=xxxxxxxxxxxxxxx Reply Y/N to continue processing with new tape
Reason:
Dynamic allocation has failed for the backup tape. The hexadecimal error and information codes are:
ERR= The error code returned by the operating system's Dynamic Allocation function.
INFO= The Dynamic Allocation function REASON Code.
DSN= The tape data set name.
Common dynamic allocation error meaning:
9700
A severe Storage Management Subsystem (SMS) error occurred which can be the result of SMS rules for the dataset
name and unit specifications and can require assistance from the group managing SMS
Resolution
- Please review your SARINIT STORGRP0 settings and discuss these settings with your SMS experts. Make sure the SARINIT STORGRP0 settings are compatible with the SMS rules that are in place on the system you are running SARSTC on. Also make sure that your SECURITY profiles are compatible with both SARSTC and the associated SMS rules.
- To avoid the WTOS associated to the SARTP042 error for the time being...
Actions for SARTP042 are:
a. Reply Y to the message to allocate a new tape and continue processing.
b. Otherwise you can reply N, correct the problem with the tape, and restart the function.
If you've tried replying 'Y' but continue to receive the error on the new tapes, our suggestion would be to reply 'N' for the time being.
The reply of 'N" will likely cause SARSTC to abend with RC=16.
- You can then restart View using the /S sarstc,OPT=STOPBU option so that the backup cycle does not restart.
- At this point, you will then need to identify and correct the actual cause of the device allocation error.
- Once you have resolved the device allocation problem, you can initiate the standard backup process again using one of the following methods:
* If the View started task (SARSTC) is already started, you can use the following operator commands to initiate a tape backup to a new tape:
F SARSTC,NEW
* If the View started task (SARSTC) is not started, you can use the following operator commands to start SARSTC and initiate a tape backup to a new tape:
S SARSTC,OPT=NEW
Additional Information
For more information on the START options for SARSTC, please refer to the following documentation:
Feedback
