CA IDMS Reference 19.0

PDF
English

@ACCEPT PROC -- moves the information block

The @ACCEPT PROC statement moves the 256-byte application program information block associated with a previously defined database procedure to a specified location in program variable storage. Information is placed in this block by a previously issued @BIND PROC statement (discussed later in this section). This information may have subsequently been updated by the procedure. The @ACCEPT PROC statement can be used by programs running under, but in a different partition from, the central version.
idmscu19
The @ACCEPT PROC statement moves the 256-byte application program information block associated with a previously defined database procedure to a specified location in program variable storage. Information is placed in this block by a previously issued @BIND PROC statement (discussed later in this section). This information may have subsequently been updated by the procedure. The @ACCEPT PROC statement can be used by programs running under, but in a different partition from, the central version.
Syntax

 
►►─── @ACCEPT PROC=
procedure-name
 ────────────────────────────────────────────►

 ►─── ,COMAREA=
procedure-control-location
 ────────────────────────────────────►◄
 
Parameters
PROC=
procedure-name
Specifies the name of the database procedure whose application program information block is to be moved to program variable storage. 
Procedure-name
 must identify a fullword-aligned 8-byte literal.
COMAREA=
procedure-control-location
Specifies the fullword-aligned 256-byte field in program variable storage to which the application program information block is to be moved.
Status Codes
After completion of the @ACCEPT PROC function, the ERRSTAT field in the IDMS communications block indicates the outcome of the operation.
The following is a list of the acceptable status codes for this function and their corresponding meaning:
  • 0000 
    The request has been serviced successfully.
  • 1508 
    The specified record is not in the subschema. The program has probably invoked the wrong subschema.
Example
The following statement moves the application program information block used by the CHECKALL procedure to the location identified as CHECKIT in the application program's variable storage:

@ACCEPT PROC='CHECKALL',COMAREA=CHECKIT