Dialog and Client/Server micropatterns
You can insert these micropatterns in the code of all the Screen and Server types from the PDP COBOL editor, or in the code of a Macro from the Source code tab.
Branching micropatterns
These micropatterns generate GO TO statements.
*!GXX
where:- *! is the required start tag of the micropattern. The
* must be entered in column 7, reserved for the comments in the COBOL code, and the
! must be entered in column 8.Note: If you press CTRL + space bar in the PDP COBOL editor, the content assist facility displays the list of the micropatterns that are adapted to the entity and to the position in the COBOL code (WORKING-STORAGE SECTION or PROCEDURE DIVISION). The micropatterns that are used only to retrieve the Pacbase data are not included in the list. Each micropattern in the list is documented. If you double-click one of them, the start tag and the identifier of the micropattern are inserted in the code. You must then complete its declaration.
- GXX is the micropattern identifier: GF, GFA, GFR, or GDB.
- GF branches to the end of the automatic function
or subfunction in which the line is inserted.Note: It can be inserted in *X-type subfunctions associated with automatic subfunctions (F20, F25, and so forth).It generates:
where FFSS is the code of the associated automatic function or subfunction.GO TO FFFSS-FN.
- GFA branches to the end of the display processing:
GO TO END-OF-DISPLAY.
- GFR branches to the end of the reception processing
GO TO END-OF-RECEPTION.
- GDB branches to the beginning of the current
iteration.
where FFSS is the function or subfunction code.GO TO FFFSS-FN.
Micropatterns to call Screens or C/S Screens
- The OSC micropattern calls the Screen or C/S
Screen that is indicated in the operands.You must conform to the following input format
where :*!OSC "SCNNNN"
- *! is the required start tag of the micropattern. The
* must be entered in column 7, reserved for the comments in the COBOL code, and the
! must be entered in column 8.Note: If you press CTRL + space bar in the PDP COBOL editor, the content assist facility displays the list of the micropatterns that are adapted to the entity and to the position in the COBOL code (WORKING-STORAGE SECTION or PROCEDURE DIVISION). The micropatterns that are used only to retrieve the Pacbase data are not included in the list. Each micropattern in the list is documented. If you double-click one of them, the start tag and the identifier of the micropattern are inserted in the code. You must then complete its declaration.
- OSC is the micropattern identifier.
- " " must frame the operands.
- SCNNNN is the code of the Screen or C/S Screen called (CL0001 for example). You can also indicate its external name.
The OSC micropattern generates:
where:MOVE 'SCEXTERN' TO 5-NNNN-PROGE MOVE 'O' TO OPER GO TO F4040.
- SCEXTERN is the external name (on 8 characters) of the SCNNNN Screen or C/S Screen.
- nnnn represent the last 4 characters of the Screen or C/S Screen (0001 for example).
- *! is the required start tag of the micropattern. The
* must be entered in column 7, reserved for the comments in the COBOL code, and the
! must be entered in column 8.
- The OSD micropattern calls the Screen or C/S
Screen that is indicated in the operands. This call is deferred to
the end of the reception processing.You must conform to the following input format
where:*!OSD "SCNNNN"
- *! is the required start tag of the micropattern. The
* must be entered in column 7, reserved for the comments in the COBOL code, and the
! must be entered in column 8.Note: If you press CTRL + space bar in the PDP COBOL editor, the content assist facility displays the list of the micropatterns that are adapted to the entity and to the position in the COBOL code (WORKING-STORAGE SECTION or PROCEDURE DIVISION). The micropatterns that are used only to retrieve the Pacbase data are not included in the list. Each micropattern in the list is documented. If you double-click one of them, the start tag and the identifier of the micropattern are inserted in the code. You must then complete its declaration.
- OSD is the micropattern identifier.
- " " must frame the operands.
- SCNNNN is the Screen or C/S Screen code (CL0001 for example). You can also indicate its external name.
The OSD micropattern generates
where:MOVE 'SCEXTERN' TO 5-NNNN-PROGE MOVE 'O' TO OPER.
- SCEXTERN is the external name (on 8 characters) of the SCNNNN Screen or C/S Screen.
- NNNN represent the last 4 characters of the Screen or C/S Screen (0001 for example).
- *! is the required start tag of the micropattern. The
* must be entered in column 7, reserved for the comments in the COBOL code, and the
! must be entered in column 8.
- The OTP micropattern calls the Screen or C/S
Screen whose external name is indicated in the operands.You must conform to the following input format
where:*!OTP "SCEXTERN"
- *! is the required start tag of the micropattern. The
* must be entered in column 7, reserved for the comments in the COBOL code, and the
! must be entered in column 8.Note: If you press CTRL + space bar in the PDP COBOL editor, the content assist facility displays the list of the micropatterns that are adapted to the entity and to the position in the COBOL code (WORKING-STORAGE SECTION or PROCEDURE DIVISION). The micropatterns that are used only to retrieve the Pacbase data are not included in the list. Each micropattern in the list is documented. If you double-click one of them, the start tag and the identifier of the micropattern are inserted in the code. You must then complete its declaration.
- OTP is the micropattern identifier.
- " " must frame the operands.
- SCEXTERN is the external name (on 8 characters) of the SCNNNN Screen or C/S Screen.
The OTP micropattern generates:
where:MOVE 'SCEXTERN' TO 5-NNNN-PROGE MOVE 'O' TO OPER GO TO F4040.
- NNNN represent the last 4 characters of the Screen or C/S Screen (0001 for example).
- *! is the required start tag of the micropattern. The
* must be entered in column 7, reserved for the comments in the COBOL code, and the
! must be entered in column 8.
Micropatterns to access Segments
*!XAA "SEGM"
where:- *! is the required start tag of the micropattern. The
* must be entered in column 7, reserved for the comments in the COBOL code, and the
! must be entered in column 8.Note: If you press CTRL + space bar in the PDP COBOL editor, the content assist facility displays the list of the micropatterns that are adapted to the entity and to the position in the COBOL code (WORKING-STORAGE SECTION or PROCEDURE DIVISION). The micropatterns that are used only to retrieve the Pacbase data are not included in the list. Each micropattern in the list is documented. If you double-click one of them, the start tag and the identifier of the micropattern are inserted in the code. You must then complete its declaration.
- XAA is the micropattern identifier (see the table for the list of the identifiers).
- " " must frame the operands.
- SEGM is the Segment code.
Micropattern identifiers | Generated result |
---|---|
XD | Deletion of the Segment indicated in the operands |
XP | Read of the first record through a dynamic access.
This micropattern always retrieves a record. Reserved for Segments defined in a repetitive category with a display use. |
XR | Read of the Segment indicated as the operands |
XRN | Sequential read of the Segment indicated in
the operands (dynamic access) Reserved for Segments defined in a repetitive category with a display use. |
XRU | Read before update of the Segment indicated in the operands |
XRW | Rewrite of the Segment indicated in the operands |
XUN | Unlock of the Segment indicated in the operands. (except for DL1). |
XW | Write of the Segment indicated in the operands |
- A PERFORM statement for the physical access to the Segment indicated in the operand
- The corresponding statement in function F80 for the files with a V (VSAM) organization
Micro-pattern to call an elementary processing on a Logical View (Server only)
*!XT "PARM1 PARM2"
where:- *! is the required start tag of the micropattern. The
* must be entered in column 7, reserved for the comments in the COBOL code, and the
! must be entered in column 8.Note: If you press CTRL + space bar in the PDP COBOL editor, the content assist facility displays the list of the micropatterns that are adapted to the entity and to the position in the COBOL code (WORKING-STORAGE SECTION or PROCEDURE DIVISION). The micropatterns that are used only to retrieve the Pacbase data are not included in the list. Each micropattern in the list is documented. If you double-click one of them, the start tag and the identifier of the micropattern are inserted in the code. You must then complete its declaration.
- XT is the micropattern identifier.
- " " must frame the operands.
- PARM1 PARM2 are the parameters. The number of parameters is not defined and their values vary according to the processing.
The elementary processing applies to the Logical View in whose block the micropattern is inserted. The micropattern *!XT "PARM1 PARM2" generates PERFORM FVVNN-PARM1-PARM2 THRU FVVNN-PARM1-PARM2-FN (where VVNN is the Logical View).
For example, the micropattern *!XT "CHKD CATR CPXX11" generates PERFORM FVI10-CHKD-CATR-CPXX11 THRU FVI10-CHKD-CATR-CPXX11-FN.
Other micropattern related to Segment accessing
The YAA micropattern generates the F80-SEGM-AA tag. This tag is used when the physical accesses to the Segment indicated in the operands are replaced.
*!YAA "SEGM"
where:- *! is the required start tag of the micropattern. The
* must be entered in column 7, reserved for the comments in the COBOL code, and the
! must be entered in column 8.Note: If you press CTRL + space bar in the PDP COBOL editor, the content assist facility displays the list of the micropatterns that are adapted to the entity and to the position in the COBOL code (WORKING-STORAGE SECTION or PROCEDURE DIVISION). The micropatterns that are used only to retrieve the Pacbase data are not included in the list. Each micropattern in the list is documented. If you double-click one of them, the start tag and the identifier of the micropattern are inserted in the code. You must then complete its declaration.
- YAA is the micropattern identifier. AA represents the last 2 characters of the Segment accessing operator (R for READ, W for WRITE, RW for REWRITE, D for DELETE for example).
- " " must frame the operands.
- SEGM is the Segment code.
Micropatterns to position errors
- Enter the ERR micropattern with the following
input format:
where:*!ERR "N DELCO IND LV=VIEW"
- *! is the required start tag of the micropattern. The
* must be entered in column 7, reserved for the comments in the COBOL code, and the
! must be entered in column 8.Note: If you press CTRL + space bar in the PDP COBOL editor, the content assist facility displays the list of the micropatterns that are adapted to the entity and to the position in the COBOL code (WORKING-STORAGE SECTION or PROCEDURE DIVISION). The micropatterns that are used only to retrieve the Pacbase data are not included in the list. Each micropattern in the list is documented. If you double-click one of them, the start tag and the identifier of the micropattern are inserted in the code. You must then complete its declaration.
- ERR is the micropattern identifier.
- " " must frame the operands.
- N is the error code, on one position. This code is an alphanumeric character (except for 0 or 1, which are reserved for the coding of documentary messages).
- DELCO is the variable Data Element with which the error code is associated. Entering this Data Element is required.
- IND is an optional operand, specific to Servers. It represents an index. Its code and length are free.
- LV="VIEW" is an optional attribute, specific to Servers. view represents the code of a Logical View. You specify this attribute only if there is no Logical View, to generate the micropattern with this Logical View.
The error message corresponding to the error code is specified on the -GE Lines of the Screen. The cursor will be positioned and the Data Element will take on the attributes defined for the Data Elements in error.Note: For a repetitive Data Element, its code is indicated, followed by the sequence number of the Data Element instance (DELCO (2) for example). - *! is the required start tag of the micropattern. The
* must be entered in column 7, reserved for the comments in the COBOL code, and the
! must be entered in column 8.
- Enter the ERU micropattern with the following
input format:
where:*!ERU "NNNN DELCO"
- *! is the required start tag of the micropattern. The
* must be entered in column 7, reserved for the comments in the COBOL code, and the
! must be entered in column 8.Note: If you press CTRL + space bar in the PDP COBOL editor, the content assist facility displays the list of the micropatterns that are adapted to the entity and to the position in the COBOL code (WORKING-STORAGE SECTION or PROCEDURE DIVISION). The micropatterns that are used only to retrieve the Pacbase data are not included in the list. Each micropattern in the list is documented. If you double-click one of them, the start tag and the identifier of the micropattern are inserted in the code. You must then complete its declaration.
- ERU is the micropattern identifier.
- " " must frame the operands.
- NNNN is the error code, on four positions, managed by the user.
- DELCO is the erroneous Data Element. Entering this Data Element is optional.
The error message corresponding to the error code is specified on the -GE Lines of the Dialog. This message will be displayed on the error message line (ERMSG). If a Data Element has been specified, the cursor will be positioned on the Data Element, and error attributes will apply.Note: This micropattern cannot be used on a repetitive Data Element. - *! is the required start tag of the micropattern. The
* must be entered in column 7, reserved for the comments in the COBOL code, and the
! must be entered in column 8.
Micropattern to generate the automatic function labels in the Business Component
The Y micropattern can be indicated in Business Components only. It generates the label of an automatic function or subfunction that was replaced with specific code (*R).
*!Y
where:- *! is the required start tag of the micropattern. The
* must be entered in column 7, reserved for the comments in the COBOL code, and the
! must be entered in column 8.Note: If you press CTRL + space bar in the PDP COBOL editor, the content assist facility displays the list of the micropatterns that are adapted to the entity and to the position in the COBOL code (WORKING-STORAGE SECTION or PROCEDURE DIVISION). The micropatterns that are used only to retrieve the Pacbase data are not included in the list. Each micropattern in the list is documented. If you double-click one of them, the start tag and the identifier of the micropattern are inserted in the code. You must then complete its declaration.
- Y is the micropattern identifier.
Micropattern to generate the list of PCBs
The PCB micropattern can be indicated in the WORKING-STORAGE SECTION or PROCEDURE DIVISION of a standard Screen, client Screen, or Server. It is used to generate the list of the PCBs that are associated with the PSB. The PSB is indicated in the Screen (PSB= option in the -GG Lines) or the Dialog (Complement tab).
*!PCB
where:- *! is the required start tag of the micropattern. The
* must be entered in column 7, reserved for the comments in the COBOL code, and the
! must be entered in column 8.Note: If you press CTRL + space bar in the PDP COBOL editor, the content assist facility displays the list of the micropatterns that are adapted to the entity and to the position in the COBOL code (WORKING-STORAGE SECTION or PROCEDURE DIVISION). The micropatterns that are used only to retrieve the Pacbase data are not included in the list. Each micropattern in the list is documented. If you double-click one of them, the start tag and the identifier of the micropattern are inserted in the code. You must then complete its declaration.
- PCB is the micropattern identifier.