Understanding Batch Process Administration for UNIX or Linux
Administering batch processes involves knowing what processes run when JD Edwards EnterpriseOne starts, where files are placed before and after printing, and how to watch those processes.
Processes running for JD Edwards EnterpriseOne are owned by the user who started the JD Edwards EnterpriseOne software. The user ID for this user is set up during the installation of the software, and is site dependent. When JD Edwards EnterpriseOne starts, these processes start and run under the environment and security of the user who started them:
Process |
Description |
|---|---|
jdenet_n |
The network listener that listens for connection requests. |
jdenet_k |
The jdenet_n process starts the jdenet_k processes, which control JD Edwards EnterpriseOne components, such as the security server, the transaction monitor, and data replication. |
Use the jdejobs command to monitor current batch processes. This example is a sample output:
JDE920 (EnterpriseOne Admin,,,): Semaphores: 1 Shmem Segs: 5 Msg.Queues: 13 Jobs on ent-1: 6137 ttyp6 0:43 jdenet_n 6163 ttyp6 0:44 jdenet_k 6188 ttyp6 0:44 jdenet_k 7213 ttyp6 2:12 jdenet_n 7241 ttyp6 0:47 jdenet_k 9008 ttyp6 1:36 jdenet_n 9009 ttyp6 0:45 jdenet_k 11042 ttyp6 0:09 runbatch
In the output, jdenet_n jobs are listening for requests, and four jdenet_k jobs are handling various JD Edwards EnterpriseOne kernel functions. A runbatch job is processing a report.
The first column of the output displays the UNIX process ID that is associated with each process. For more information about a particular process, look for the files in the log directory that have the same process ID as part of the file name.
All output from each report, regardless of whether it is a preview, is placed in the PrintQueue directory under the installation directory of JD Edwards EnterpriseOne before printing. Depending on the JDE.INI settings for the workstation, the job might not be deleted after printing.
Jobs are printed to the location specified in the JDE.INI file unless a JD Edwards EnterpriseOne program overwrites them. Use the Printers program to specify default printers.
Two settings in the JDE.INI file for the workstation tell the server whether to print the report immediately upon completion, and whether to save the output from the report or delete it. These settings are as follows:
[NETWORK QUEUE SETTINGS]
SaveOutput=TRUE
PrintImmediate=TRUE
Setting SaveOutput to TRUE causes the JDE.INI to hold the jobs within the PrintQueue directory until the user explicitly deletes them. Setting PrintImmediate to TRUE tells the JDE.INI file to print the job immediately after completion of the report.
You can list output files. The returned data looks similar to this:
R014021_XJDE0001_4554_PDF R014021_XJDE0001_4554_PDF.jde.log R014021_XJDE0001_4554_PDF.jdedebug.log R31515_XJDE0001_4566_PDF R31515_XJDE0001_4566_PDF.jde.log R31515_XJDE0001_4566_PDF.jdedebug.log R94NM08_XJDE0008_4568_PDF R94NM08_XJDE0008_4568_PDF.jde.log R94NM08_XJDE0008_4568_PDF.jdedebug.log R94NM10_XJDE0016_4526_PDF R94NM10_XJDE0016_4526_PDF.jde.log R94NM10_XJDE0016_4526_PDF.jdedebug.log R94NM10_XJDE0016_4526_PDF.ps R94NM10_XJDE0016_4527_PDF R94NM10_XJDE0016_4527_PDF.jde.log R94NM10_XJDE0016_4527_PDF.jdedebug.log R94NM10_XJDE0016_4527_PDF.pcl
The file names in this example are the actual reports that were generated when the job was executed. The file naming conventions are as follows:
Segment |
Description |
|---|---|
R31515 |
The report name |
XJDE00001 |
The report version executed |
1914 |
The request number assigned by JD Edwards EnterpriseOne |
A PDF file, meant for viewing on the workstation |
|
.jde.log |
The file extension that indicates the log file for the report |
.jdedebug.log |
The file extension that indicates the debug log for the report |
.ps |
The file extension that indicates a file formatted for postscript printing |
.pcl |
The file extension that indicates a file formatted for pcl printing |
You should encourage workstation users to use the SaveOutput=FALSE entry in their jde.ini file. If users at workstations decide to save their output, they should periodically delete the entries through JD Edwards EnterpriseOne. When you delete .PDF files from the operating system, the corresponding JD Edwards EnterpriseOne print job entries in the Job Control Status Master table (F986110) are not deleted. You must manually delete these entries from JD Edwards EnterpriseOne using the Work with Servers program (P986116).