z/OS MVS Programming: Writing Transaction Schedulers for APPC/MVS
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Set_AS_Attributes

z/OS MVS Programming: Writing Transaction Schedulers for APPC/MVS
SA23-1398-00

The Set_AS_Attributes service lets a transaction scheduler set attributes for a subordinate address space. In particular, this service can set an attribute to designate whether conversations allocated from the specified address space are to be associated to the system base LU. You can use this service to prevent an inadvertent association in cases where the subordinate address space allocates a conversation before the transaction scheduler connects the subordinate address space to itself. Without Set_AS_Attributes in such cases, the conversation is assigned to the system base LU, and when the transaction scheduler attempts to connect the subordinate address space to itself later, if the conversation is still outstanding, the connect fails.

For example, you could use Set_AS_Attributes for this purpose in the following manner:

  1. The transaction scheduler is active when APPC is not, so Identify and Connect cannot be performed.
  2. The transaction scheduler calls Set_AS_Attributes with the Default_LU_Designation parameter set to 1 (to not associate conversations with the system base LU).
  3. APPC is started on the system.
  4. A subordinate address space allocates a conversation before the transaction scheduler identifies itself to APPC and connects the subordinate address space.

In the above scenario, if the transaction scheduler did not call Set_AS_Attributes first, APPC/MVS would assign the subordinate address space to the system base LU as soon as APPC/MVS received the outbound allocate request.

Instead, because the transaction scheduler does call Set_AS_Attributes first, APPC rejects the allocate request. When the transaction scheduler is notified of APPC initialization, the transaction scheduler can identify itself to APPC and connect the subordinate address space to itself.

The Set_AS_Attributes service can be called when APPC/MVS is not active.

Environment

Format

Figure 1. ATBSASA - Set_AS_Attributes
CALL ATBSASA (ASCB_ptr, 
              Default_LU_Designation, 
              Return_Code
             ); 

Parameters

ASCB_ptr
Supplied parameter
  • Type: Pointer
  • Char Set: N/A
  • Length: 32 bits

Specifies the pointer to the address space control block (ASCB) that represents the subordinate address space whose attributes are to be set.

Default_LU_Designation
Supplied parameter
  • Type: Integer
  • Char Set: N/A
  • Length: 32 bits

Specifies whether conversations allocated from the specified address space should be associated with the system base LU. If conversations are not to be associated with the system base LU, the address space cannot use APPC services until it is explicitly connected using the ATBCONN service.

Valid values for this parameter are:
Value
Meaning
0
Associate outbound conversations with the system base LU. This value is the default.
1
Do not associate conversations with the system base LU.

By default, the conversations from any unconnected address space will automatically be associated to the system base LU unless this service is called.

Return_code
Returned parameter
  • Type: Integer
  • Char Set: N/A
  • Length: 32 bits
Set_AS_Attributes might return one of the following decimal values in the return code parameter:
Decimal
Meaning
0
Attributes were set successfully.
4
Request failed -- the ASCB_ptr was not valid.
8
Request failed -- the value for Default_LU_Designation was not valid (must be 0 or 1).
40
The caller was not running in supervisor state or with PSW key 0-7.
48
APPC/MVS services failure.

Characteristics and Restrictions

Transaction schedulers that call the Set_AS_Attributes service should not have any enabled unlocked task (EUT) functional recovery routines (FRRs) established. For more information about EUT FRRs, see the information on providing recovery in z/OS MVS Programming: Authorized Assembler Services Guide.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014