Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Providing the OPFT subsystem

&pagelevel(4)&pagelevel

The commands in the dialog tasks with which FT users and administrators work (NCOPY or an alias, or FTHELP or FTTRACE) are encrypted for the purposes of internal communication with openFT. This encryption (and decryption) is performed by the OPFT subsystem. In addition, OPFT administers the running openFT instances. Optionally, it is also possible to use the MSG_CRYPT parameter in the PARM library to activate message encryption. OPFT must be installed in the computer’s IPL. To do this, it is necessary to copy the members from OPENFT.LPALIB to SYS1.LPALIB or store them in a user LPALIB that is concatenated with this library.

  • IGX00211 (SVC handler)

  • OPFTIGX

  • OPFTINIT (Startup routine of the OPFT subsystem)

  • OPFTSUB (Subsystem handler)

It is important to avoid name conflicts with load modules that already exist in SYS1.LPALIB.

The portal to the subsystem is implemented via SVC 109 with "extended code 211". If "extended code 211" is already used for a different purpose in your system then the samples in openFT provide a procedure with the name LINKIGX that allows you to generate other, alternative "extended codes" that can be set in the PARM file with ’OPENFT_SVC='.

The subsystem is initialized the first time openFT is started after IPL. The start of the subsystem is confirmed by a console message. After initialization, the subsystem remains active until the next IPL. No further administration is necessary and, in particular, the subsystem does not require any start parameters.