Pathway/iTS SCUP Reference Manual

Introduction to SCUP
HP NonStop Pathway/iTS SCUP Reference Manual—520269-002
1-4
Controlling TCP Access
•
Name of the program (taken from the PROGRAM-ID paragraph in the Identification
Division)
•
Access flag for the program unit
•
Version of the program
•
Location and size in the code file where the program object code is stored
•
Flag that indicates whether a symbol table exists for the SCREEN COBOL
program
When displaying information about the contents of a SCREEN COBOL object file,
SCUP retrieves some of the information from the directory file and retrieves the date
the program was compiled from the code file.
Controlling TCP Access
The TCP needs to locate programs in the following two situations. In each case, the
TCP examines the directory file to find the entry for the named program:
•
When starting a terminal, the TCP must locate the INITIAL program for that
terminal.
•
When a SCREEN COBOL program CALL statement is executed, the TCP must
locate the called program.
SCUP lets you control which programs and versions of programs the TCP can execute
by setting an access flag for each program. Each entry in the directory file has an
access flag that you can turn ON or OFF through SCUP. The TCP recognizes the flag
settings and ignores those entries for which access has been denied. The TCP looks
for the highest version number of the program with the access flag ON.
In addition to the access flag for each entry, the library has an access flag (ON or OFF)
that applies to new programs added to the object files. If the library access is set OFF,
any program added to the library has access OFF. The library access setting does not
affect entries already in the library.
SCUP allows you to alter the access flag for program units and the access flag for
the library.
An example of a directory file with access flags shown is illustrated in Figure 1-2.