SNAX/APC Configuration and Management Manual

Planning for SNAX/APC
SNAX/APC Configuration and Management Manual—138787
2-13
Sync Point Support Considerations
Server Conversation-Level Security Test Failures
All server conversation-level security checking occurs when an Attach request arrives
from a remote LU and the Attach requires security checking. The result of the security
checks is that the request is either honored or rejected. When the request is honored, a
conversation is started with the requested server transaction program. (The request may
be queued to wait for the transaction program if it is not immediately available.) If the
request is rejected, an error is communicated to the remote LU. The remainder of this
section describes the conditions that cause a request to be rejected and the error
indication that is communicated to the remote LU in that case.
•
If the request violates protocol with respect to the security information fields, the
session is deactivated and the UNBIND includes the sense code %H080F6051. An
example of this condition is an Attach that contains a user ID but no password and
the already-verified indicator is not on in the Attach request.
•
If the request uses a level of security not accepted by the local LU, the session is
deactivated and the UNBIND includes the sense code %H10086040. An example of
this condition is an Attach that includes a user ID and the already-verified indicator,
but the local LU does not accept already-verified from the remote LU.
•
If the request contains invalid security information, the Attach is rejected with the
sense code %H080F6051. In this case the sense code is carried in an FMH-7 and
the session is not deactivated. An example of this is an Attach that includes an
invalid user ID and password pair.
Sync Point Support Considerations
You must be licensed to use SNAX/APC sync point support. The license is granted
when you buy SNAX/APC and its sync point option.
SCF Considerations for Sync Point Support
There is only one SCF attribute required to enable sync point support but sync point
cannot be used on a conversation until certain sync point parameters are also set in the
TP-READY and (MC)ALLOCATE verbs.
The new SCF attribute is LOCAL-LU-SYNC2-SUPPORT and its arguments are NONE,
the default, and SYNCPT. On an SCF ADD or ALTER LU, you use LOCAL-LU-
SYNC2-SUPPORT SYNCPT to enable the local LU for sync point support. See
Section 8, SCF Commands for SNAX/APC
for details about the use of the SCF ADD
LU and ALTER LU commands and the LOCAL-LU-SYNC2-SUPPORT attribute.
SNAX/APC Verb Considerations for Sync Point Support
In order to use sync level support, the UOW containing the TP-READY verb and all
subsequent UOWs for the conversation must use IPC Version Code S5. The TP-
READY verb must use TR-SYNC-SUPPORT-INDICATOR “Y” and the subsequent
(MC)ATTACH verb must use AL-SYNC-LEVEL “S”. For more information about
UOWs, the IPC Version Code, the TP-READY verb and the (MC)ALLOCATE verbs,
consult the SNAX/APC Application Programming Manual.