$HASP703

devname

Explanation

>>-devname--FSI ERROR  –  RT=--rc – ---------------------------->

>--+-MGCRE SERVICE FAILED --------+----------------------------><
   +-GETMAIN SERVICE FAILED ------+   
   +-ORDID= -nnnn--REQUEST FAILED-+   
   +-ORDID= -nnnn--BAD RESPONSE---+   
   +- FSA (DEVICE) FSID TOO LARGE-+   
   '- $SUBIT SERVICE FAILED ------'   

 JES2 (HASPFSSP) detected an incorrect or unsuccessful
return code from a system or functional subsystem interface (FSI)
service routine during FSI processing. The return code is displayed
as the RT= value. The text following the message indicates the service
that was detected as failing. If the text indicates an FSI order failure,
ORDID= gives the ID of the order that failed.
 In the message
text:  devname
The name of the device.
rc
A return code.
nnnn
The identifier of the failed order.
MGCRE SERVICE FAILED
The service used to issue the start command to start the FSS address
space failed. RT=rc indicates the MGCR return
code.
GETMAIN SERVICE FAILED
The request to allocate virtual storage failed. RT=rc indicates the GETMAIN return code.
ORDID=nnnn REQUEST FAILED
The request for an FSS/FSA order (JES2 command) failed. RT=rc indicates the FSIREQ return code.
ORDID=nnnn BAD RESPONSE
The FSS/FSA returned an incorrect response to an FSS/FSA order
(JES2 command).
FSA (DEVICE) FSID TOO LARGE
When the first device was started under this FSS, the number of
devices assigned to this FSS at that time was used to perform some
FSS initialization. The number was inflated at that time to allow
for additional devices to be moved to the FSS using JES2 commands.
Because the maximum number of devices for this FSS has now been reached
(by moving and starting too many devices), the identifying FSI FSID
for this device is too large. RT=hhhh indicates
the maximum number of devices, in hexadecimal, that can be active
in this FSS at one time. You must shut down the FSS and restart it
to change this number.
$SUBIT SERVICE FAILED
The $SUBIT service was used to issue the start command; however,
it was unable to complete the request. RT=rc indicates
the $SUBIT return code.

System action
 The system action depends upon the current processing
being performed. If the service failure is detected during functional
subsystem (FSS) start, drain, or stop processing, this message is
typically followed by $HASP700, $HASP701, or $HASP702. Refer to this
accompanying message for the system action taken. If the failure is
detected during functional subsystem interface (FSI) order (JES2 command)
processing, this message is followed by $HASP152, and system operation
continues.

Operator response
 Notify the system programmer. If the $HASP703
message is followed by $HASP700, $HASP701, or $HASP702, see the operator
response for that message. If the $HASP703 message is followed by
$HASP152, reenter the JES2 command.

System programmer response
 Determine the cause of the service
failure from the return code displayed in the message. Correct the
problem and see the action for $HASP700, $HASP701, or $HASP702, if
appropriate.
 Note: If the return code is from the
FSI order service, contact the appropriate FSS documentation for a
description of the return code and any actions that are required.

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