Examples and Tips

We will now present a few examples of NZCOM command lines to help

make clear how the syntax works. As we discuss these examples, we

will point out some tricks that can simplify or speed up the operation of NZCOM.

Loading _{a Special}

_{NZ-COM Configuration}

The following command line could be used _{to load a special configura-}

tion defined by SMALL. ENV.

_It

is _{assumed that the definition and the}

modules SMALLFCP _{.ZRL and} SMALLRCP. ZRL tbat it uses _{are included} in

the library SPECIAL _{.LBR which resides in directory A15:}

. Other than

those specific modules, al) _{other modules are the default files kept as}

usual in NZCOM _{.LBR in} AO: . Here

is _{the command line that loads this}

system:

NZCOM A15 :_{SPECIAL.LBR SXALL.ENV} SMALLFCP _.ZRL SMALLRCP.ZRL AO: NZCOM.LBR

_/V<cr>

We have used expjicit drive specifications for both libraries so that

nzcom will not. _{have to waste anv time searching for them along the} -

path.

By including an explicit file type in the term SMALL.ENV we gain two

advantages. First we make sure that files with the names SMALL. _ZCI

or SMALL. ZCX are not loaded (against our intent,ions here). Second, in case the file is accidentally not in the library, we prevent NZCOM from

performing a rather Jengthy search for files with all three descriptor

file t.ypes

over the entire search route before the error is detect,ed and reported.

The inclusíon ofthe _term AO: NZCOM.LBR at the _{end of the}jfíle _{list is uery}

important. Without it, the current library at the end of the list would have been A15 :_S!(ALL .LBR. _{The default files required for the remaining}

modules would not have been found, since NZCOM _{would not have looked}

automatically in NZCOM .LBR.

The option

_"lv"

_{at the end makes sure that} NZCOM _{displays a detailed}

load map showing how the system was generated.

If

one were going to load the system configuration defined by this com- mand more than just one or two times,

it

would make sense to add this

command line to the ALIAS .CMD _{file under an alias name like} SMALL.

This would save a lot of typing and prevent a lot of errors, such as for-

getting to include the NZCOM. LBR _{term or typing one of the file names}

incorrectly.

Loading Special Modules

The following command is _{used to load a}

new group of command mod- ules.

_It

_{assumes that} we develop our RCPS _in a directory with the name RCP and that we keep the ones we have completed in a library called RCPS .LBR.

_It

_{assumes that} we only have a few versions of FCP and that

we prefer to leave them as individual files in our main directory AO: . NZCOM RCP :RCPS .LBR RCP-D _.ZRL AO :_{FCP-1 .ZRL< cr>}

By including _{an explicit} AO: _{in front of the FCP-1.ZRL term we gain}

speed. NZCOM _{would normally look for the file first in} RCPS .LBR _and

only then search the path. By including the correct directory prefix,

we get NZCOM _{to loca.te} t.he _{file immediately.}

Loading _{a New} Command Processor

Users of Z-System are accustomed to the idea of loading new RCP and FCP _modules.

_It

_{may come as something of} a surprise that NZCOM can

just as easily load a _{new command processor.} The NZ-COM distribu-

tion package includes a library called ZCPR34.LBR that contains sev-

eral alternative command _{processor configurations. One of them sup-} ports a nonstandard form of SUBMIT processing that allows arbitrarily

long SUBKIT files,6 To use the special command _{processor file named} Z34LONG _{.ZRL we would use the command line}

NZCOM AO :_ZCPR34.LBR Z34LONG _{.ZRL< cr>}

It

would probably be useful in the long _{run to define an alias in} ALIAS .CKD _{under a}

name like LSUBCPR that would generate this com- mand line for us.

6_OrdinaryCP/M SUBKIT files _may not contain _more than 128 command lines, the number _{that can} be included in _{a single} file _"extent".

6.4. _{PATCHING NZCOM.COM} 69

6.4

Patching

NZCOM.COM

There are several options in NZCOM. COM _{that are controlled by config-}

uration bytes in the code. _{You can install changes in several ways.} The most convenient method uses a patching utility like ZPATCH. You

can also use facilities already provided by Z-System. You can load NZCOM _{into memory using the} GET _command, make the changes using the POKE _{command, and then save the modified image using the} SAVE

utility. _{Before you do this, however, you have to know how large the} file NZCOM.COM is _{in records. The} SDZ _{directory program} with the

_"lc"

option _{will give you this information.}

We will _{now describe the current} configuration areas in detail. This

information is _{correct for} tthé _{initial release version of} NZ-COM, _{and it}

is quite possible that future versions will have additional _{or different} configuration options. You should always consult the file RELEASE. NOT,

if

one is present, for more recent information.

In document NZ COM Z System Manual 1988 pdf (Page 71-73)