ID and required PAM pages
For the first installation, an ID with the name SYSFJAM and the default catalog ID must be created for openFT on the home pubset of the processor. If you are running multiple openFT instances on your system, you must set up the configuration user IDs of the instances so that they are the same as SYSFJAM (the restriction concerning the home pubset does not apply here). The IDs should be set up in a manner that prevents a SET-LOGON-PARAMETERS command being entered. The number of PAM pages required by this ID depends on:
the size of the request files and partner lists used and the required functionality, i.e., whether FTAC functionality is to be used. The openFT request queue SYSRQF has a default size of 12690 PAM pages while the option file SYSOPF requires 6 PAM pages and the partner list SYSPTF 1824 PAM pages. The FTAC file SYSFSA occupies at least 501 PAM pages.
the size of the log file SYSLOG (at least 501 PAM pages) which, in turn, depends on the number of transfer requests handled and on which sets are engaged (i.e. only FT sets, only FTAC sets, or both).
the size of the SYSFSI, SYSKPL, and SYSKEY files (by default, a total of 54 PAM pages), and on the number of key pairs (SYSPKF files) created.
the type and number of trace functions activated.
It is therefore advisable to allow PAM page overruns for the ID SYSFJAM.
Access to public keys
In order to be able to access public keys, the FT administrator needs access to the SYSPKF files and the SYSKEY library on SYSFJAM or on the configuration user ID. If he/she does not have privileges granting him/her access to operating system resources, the FTAC admission profiles should be set up to grant him/her access.
Starting and stopping the FT subsystem
openFT requires a subsystem catalog entry containing a subsystem declaration with the load time set to “AT-CREATION-REQUEST”. The FT subsystem must be explicitly loaded in a startup procedure (e.g. CMDFILE).
When an FT instance is stopped, (particularly by using /STOP-SUBSYSTEM FT) all the file locks held by openFT (see "Protection mechanisms against data manipulation") are cleared and, on loading an instance (e.g. by using /START-SUBSYSTEM FT), the locks are reset for files affected by existing requests. The FT or system administrator must therefore observe the following:
On starting the FT subsystem, all pubsets that contain data that is to be used in the event of a restart must be available.
On the other hand, the loading must also occur early enough to ensure that the files to be transmitted are protected in time. This also applies to the transfer files of all configured openFT instances.Unloading an FT instance should be done as late as possible, but before the export of the pubsets on which the files to be transmitted are located.
Result lists
The job class JBCLLST should be generated with a small maximum processing time and, if possible, a high selection priority for printing result lists. This job class should be accessible to all FT users. The high priority (JOBPRIORITY operand in job class setup) ensures that jobs of this type are quickly started. A low maximum processing time (CPU-TIME operand in job class setup) prevents these jobs blocking the processor for a prolonged time.
Follow-up processing
For follow-up processing initiated by the openFT, you should generate the job class JBCLJOB with low maximum processing time and, if necessary, a high selection priority. If you do not do this the default job class will be used for follow-up processing. You should start extended, CPU-intensive follow-up jobs as enter jobs using the job classes which are available as standard in the BS2000-System.
/BCMAP FUNCT=INIT,MAXMAP=500
If initialization is to be done using other values, it must take place before the first START-FT command.