M204.2028: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
 
m (add <var>'s)
 
Line 6: Line 6:


<p>
<p>
<b>System manager response:</b> An IODEV 27 thread or sufficient SPCORE for a buffer could not be acquired by Model&nbsp;204 to send a reject-attach message to the remote partner. This increases the likelihood that the user may need for you to help
<b>System manager response:</b> An <var>IODEV</var> 27 thread or sufficient <var>SPCORE</var> for a buffer could not be acquired by Model&nbsp;204 to send a reject-attach message to the remote partner. This increases the likelihood that the user may need for you to help
diagnose the problem: messages will have been written locally to your audit trail or operator's console, but sense data summarizing the problem cannot be transmitted back to the user. You may alleviate this condition by defining additional IODEV
diagnose the problem: messages will have been written locally to your audit trail or operator's console, but sense data summarizing the problem cannot be transmitted back to the user. You may alleviate this condition by defining additional <var>IODEV</var> 27s or by increasing <var>SPCORE</var>. </p>
27s or by increasing SPCORE. </p>
<p>
<p>
<b>Operator response:</b> This is an informational message. The condition is usually temporary. It means that a user at some remote site is failing in an attempt to establish a conversation with your system but is receiving no diagnostic feedback,
<b>Operator response:</b> This is an informational message. The condition is usually temporary. It means that a user at some remote site is failing in an attempt to establish a conversation with your system but is receiving no diagnostic feedback,
and that user will probably need to communicate with your system administrator to resolve the problems. If this message appears frequently, notify your system administrator. </p>
and that user will probably need to communicate with your system administrator to resolve the problems. If this message appears frequently, notify your system administrator.  
 
</p>
{{Template:M204.2028 footer}}
{{Template:M204.2028 footer}}
<!-- skeleton as it was in pdf/UNABLE TO SEND REJECT-ATTACH DUE TO LOCAL RESOURCE SHORTAGE /-->
<!-- skeleton as it was in pdf/UNABLE TO SEND REJECT-ATTACH DUE TO LOCAL RESOURCE SHORTAGE /-->

Latest revision as of 17:12, 15 March 2018

M204.2028  Unable to send reject-attach due to local resource shortage

Model 204 has received an attach request from a remote partner to begin an inbound process. The attach request must be rejected, but Model 204 cannot acquire the resources necessary to transmit a reject-attach message containing diagnostic information back to the remote partner.

System manager response: An IODEV 27 thread or sufficient SPCORE for a buffer could not be acquired by Model 204 to send a reject-attach message to the remote partner. This increases the likelihood that the user may need for you to help diagnose the problem: messages will have been written locally to your audit trail or operator's console, but sense data summarizing the problem cannot be transmitted back to the user. You may alleviate this condition by defining additional IODEV 27s or by increasing SPCORE.

Operator response: This is an informational message. The condition is usually temporary. It means that a user at some remote site is failing in an attempt to establish a conversation with your system but is receiving no diagnostic feedback, and that user will probably need to communicate with your system administrator to resolve the problems. If this message appears frequently, notify your system administrator.

Message attributes:

RETCODEO=0Sets online return code
RETCODEB=0Sets batch (single user) return code
CLASS=IInformation class; the message can be suppressed with the X'02' bit setting of the MSGCTL parameter
AUDITMSWrites the message with line type MS to the audit trail
NOCOUNTDoes not increment the error count (ERCNT) parameter
NOTERMDoes not display the message on the user's terminal
OPRWrites the message to the (operator) console
SAVESaves the message in the VIEW ERRORS table

Back to list of messages