Activate Bound Program (ACTBPGM)

Operand 2: System pointer or space pointer data object

Built-in number for ACTBPGM2 is 658.
ACTBPGM2(
         activation_defn   : address of aggregate
         program_spec      : address of system pointer or
                             address of space pointer(16)
)
 
OR
 
Built-in number for ACTBPGM is 416.
ACTBPGM (
         activation_defn   : address of aggregate
         program_spec      : address of system pointer or
                             address of space pointer(16)
)

Warning

The following information is subject to change from release to release. Use it with caution and be prepared to adjust for changes with each new release.

Description

Activates a bound program or bound service program. The program spec operand specifies the target program to be activated, either directly or indirectly.

If the program spec operand specifies a space pointer, it must locate a 16-byte aligned structure. The format of the structure is different for the ACTBPGM and ACTBPGM2 instructions.

Format of program spec for ACTBPGM2 instruction

Offset
Dec	Hex		Field Name						Data Type and Length
0	0		Program						System pointer
16	10		Target activation group						UBin(8)
16	10			Target activation group (Non-Bound program)						Char(8)
24	18		Options						Char(1)
24	18			Prefer teraspace storage						Bit 0
				0= No 1= Yes
24	18			Reserved (binary 0)						Bits 1-7
25	19		Reserved (binary 0)						Char(23)
48	30		--- End ---

When prefer teraspace storage is no, then the definitions for the ACTBPGM program spec template apply to ACTBPGM2.

For user-state clients, prefer teraspace storage will be ignored and the instruction will execute as though prefer teraspace storage is no.

Format of program spec for ACTBPGM instruction

Target activation group is the activation group mark of an existing activation group into which the service program is to be activated. If the activation group does not exist, then the activation group not found  (hex 2C13) exception is signaled.

The service program is eligible to be activated into the target activation group if one of the state conditions and one of the storage model conditions hold.

State conditions:

• The target activation group's state and the service program state are equal (i.e. either both are system-state or both are user-state).

• The service program state is inherit-state and the target activation group's state is equal to the current thread execution state.

Storage model condition:

• The target activation group's storage model and the service program storage model are equal (i.e., either both are single level or both are teraspace).

• The service program storage model is inherit.

If the program spec operand specifies a system pointer, it designates the target program to be activated. The target program must be either a bound program or a bound service program, otherwise invalid operation for program  (hex 2C15) exception is signaled.

Activating the Program

The program activation operation is discussed in detail in the CALLX instruction.

If the target program adopts its owner's user profile, the effect is as if the target program were the most recent invocation on the call stack. This permits the adopted authority of the owner to be applied for purposes of activating dependent service programs. This adoption policy is in effect for the duration of the ACTBPGM operation.

Activation Definition

The activation defn must point to a 16-byte aligned area which receives the activation definition. The format of the structure is different for the ACTBPGM and ACTBPGM2 instructions.

Format of activation defn for ACTBPGM2 instruction

Format of activation defn for ACTBPGM instruction

where,

The activation group mark identifies the activation group into which the target program was activated.

The activation mark identifies the activation of the program.

The activation status indicates whether the operation created a new activation (=0) or found an existing activation (=1).

Authorization Required

• Execute

  • Program referenced by operand 2

  • Contexts referenced for address resolution

Lock Enforcement

• Materialize

  • Contexts referenced for address resolution

Exceptions

06 Addressing

• 0601 Space Addressing Violation
• 0602 Boundary Alignment
• 0603 Range

0A Authorization

• 0A01 Unauthorized for Operation

10 Damage Encountered

• 1004 System Object Damage State
• 1005 Authority Verification Terminated Due to Damaged Object
• 1044 Partial System Object Damage

1A Lock State

• 1A01 Invalid Lock State

1C Machine-Dependent

• 1C03 Machine Storage Limit Exceeded

20 Machine Support

• 2002 Machine Check
• 2003 Function Check

22 Object Access

• 2201 Object Not Found
• 2202 Object Destroyed
• 2203 Object Suspended
• 2207 Authority Verification Terminated Due to Destroyed Object
• 2208 Object Compressed
• 220B Object Not Available

24 Pointer Specification

• 2401 Pointer Does Not Exist
• 2402 Pointer Type Invalid
• 2403 Pointer Addressing Invalid Object Type

2A Program Creation

• 2AB5 Observable Information Necessary For Retranslation Not Encapsulated

2C Program Execution

• 2C12 Activation Group Access Violation
• 2C15 Invalid Operation for Program
• 2C1E Activation Access Violation
• 2C2A Argument Optimization Interface Error

2E Resource Control Limit

• 2E01 User Profile Storage Limit Exceeded

36 Space Management

• 3601 Space Extension/Truncation

44 Protection Violation

• 4401 Object Domain or Hardware Storage Protection Violation
• 4402 Literal Values Cannot Be Changed