CMS FILE:
FILENAME
===>
IF NOT lINKED, SPECIFY;
OWNER'S 10
===>
DEVICE ADDR.===>
lINK ACCESS MODE===>
READ PASSWORD
===>
UPDATE PASSWORD===>
ASSEMBLER OPTIONS:
===>
LIST NODECK OBJECT ADDITioNAL CONCATENATED MACLIBS:===>
C,.'SLIB===>
OSMACRO===> ===>
Figure 69. Foreground - Assembler example
Upon completion of the foreground processing, a "MORE ••• " message will be displayed in the lower right-hand corner of the screen.
The user may then press the PA2 key to return to the foreground processor menu.
When the foreground processor menu is redisplayed, a message indicating completion of the process is displayed in the upper right-hand corner of the screen. The user may then enter another foreground processing request or press the End PF key to return to the previous menu.
ASSEMBLER/COMPILER PROCESSING
The Assembler menu shown in Figure 69 is typical of the language processor menus. In the figure, a library concatenation sequence of three data sets has been specified. The concatenation order is:
SPFDEMO.XXX.ASM SPFDEMO.TEST.ASM SPFDEMO.MASTER.ASM
Note: The SPF type qualifier for an assembler source library need not be ASSEMBLE, as illustrated in the example.
Before invoking the foreground processor, SPF will scan the con-catenated sequence of libraries to find the member to be assembled or compiled (member TOP in this example). A eMS file with a filetype acceptable to the language processor (ASSEMBLE in this example) will be created on the user's A-disk by extracting the member from the first library in the sequence in which it occurs.
FOREGROUND PROCESSING (OPTION 4) 131
For any library in the sequence that is a collection of sequential files, a MACLIB is created on the user's A-disk to enable the use of COPY or INCLUDE statements. (For performance reasons, it is recommended that high-level libraries be specified as MACLIBs.) Any temporary files created by SPF will be erased at the com-pletion of the foreground process.
For this example, if SPFDEMO.XXX.ASM is a colletion of sequential files and the higher-level libraries are already MACLIBs, the GLOBAL command preceding the ASSEMBLE command might look like:
GLOBAL MACLIS SPFOOSl1 TEST MASTER CMSLIB OSMACRO
where SPFOOS11 is the SPF generated filename for the MACLIB con-taining all the members of SPFDEMO.XXX.ASM.
Note the following points:
1. The concatenation sequence serves two purposes: It is used by SPF to locate the primary member to be assembled, and it allows inclusion of subsidiary members referenced by COpy statements in the assembler source.
2. Other MACLIBs can be appended to the GLOBAL statement, fol-lowing the SPF libraries, by specifying them in the desired order in the "additional concatenated MACLIBs" fields.
3. If the source is from an SPF library, the TEXT file is placed language processor (ASSEMBLE in this example). The resulting TEXT and LISTING files are placed on the user's A-disk. specified as processor options. Only those options specified on the menu are passed to the language processor; SPF does not automaticallY generate any options.
The processor menus for COBOL, FORTRAN, and the two Pl/I compilers
132 SPF/CMS PROGRAM REFERENCE MANUAL
The menus for the interactive debug facilities differ somewhat from the other foreground menus:
• The COBOL interactive debug menu allows specification of up to four additional program ids (which must match the external filenames), and PRINT and SOURCE options which determine what FILEDEFs are generated by SPF. Also allowed are 15 tokens of execution parameters that are stacked for use by the process-or, and the specification of up to four additional TXTLIBs.
• The FORTRAN interactive debug menu allows variations of the DISK or PRINT options, the specification of up to four addi-tional filenames, and the specification of up to four TXTlIBs to be included in the GLOBAL-TXTLIB command.
LOAD PROCESSING
.This foreground option (option 4.6) provides a menu interface to the LOAD command (Figure 70). The menu allows a simple LOAD and GENMOD command to be issued with the specified options, or a user-specified EXEC to be issued for more complex load functions with multiple filenames, INCLUDEs, etc.
--- FOREGROUND LOAD ---ENTERIVERIFY PARAMETERS BELOW:
SPF LIBRARY:
PROJECT
===>
SPFDEMOLIBRARY
===>
XXX===>
TEST===>
MASTER===>
TYPE
===>
TEXT MEMBER===>
TOP_CMS FILE:
FILENAME
===>
IF NOT LINKED, SPECIFY:
OWNER'S 10
===>
DEVICE ADDR.===>
LINK ACCESS MODE===>
READ PASSWORD
===>
USER EXEC
===>
OPTIONS: (USER'S EXEC TO BE RUN INSTEAD OF LOAD/GENMOD) LOAD
===>
CLEAR MAPGEHMOD
===>
MAPADDITIONAL CONCATENATED TXTLIBS:
===> ===> ===> ===>
Figure 70. Foreground - LOAD menu
FOREGROUND PROCESSING (OPTION 4) 133
BATCH PROCESSING (OPTION 5)
The batch option provides an interface with standard language processors for compilation and assembly in the CMS batch machine of programs stored in SPF libraries or CMS files. It also pro-vides a menu interface for batch execution of the CMS LOAD com-mand.
When batch is selected (primary option 5), a menu is displayed t9 allow the user to select a language processor, and to enter and/or verify job statement parameters (Figure 71). When the user enters the desired information and presses the ENTER key, SPF dis-plays the appropriate processor menu.
It is possible to bypass the secondary menu by entering two num-bers, separated by a decimal point, on the primary option menu.
For example, "5.2" to select a batch COBOL compile. Note, howev-er, that use of this procedure does not allow verification or changes to the job statement parameters, nor does it allow the generation of multiple compilations (multiple job steps) within the same job.
--- BATCH SELECTION MENU ---SELECT OPTION
===>
1 - SYSTEM ASSEMBLER 2 - OS/VS COBOL COMPILER 3 - FORTRAN IV (GI) COMPILER
4 - PL/I CHECKOUT COMPILER 5 - PL/I OPTIMIZING COMPILER 6 - LOAD
BATCH JOB INFORMATION: (ENTER OR VERIFY BEFORE PROCEEDING)
(YOUR CMS USER 10 AUTOMATICALLY BECOMES YOUR BATCH JOB USER 10.) BATCH MACHINE 10
===>
CMSBJOB STATEMENT INFORMATION:
ACCOUNT NUMBER
===>
UIOI JOB NAME===>
LENFigure 71. Batch selection menu
When job information has been entered and a language processor selected, a menu is displayed to allow the user to specify SPF library information or CMS filename, and processor options.
Figure 72 shows an example for the PL/I optimizing compiler. The project name, first library name, type qualifier, and member name must be specified to compile a program whose source is in an SPF library. The filename must be specified to compile a eMS file with a filetype of PLI or PLIOPT. (If the CMS filename ;s entered, it overrides any SPF library specification.) The other parameters are optional, except as noted below.
134 SPF/CMS PROGRAM REFERENCE MANUAL
--- BATCH PLI OPTIMIZING COMPILE ---ENTER/VERIFY PARAMETERS BELOW:
SPF LIBRARY:
PROJECT
===>
SPFDEMOLIBRARY
===>
LARRY===>
V3TE$T===>
MASTER===>
TYPE