HP 3000 Manuals HP 3000 Manuals
Running SDUTIL
SDUTIL may be run in either session or batch mode. These are explained
further on in this chapter. The following information applies to both
session and batch mode.
Run Options
When you run SDUTIL, you can specify one of several options through the
use of the PARM parameter. These options deal with the processing of the
commands and the handling of any errors encountered. The parameter
values and their meanings are shown in following table.
SDUTIL Run Options
----------------------------------------------------------------------------------------------
| | | |
| -1 | Parse Only | When SDUTIL is run with the parse-only option, no |
| | | dictionary or files are opened and no definitions |
| | | are copied. The commands issued are only parsed to |
| | | catch syntax errors. |
| | | |
----------------------------------------------------------------------------------------------
| | | |
| 0 | Execute and do not abort | If the PARM parameter is not specified, the default |
| | (Default) | is not to abort regardless of the number of errors |
| | | encountered. All the errors are reported, but |
| | | non-fatal errors will not terminate the program. |
| | | |
----------------------------------------------------------------------------------------------
| | | |
| 1 | Execute and abort on the | Aborts on first syntactical or operational error. |
| | first error | |
| | | |
----------------------------------------------------------------------------------------------
| | | |
| >1 | Execute and abort only if | Aborts at user-specified number of syntactical or |
| | the specified number of | operational errors. May abort before the error |
| | errors are found | count is reached if a fatal error is encountered. |
| | | |
----------------------------------------------------------------------------------------------
Note that the execute and abort options allow flexibility for you to
specify the exact number of errors that are considered acceptable.
Command Language
The general format of SDUTIL commands is either:
* a command, or
* one or more keyword oriented clauses (if required)
The System Dictionary Command Language is free formatted, i.e., the
command and keyword clauses may appear on a single line or on multiple
lines. For example, you can enter the DICTIONARY= keyword clause on the
same line as the FROM command as shown below,
>FROM DICTIONARY=sysdic.pub;
or you could enter it on a second line, like this:
>FROM
>>DICTIONARY=sysdic.pub;
Phrases. Commands and keyword clauses both are considered to be phrases,
and are defined as follows:
command An SDUTIL defined name which specifies the action to be
taken.
keyword clause An SDUTIL defined name which specifies a qualifying
value. It is a keyword followed by an ++=++ followed by
a keyword value list. A keyword value list is zero or
more values separated by commas. Values are user
defined names. Keyword clauses are separated by
semicolons.
Note that the order of these phrases is important. The command must
precede the keyword clauses. Keyword clauses, however, may be entered in
any order. For example, two keyword clauses 1) which specifies the
dictionary name, and 2) which specifies the scope, may be entered as
shown in either example 1 or 2.
Example 1
>FROM
>>DICTIONARY=sysdic.pub;
>>SCOPE=dict;
Example 2
>FROM
>>SCOPE=dict;
>>DICTIONARY=sysdic.pub;
Punctuation Characters. The following characters are legal for use when
punctuating SDUTIL commands or keyword clauses:
Character Description
. Command terminator. The period is used to signify the
end of a string of characters denoting a command. It is
optional for the commands: COMMENT, COMPILE, EXIT,
HELP, MERGE, PREVIEW, REDO, SHOW.
, Separates items in a list. The comma is used to
separate values in a keyword value list.
; Separates keyword clauses. If there are two or more
keyword clauses, there must be semicolons between them.
= Specifies a keyword and a keyword value pair. e.g.
DICTIONARY = sysdic
" Optional around passwords as long as the value can be
accepted as a valid System Dictionary name (ie. no
punctuation or invalid characters embedded); otherwise,
it is required. Use two quotes to represent an embedded
quotation mark in the password.
! Defaults target value(s) to the source value(s).
[[ ]] Blanks must be used to separate a command and its
keyword clauses. Any number of blanks may appear
between any name and any punctuation character.
[[RETURN]] Treated the same as a blank. Wherever a blank is legal,
a [[RETURN]] is legal except within a quoted password.
Running SDUTIL in Session Mode
To run the program, enter the following MPE command:
:RUN SDUTIL.PUB.SYS
SDUTIL will respond with the banner:
HP System Dictionary SDUTIL HP32256v.uu.ff -(C) Hewlett-Packard Co. 1985
A prompt character (>) is displayed (SDUTIL prompts are described below),
indicating that SDUTIL is ready for a command. At this point, you may
enter one of the following commands:
COMMENT MERGE-OPTIONS
COMPILE-OPTIONS MERGE-TO
COMPILE-TO PURGE
EXIT REDO
FROM RENAME
HELP SHOW
: (any MPE Command)
If any other command is entered, SDUTIL will issue an error message. The
functions and abbreviations of these commands are listed in the table at
the beginning of Chapter 3.
SDUTIL Prompts. The following prompts are used by SDUTIL:
Prompt Description
> Command prompt. SDUTIL is expecting a command.
>> Command continuation prompt. SDUTIL is expecting a
clause to complete the command.
Special Character Responses. The following characters have special
meanings when used in response to an SDUTIL prompt:
Character Description
< Control X > Ignores the line on which the < Control X > was typed.
The system types three exclamation points (!!!) and
then waits for you to reenter the data for the line.
< Control Y > Prints the message "< Control Y >" and returns to the
highest prompt (>) level. In response to the >> prompt,
the command is terminated without executing. In
response to the > prompt, no action is taken, but the >
prompt is reissued.
During a merge or preview, hitting < Control Y > will
terminate the merge or preview process. During a
compile < Control Y > is disabled.
Running SDUTIL in Batch Mode
SDUTIL may be run in batch mode, via a job file. An example of a job
file is shown below. In this example, SDUTIL reads commands from an
input file SDIN, which in the example has been redirected to the file
COMMANDS.
The PARM parameter is used to specify the action of the job if an error
is encountered. In the example, the program is aborted if 10 errors are
found. Refer to the text earlier in this chapter for details on the
various run options.
Finally, the JCW job control word shows whether the system executed
successfully or terminated abnormally.
!JOB SDJOB,DICK/WRITER.SDUSER
!FILE SDIN = COMMANDS
!CONTINUE
!RUN SDUTIL.PUB.SYS;PARM=10
!IF JCW = FATAL THEN
! TELL DICK.SDUSER Fatal Dictionary Error
!ELSE
! TELL DICK.SDUSER Dictionary Job Completed
!ENDIF
!EOJ