The OPFT subsystem is used for secure encryption of the user command and to provide the "right" user ID for later authentication (RACF etc.).
Components of the subsystem
The subsystem consists of three components (load modules) which must be assigned to the LPALIB when the computer is started (IPL):
OPFTINIT
OPFTSUB
IGX00nnn, where IGX00211 is permanently predefined.
If IGX00211 is already assigned, another module with a number nnn from the range 200 ... 255 with the basis OPFTIGX must be linked (see LINK skeleton).
Following IPL and the first startup of openFT, the status of the subsystem can be displayed using the following system command:
D SSI,SUB=OPFT
The problems described below can mainly be attributed to inadequate generation or interpretation and are thus referred to as "generation error type n" (n=1 through 5).
Generation error type 1
After openFT has been started, the following error messages are output one after the other:
FTR4199 OPENFT: SYSTEM ERROR. ERRORCODE ADM: 3410,nnnn
FTR4121 OPENFT: TERMINATED.
However, no message of the type OPENFT: SUBSYSTEM... is displayed on the system console.
Cause and possible solution
A subsystem status output further localizes the problem:
If no information on the OPFT subsystem is available, the LPALIB is not or is not fully equipped with the modules listed under "Components of the subsystem".
If the subsystem is of the type "static", it was created explicitly in the generation.
If the subsystem does not have the attribute COMMANDS=REJECT, it was also created in the generation.
Omitting these specifications concerning the subsystem and the SVC in the generation solves the problem. An IPL is required.
Generation error type 2
As with type 1, messages FTR4199 and FTR4121 are issued. In contrast to type 1, the following three messages are displayed on the system console:
IEW4000I FETCH FOR MODULE OPFTSUB FROM DDNAME STEPLIB FAILED BECAUSE INSUFFICIENT STORAGE AVAILABLE OPENFT: SUBSYSTEM CREATION FAILED OPENFT: RC / REASON 00000016 / 00000000
Cause and possible solution
With this problem, insufficient space is available in the common service area (CSA) to load the subsystem.
Increasing the size of the CSA pool in the generation solves the problem. A renewed IPL is required.
Generation error type 3
Following successful operation of openFT, the session is terminated by FTTERM and then restarted. Subsequently messages FTR4199 and FTR4122 are issued again, but no system messages are displayed on the console.
The subsystem status query shows that it is inactive.
Cause and possible solution
In this case the modules of the subsystem were placed not in the LPALIB but in the LINKLIB, which then led to the subsystem being "unloaded" when FTTERM took place.
Taking the modules over into the LPALIB when the next IPL takes place solves the problem.
Generation error type 4
The dialog connection to openFT is rejected with one of the following error messages:
FTR4193 OPENFT: OPENFT NOT AVAILABLE
FTR4196 OPENFT: DIALOG TASK VERSION INCOMPATIBLE
At the same time the CONN file in the connection to the client was dispensed with.
Cause and possible solution
In this case no standard instance STD was generated, but such an instance is necessary for a connection without a CONN file.
After the standard instance has been generated, a dialog connection can be established to this instance without a CONN file.
Generation error type 5
Starting openFT leads immediately to abortion with a dump.
Cause and possible solution
In this case the modules of the subsystem were copied from the openFT LOADLIB to the LPALIB without at least deleting OPFTSUB in the LOADLIB. As a result the system - if the LOADLIB is apf-authorized - takes OPFTSUB from the LOADLIB and not from the LPA. This leads to address error 0C4.
After OPFTSUB has been deleted in the LOADLIB, a new IPL must be created.