The file SINPRC.EDT.170
contains a procedure which can be used to install a private version under any user ID. Private versions should only be used for test purposes and should not lead to the coexistence of two EDT versions.
Before this procedure is called, at least the following files must be available under the installation ID for the private EDT version:
SYSPRG.EDT.170
andSYSPRG.EDT.170.EDTU
(starter phases)SYSLNK.EDT.170
(module library)SYSLNK.EDT.170.INIT
(module library containing the EDT initialization routine)SYSREP.EDT.170
(REP file)
For reasons of compatibility, a file named EDT
is also used as the starter phase for compatibility mode (as in a public installation) if no file named SYSPRG.EDT.170
is present under the installation ID. However, it is advisable to use the name SYSPRG.EDT.170
since this is the only way of creating multiple private installations of different EDT versions under a single installation ID.
The procedure can be called under the installation ID or TSOS:
/CALL-PROCEDURE FROM-FILE=SINPRC.EDT.170, - /PROCEDURE-PARAMETERS=(USERID=userid,ORIG=Y|N, - /EDT=edt,EDTU=edtu,EDTLIB=edtlib,INILIB=inilib, /REPFILE=repfile)
The procedure parameters can be specified directly or via parameter prompting. The parameters EDT
, EDTU
, EDTLIB
, INILIB
and REPFILE
only need to be specified if ORIG=N
has been specified.
userid | Installation ID under which the private EDT version is to be installed. |
ORIG=Y | Specifies that the provided original files (under the installation ID) are to be |
ORIG=N | Specifies that copies of the provided original files are to be created and that the |
edt | Name of the copy for the private starter phase for compatibility mode (if the |
edtu | Name of the copy for the private starter phase for Unicode mode (if the original |
edtlib | Name of the copy for the private module library (if the original files are not to be |
inilib | Name of the copy for the private module library containing the EDT initialization |
repfile | Name of the copy for the private REP file for EDT (if the original files are not to |
The private EDT version can be started with the command
/START-PROGRAM FROM-FILE=$userid.name-private-starterphase
The installation procedure freezes all the references to the logical names defined in IMON for the private version. This is particularly important if a SYSDAT.EDTSTART
assignment has been defined. Any EDT start procedure defined centrally in this way is therefore not executed by the private version.
Programs that want to call this private EDT version must either link the connection module IEDTGLE
from the created module library or dynamically load it from this library using the ENTRY name IEDTGLE
. When doing this it is essential to specify the parameter SHARE=NO
in the BIND
macro.
Programs that want to call the private EDT version as a subroutine and dynamically load EDT from $.EDTLIB
using a BIND
(not LINK
) macro call can assign a private module library with the following command:
/SET-FILE-LINK LINK-NAME=BLSLIBnn,FILE-NAME=library
where nn=00..99
. This procedure is only possible if EDT is not loaded as a subsystem.