$HASP701

devname

Explanation

>>-devname--NOT DRAINED  –  FSS=--fssname – -------------------->

>--+-STOP DEVICE ORDER UNSUCCESSFUL +--------------------------><
   +-STOP FSA ORDER UNSUCCESSFUL ---+   
   '-FSA FAILED TO DISCONNECT ------'   

 devname NOT
DRAINED – FSS=fssname –  { STOP DEVICE ORDER UNSUCCESSFUL }

{ STOP FSA ORDER UNSUCCESSFUL }

{ FSA FAILED TO DISCONNECT }

 The indicated device controlled
by functional subsystem fssname cannot be completely
drained. The device remains in the last phase completed successfully.
That is, if the functional subsystem application (FSA) is not successfully
stopped after the stop device order is successful, the device is not
restarted.
 In the message text:  devname
The name of the device.
fssname
The name of the functional subsystem.
STOP DEVICE ORDER UNSUCCESSFUL
The functional subsystem application could not successfully process
the order to stop the device.
STOP FSA ORDER UNSUCCESSFUL
The functional subsystem could not successfully process the order
to stop the functional subsystem application.
FSA FAILED TO DISCONNECT
The functional subsystem application did not disconnect within
a predetermined amount of time after a STOP FSA order was issued.

System action
 Normal operation continues. No work is selected
by the indicated device. The device is left in the draining state.

Operator response
 Notify the system programmer. The $P command
can be entered for the device again. If this message appears during
$PJES2 processing, the system will not withdraw and a $PJES2,ABEND
may be required to withdraw JES2 from the system. Use the MVS™ CANCEL command to cancel the functional subsystem address
space with a dump.
 Save the hard-copy log. For systems with
remote consoles, save the remote console sheet.

System programmer response
 If the system issues message $HASP703
along with this message, use the return code issued in message $HASP703
and the appropriate functional subsystem (FSS) documentation to analyze
the error.
 If you use SMP/E to make all changes to the system,
use the LIST CDS and LIST PTFBY functions of SMP/E to obtain a list
of the current maintenance from the SMP/E control data set (CDS).
 If you make any changes to the system without using SMP/E, run
the LISTIDR function of AMBLIST to obtain a list of all members with
a PTF or local fix and save the output. Run LISTIDR against the following:
 SYS1.LINKLIB.
SYS1.SVCLIB
The library containing the program that issued the message.
SYS1.LPALIB

 Save all the associated output and contact the IBM® Support Center for assistance.

Module
 HASPFSSP
 Routing Code: 1,2,10
 Descriptor Code: 4