
F986110.JCPRTQ Is Not The Print Queue
There’s been a JDE table column usage scandal under our noses the whole time!
I’ve been working with JDE for 24+ years and I’ve never noticed that in the F986110, the JCPRTQ (Data Dictionary = Print Queue) column is used to store the port number of the JDE services running on the execution host. It has nothing to do with the Print Queue.
I’ve seen documentation that it’s been this way since at least 2002 (JDEList.com).

The F986110 has 20 columns. A brief description is below and the full table definition is on jde.erpref.com.
Field | Description | Data Type |
---|---|---|
JCJOBQUE | Job Queue | String |
JCJOBPTY | Job Priority | String |
JCJOBSTS | Job Status | String |
JCENHV | Environment Name | String |
JCUSER | User ID | String |
JCPSWD | Password | String |
JCJOBTYPE | Job Type | String |
JCSBMDATE | Date – Job Submitted | Date |
JCSBMTIME | Time Job Submitted | Numeric |
JCJOBNBR | Server Job Number | Numeric |
JCEXEHOST | Execution Host Name | String |
JCORGHOST | Origination Host Name | String |
JCPROCESSID | Server Process ID | Numeric |
JCACTDATE | Date – Last Task | Date |
JCACTTIME | Time – Last Task | Numeric |
JCSRVBLOBA | EnterpriseOne Foundation Blob Buffer | Binary (Blob) |
JCFUNO | Object Type | String |
JCPRTQ | Print Queue | String |
JCFNDFUF1 | Foundation – Future Use 1 | String |
JCFNDFUF2 | Foundation – Future Use 2 | String |
It looks to me like JDE didn’t have enough “Future Use” columns and had to use what was there because of their own limitations on creating tables/files.
Did you know this already?
Any idea what the story behind this might be?
Average Rating