SUMMARY OF SPF COMMANDS 157

APPENDIX E: SPF COMMAND SYNTAX - QUICK REFERENCE SUMMARY

158 SPF/CMS PROGRAM REFERENCE MANUAL

Advanced Features:

EDIT PRIMARY COMMANDS

SAVE Text Preparation Features:

CANCEL CAPS [ON/OFF]

FIND/CHANGE STRINGS (BROWSE AND EDIT) Character String Format: Picture Strings - Special Characters:

P'=' any character (don't care)

P'~' any non-blank character

P'.' any non-displayable (invalid) character P'I' any numeric character (0-9)

APPENDIX F: SPF/TSQ - SPF/CMS DIFFERENCES

SPF/CMS is functionally equivalent to the SPF/TSO program pro-duct, 5740-XT8, Version 2.2. The two products are 'fully compat-ible in display formats and operation, except for those features which are explicitly oriented to the VS2/TSO ^01'" VM/CMS environ-ment. The following is a list of those differences.

• On the primary option menu, option 6 is:

SPF/TSO: Enter TSO Command or CLIST SPF/CMS: "Enter CMS Command or EXEC

• Menus and tutorials which refer to "data sets" in SPF/TSO refer to "files" in SPF/CMS. The first part of the data set (file) menus allows specification of an SPF library. The for-mat is identical in SPF/TSO and SPF/CMS, namely;

SPF LIBRARY:

PROJECT

===>

LIBRARY

===>

TYPE

===>

MEMBER

===>

The second part of the data set (file) menus differs as fol-lows. For SPF/TSO:

OTHER PARTITIONED OR SEQUENTIAL DATASET:

DATASET NAME

===>

VOLUME SERIAL

===>

eMS FILE:

FILE 10

===>

MEMBER

===>

OWNER'S 10

===>

===>

===>

The third part o'f the data set (file) menus contains an (OS) password field for SPF/TSO. For SPF/CMS, this part of the menu may contain a read password field, an update password field, or both, depending on the type of function. In SPF/TSO, passwords pertain to data sets; in SPF/CMS, they pertain to mini disks.

• Implementation of SPF libraries in SPF/TSO is accomplished usi ng parti ti oned data sets, whi Ie SPF/Cl'1S uses sequenti al CMS fi les and/or MAClIBs and TXTlIBs (under user option).

• SPF/TSO supports printing on either: _,

System printer (via submission of a background job) 328x printer (via interface to DSPRINT command)

SPF/CMS supports printing via the eMS PRINT command. The out-put may be directed to the system printer or spooled to anoth-er usanoth-er ^(01'" machi ne), whi ch may be at a remote node in the network. SPF/CMS does not support printing on a 328x printer.

• Specification of "job statement information" occurs in SPF/TSO on the background selecti on menu and all menus per-taining to hardcopy output. SPF/CMS provides job information on the batch selection menu only. All other output is accom-pl i shed wi th the CMS PRINT, PUNCH, or DISK DUMP commands, rather than via job submission.

160 SPF/CMS PROGRAM REFERENCE MANUAL

Additionally, job statement information syntax and keywords are different, reflecting differences between CMS batch job

str~am5 and VS2 JCL.

• Differences in foreground processing (option 4) and back-ground (batch) processing (option 5) are as follows:

SPF/TSO: Compiled/assembled output (object module) goes into an SPF library whose "type" is OBJ. link edit out-put (load module) goes into an SPF library whose

"type" is LOAD.

SPF/CMS: Compiled/assembled output (object module) goes into an SPF library whose "type" is TEXT. linkage

edit-ing is not s~pported, but the LOAD command is sup-ported.

• Option 3.2 (dataset/file utility). The following suboptions of this utility in SPF/TSO:

A - Allocate new data set C - Catalog data set U - Uncatalog data set are replaced in SPF/CMS with:

S - Specify new SPF library U - Unspecify SPF library

There is no need for an "allocate file" capability under SPF/CMS, since space allocation is handled automatically by VM/CMS. There is, however, a need to pre-specify SPF library identifiers and file characteristics to SPF/CMS.

• Option 3.4. In SPF/TSO this is the catalog management utili-ty. In SPF/CMS it is replaced with the project utility, which provides a similar function for SPF libraries.

• Option 3.6. In SPF/TSO this is the hardcopy utility. In SPF/CMS it ;s replaced with the spool utility, which provides similar functions for printing and punching, and also allows spooling to another user (or machine), which may be at a remote node in the network.

• Option 3.7. In SPF/TSO this is the list VTOC utility, which has no equivalent in SPF/CMS. It is replaced with a new SPF/CMS function, the reader utility.

• Option 3.8. In SPF/TSO this is the outlist utility, which has no equivalent in SPF/CMS. It is replaced with a new SPF/CMS function, the retrieve utility.

APPENDIX F: SPF/TSO - SPF/CMS DIFFERENCES 161

Access (see Link Access Mode)

Create/Update SPF Statistics 115 Cursor

Display Document (SCRIPT/VS) 126

Display Member Selection List 8, 23, 104 Display Project Entries 113

Display SPF library or File Information 107 SPF Display Formats 2

Draft Document Options (SCRIPT/VS) 126 Edit 40 162 SPF/CMS PROGRAM REFERENCE MANUAL

Final Document Options (SCRIPT/VS) 127

Foreground Processing 130, 148 Help

Page Size

Print Document (SCRIPT/VS) 129 Print High/low Intensity 11 SCRIPT/VS Document Processing 125 PROFILE Command 89 .

Program Access (PA) Keys 10

Program Function (PF) Keys 10, 28 Programming libraries 6, 145 Programming Systems 17

Project Name 6, 145 Project Utility

Display Project Entries 113 Print Project Entries 113 Reset SPF Statistics Utility

Create/Update SPF Statistics 115 Delete SPF Statistics 115

Display Formatted Document 126 Draft Document Options 126 Final Document Options 127 Print Formatted Document 129

164 SPF/CMS PROGRAM REFERENCE MANUAL

Scrolling 12 Text Preparation Features 93 Text Split "TS" Line Command 94

Structured Programming Facility/Conversational Monitor System: Program Reference Manual Printed in U.S.A. SH20-2409-0

~

C0()

~

@J ~

11111111 '"

0

'>",\

dl

1 ^{111 '} ,

0

1111111

'IIi:t

N

~

6

II:U:II

N J:

~

en

11111111 ~

Q) +-' o Z

Structured Programming Facility/Conversational Monitor System:

Program Reference Manual SH20-2409-0

This form may be used to communicate your views about this publication. They will be sent to the author's department for whatever review and action, if any, is deemed appropriate. Comments may be written in your own language; use of English is not required.

READER'S