The AUTO_FORM subsystem contains one job for each monitored output queue. The jobs inside the subsystem is not taking any processing power while waiting, as they are waiting for an entry in a data queue connected to the relevant output queue (and placed in the same library as the monitored output queue).
You can view the jobs in the subsystem with the command:
WRKACTJOB
- or even:
WRKACTJOB SBS(AUTO_FORM)
Or select option 12. Work with active subsystem AUTO_FORM from the Auto Forms Control menu.
Work with Active Jobs PMK250 17/06/18 17:14:42 CPU %: 2,4 Elapsed time: 00:00:43 Active jobs: 410
Type options, press Enter. 2=Change 3=Hold 4=End 5=Work with 6=Release 7=Display message 8=Work with spooled files 13=Disconnect ... Current Opt Subsystem/Job User Type CPU % Function Status AUTO_FORM QSYS SBS 0,0 DEQW PRT01_IN AFCOPER BCH 0,0 PGM-AFC700 DEQW PRT02_IN AFCOPER BCH 0,0 PGM-AFC700 DEQW TOOLSHED AFCOPER BCH 0,0 PGM-STRTOOLSS DEQW TOOLSHED AFCOPER BCH 0,0 PGM-STRTOOLSS DEQW
Bottom Parameters or command ===> F3=Exit F5=Refresh F7=Find F10=Restart statistics F11=Display elapsed data F12=Cancel F23=More options F24=More keys
|
In the Auto Forms subsystem a couple of TOOLSHED jobs are running. They are java service jobs, which can be used by various InterForm400 functions. It is e.g. used for installing color images, that are not BMP or JPG. Java 1.6 (or higher) is required for this. A specific java version can be selected via the data area, APF3812/JAVA_HOME.
The logging of the Toolshed jobs can be setup to run in either production logging or debug logging. That is setup via these options from the InterForm400 Main Menu:
70. Configuration and licences
7. Configure java log settings
Here you see this screen:
Log library is APF3812home/LOG (JVALOG)
Type choices, press Enter.
Set log level. . . . . . . . . . LOGTYPE > *PROD
Bottom F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys
|
The possible values for the log type are:
*PROD
This is the selection, that you should normally use. When you select this, then the contents of the configuration file, /APF3812HOME/LIB/LOG4J.PROPERTIES.PRODUCTION in the IFS is copied to the file: /APF3812HOME/LIB/LOG4J.PROPERTIES. The configuration file is used for setting up the log level, the output file and all log settings.
*DEBUG
Use this if you (or an Interform400 consultant or programmer) want extra log data in the output. When you select this, then the contents of the configuration file, /APF3812HOME/LIB/LOG4J.PROPERTIES.TEST in the IFS is copied to the file: /APF3812HOME/LIB/LOG4J.PROPERTIES. The configuration file is used for setting up the log level, the output file and all log settings.
If you want to change the settings of either production (*PROD) or debugging (*DEBUG), then you should first of course take a copy of the file, and then edit either of the files:
/APF3812HOME/LIB/LOG4J.PROPERTIES.PRODUCTION or /APF3812HOME/LIB/LOG4J.PROPERTIES.TEST to change the logging properties as you want.
Detailed information about these LOG4J log files are found here: https://www.tutorialspoint.com/log4j/log4j_configuration.htm
A change of *PROD/*DEBUG is activated on the next restart of the Auto_Form subsystem.
The Toolshed jobs are described here: