GDSX (Extended General Device Support) Manual

Using Pseudo Procedures in a TS/MP Environment
Extended General Device Support (GDSX) Manual—529931-001
D-3
Binding
The user code is compiled when this command is entered at the TACL prompt:
> OBEY COMP1
Binding
The second step is binding TSCODE and USCODE1 together into a GDSX object file
named OGDS1. In the following example, the commands to do this were entered in a
file called BIND1:
ADD * FROM $SKY.LINZ.TSCODE
ADD * FROM USCODE1, DELETE
SET DATA 64 PAGES
SET INSPECT ON
SET SAVEABEND ON
SET SUBTYPE 30
BUILD OGDS1 !
CHANGE HIGHPIN ON IN OGDS1
The binding process occurs when a BIND command is entered at the TACL prompt,
specifying the BIND1 file with an IN option:
> BIND /IN BIND1/
Creating the Database
The third step is creating the database file for the TS/MP server:
> FUP PURGE $SKY.LINZ.TSTDAT
> FUP CREATE $SKY.LINZ.TSTDAT, TYPE K, REC 62, KEYLEN 11,
KEYOFF 0, EXT (20,20)
> FUP ALTER $SKY.LINZ.TSTDAT, AUDIT
The FUP ALTER command is necessary to establish the database as a file audited by
the TMF.
Starting NonStop TS/MP
The fourth step is configuring and cold starting the TS/MP application. The following
configuration commands were entered in a file named PATHIN:
SET PATHMON BACKUPCPU 1
SET PATHWAY MAXTCPS 2
SET PATHWAY MAXTERMS 10
SET PATHWAY MAXPROGRAMS 0
SET PATHWAY MAXLINKMONS 1
SET PATHWAY MAXEXTERNALTCPS 1
SET PATHWAY MAXSERVERCLASSES 2
SET PATHWAY MAXSERVERPROCESSES 4
SET PATHWAY MAXSTARTUPS 10
SET PATHWAY MAXPATHCOMS 3
SET PATHWAY MAXASSIGNS 5
SET PATHWAY MAXPARAMS 5
START PATHWAY COLD !