HP 3000 Manuals HP 3000 Manuals
Changing Input, List and Output Files
DICTPDE uses the formal file designators DICTIN as the input file for
DICTPDE commands, DICTLOG as the list file for the commands entered
interactively, and DICTOUT as the output file for the generated source
code.
When DICTPDE is run interactively, DICTIN is the terminal (DICTPDE
commands are accepted as they are entered at the terminal). DICTPDE can
also be executed to accept commands from a command file (in either a
session or a job stream) by redirecting DICTIN to a command file. To
redirect DICTIN to command file, use the following MPE file equation:
FILE DICTIN = command file name
The next time DICTPDE is run (in either a session or job stream), the
input commands will be read from this file. Remember, before you can
initiate DICTPDE to accept commands from a command file, you must first
create the command file using the EDITOR and enter the DICTPDE commands
into the file.
DICTPDE can also be executed to accept commands from a command file that
contains the DICTPDE commands previously entered at the terminal. To do
so, redirect the list file DICTLOG to a disc file, and then run DICTPDE
interactively. If the file specified by DICTLOG does not already exist,
DICTPDE will build the file for you. All the commands entered
interactively for that session will be saved in this disc file in the
order you entered them. Before DICTPDE is run again, redirect DICTIN to
the disc file used for DICTLOG and reset DICTLOG. The next time DICTPDE
is run interactively, the commands will be read from the disc file as
they were entered in the previous session. This process is shown below:
1. FILE DICTLOG = command file Commands are written to this file.
2. RESET DICTIN Do this if DICTIN was directed to a
file.
3. RUN DICTPDE.PUB.SYS Run DICTPDE and enter the commands.
4. Exit DICTPDE Exit this session.
5. FILE DICTIN = command file DICTIN will take commands from this
file.
6. RESET DICTLOG DICTLOG must be reset.
7. RUN DICTPDE.PUB.SYS Commands are now taken from the
command file.
The data declarations generated by DICTPDE are echoed to $STDLIST (which
is the terminal when DICTPDE is run interactively) and written to an
output file. DICTPDE uses the output file DICTOUT (a fixed ASCII file
with 80 bytes) unless a different output file is specified. To specify a
different output file, you can either use an MPE file equation to
redirect DICTOUT or you can use the ALTER OUTPUT command-subcommand.
(ALTER OUTPUT is discussed in detail later in this section.) The
specified file can be a new file or an existing file. If the file is
new, DICTPDE will build that file as a fixed ASCII file with 80 bytes.
If the file already exists, DICTPDE will append the generated code to the
existing contents of that file.
The following is an example of how to run DICTPDE within a job stream.
Note that in this example, DICTPDE will accept commands from the command
file COMMANDS and write the generated declarations to the output file
OUTPUT.
!JOB CODEGEN, LYNN.ACCTS
!FILE DICTIN = COMMANDS
!FILE DICTOUT = OUTPUT
!RUN DICTPDE.PUB.SYS
MGR
!EOJ
Note that the Dictionary password must be supplied in the job stream
immediately after the MPE RUN command for DICTPDE. In the above case, the
password used is MGR. Also, remember to create the command file COMMANDS
with the EDITOR before streaming this job. (Don't forget to include an
EXIT command at the end of the command file to terminate DICTPDE.)