Document 1502927.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

Copyright (c) 2022, Oracle. All rights reserved. Oracle Confidential.

E1: UBE: Common UBE Submission Issues (Doc ID 1502927.1)

In this Document

Purpose
Troubleshooting Steps
Common Issues When Submitting UBEs
All Server Platforms
Issue 1: Invalid Job Queue
Issue 2: Invalid Enterprise Server name in F986130
Issue 3: Unable to Insert Job Record in F989110 Because of Duplicate Job Number
Issue 4: Unable to Save Temporary Files on the Enterprise Server
Issue 5: Security Server is Disabled in Local JDE.INI
Issue 6: Spec Errors When Submitting from EnterpriseOne Web Client
Issue 7: Not Enough Disk Space on Web Server
Issue 8: "Not Authorized to Run Report" Errors in Server Process Log
Issue 9: Error "There was a problem with the server while running the business function
IsXMLP2SPPresent"
Issue 10: Error "There was a problem with the server while running the business function
IsPrinterMappingPresent"
Issue 11: Error "Security token not valid" when Submitting UBEs from a Windows/Fat Client
Issue 12: All UBEs fail with error, *ERRROR* LaunchUBE: LaunchUBE failed- JDEKDCL.h/UBEERRORCODE
error 22 user
Unix and Linux Server Platforms
Issue 1: Server Name Mismatch in F986130
Issue 2: All UBEs fail with error, *ERRROR* LaunchUBE: LaunchUBE failed[4] - Invalid Queuename - not
defined for server
AS/400 Server Platform
Issue 1: UBEs fail to Submit when SQL Server Mode is Enabled
Issue 2: AS/400 User Permissions Issues
Issue 3: Custom Job Queue outside System Library on AS400
Issue 4: Other AS/400 Issues
Other Less Common Issues
References

APPLIES TO:

JD Edwards EnterpriseOne Tools - Version SP24 and later

Information in this document applies to any platform.

PURPOSE

This document provides troubleshooting information and solutions to common issues that occur when submitting UBEs.
UBE submission issues are any issues that prevent a batch record to be added to the Job Table F986110. If a job record
is added to this table and it can be seen from Work with Submitted Jobs (WSJ) application, then the submission is

1 of 12 8/7/2022, 9:08 PM
Document 1502927.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

considered to be successful. Any problem that happens after the record is added is considered a UBE processing or
runtime issue.

For more information on the UBE Submission process refer to Doc ID 1498831.1

For information and issues that happen while processing the UBE refer to Doc ID 1502974.1 and Doc ID 1502985.1

TROUBLESHOOTING STEPS

Common Issues When Submitting UBEs

The majority of issues related to UBE Submission will result on the following error messages on EnterpriseOne clients:

Web Client: ERROR / Your report has NOT been submitted successfully.
Windows Client: Remote Job / An error occurred submitting batch REPORTID, VERSIONAME to SERVERNAME

When this happens the following errors will be found in client log, JAS logs or in the log created by the server process
which tried to submit the UBE on the server itself (report interconnect calls, business functions, SCHEDULER kernel,
RUNUBE and RUNUBEXML).

Windows client and server process logs:

KNT0000107 - Remote batch process could not be submitted on SERVERNAME

...
KNT0000105 - JDENET_SendMsg failed. Error = 8
...
KNT0000106 - JDENET_ReceiveMsg failed. Error = 11

Web client:

[SEVERE] USERID - [KERNEL] *ERRROR* LaunchUBE: LaunchUBE failed- JDEKDCL.h/UBEERRORCODE error XX; job
Number = JOB# user:USERID Env:ENVIRONMENT
[SEVERE] USERID - [JAS] SubmitUBE.launchUBE() : Exception thrown during UBE submission! | Report Name :
REPORTID, Version Name : VERSIONNAME, Server Name : null, User Name : USERID
...
[SEVERE] USERID - [KERNEL] *ERRROR* LaunchUBE: Fatal: Internal LaunchUBE error. user:USER Env:JPD900
[SEVERE] USERID - [JAS] SubmitUBE.launchUBE() : Exception thrown during UBE submission! | Report Name :
REPORTID, Version Name : VERSIONNAME, Server Name : null, User Name : USERID
com.jdedwards.system.kernel.LaunchUBEException: Fatal: Internal LaunchUBE error.

Even though these symptoms are common to most issues related to job submission, their causes may vary. This is the
reason it is important to know the process in order to understand the potential points of failure.

A powerful tool in diagnosing submission issues is the UBEERRORCODE error number found in JAS logs when
submitting UBEs from a web client. These are the known codes and their meanings:

ERROR MESSAGE AND CODE Meaning Common Issue

(JAS log)

JDEKDCL.h/UBEERRORCODE NO ERROR Job submitted successfully. This

error 0 message is not typically logged.

2 of 12 8/7/2022, 9:08 PM
Document 1502927.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

JDEKDCL.h/UBEERRORCODE VERSION NOT SUPPORTED

error 1

JDEKDCL.h/UBEERRORCODE INVALID CODEPAGE

error 2

JDEKDCL.h/UBEERRORCODE INVALID PACKET Network communication issues

error 3

JDEKDCL.h/UBEERRORCODE INVALID QUEUE NAME The default job queue does not
error 4 exist or is invalid

JDEKDCL.h/UBEERRORCODE GET ENVIRONMENT FAILED Environment initialization failed

error 5

JDEKDCL.h/UBEERRORCODE GET USER FAILED User session failed

error 6

JDEKDCL.h/UBEERRORCODE CONVERT BLOB FAILED

error 7

JDEKDCL.h/UBEERRORCODE OPEN F986110 FAILED Unable to access F986110

error 8

JDEKDCL.h/UBEERRORCODE FOPEN FAILED Unable to open file

error 9

JDEKDCL.h/UBEERRORCODE FWRITE FAILED Unable to write to file

error 10

JDEKDCL.h/UBEERRORCODE CREATE F986110 BLOB FAILED

error 11

JDEKDCL.h/UBEERRORCODE SECURITY CHECK FAILED ON

error 12 AS/400

JDEKDCL.h/UBEERRORCODE CHGOBJOWN FAILED ON

error 13 AS/400

JDEKDCL.h/UBEERRORCODE RVKOBJAAUT FAILED ON AS/400

error 14

JDEKDCL.h/UBEERRORCODE INSERT TO F986110 FAILED Usually seen when trying to

error 15 insert a duplicate record but may
also occur for other reasons such
as ORA-01653

JDEKDCL.h/UBEERRORCODE COMMUNICATINO TO QUEUE QUEUE kernel is not responding

error 16 KERNEL FAILED

JDEKDCL.h/UBEERRORCODE GET PATHCODE FAILED

error 17

JDEKDCL.h/UBEERRORCODE SPEC FORMAT NOT SUPPORTED

error 18

JDEKDCL.h/UBEERRORCODE INVALID REPORT

error 19 INTERCONNECT

JDEKDCL.h/UBEERRORCODE INVALID PROCESSING OPTIONS

error 20

JDEKDCL.h/UBEERRORCODE INVALID AUDIT INFORMATION

error 21

3 of 12 8/7/2022, 9:08 PM
Document 1502927.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

JDEKDCL.h/UBEERRORCODE INVALID SECURITY

error 22 INFORMATION

JDEKDCL.h/UBEERRORCODE INVALID PRINT INFORMATION

error 23

JDEKDCL.h/UBEERRORCODE INVALID UBE VARIABLE

error 24

JDEKDCL.h/UBEERRORCODE GET JOB NUMBER FAILED There were issues reading from
error 25 F986111. Example UBE kernel
fails to read F986111:
OCI0000017 - Unable to execute
statement for describe - SELECT
SVM920.F986111.*, ROWID
FROM SVM920.F986111 WHERE (
JCEXEHOST = :KEY1 ) ORDER BY
JCEXEHOST ASC FOR UPDATE OF
JCJOBNBR

JDEKDCL.h/UBEERRORCODE FAILED TO SEND MESSAGE TO METADATA kernel not responding

error 26 METADATA KERNEL

If available, these error codes can lead you directly to the root cause of the issue.

For database related errors such as error 11 or error 15 , UBE kernel Logs will show you exact database errors such as:

OCI0000179 - Error - ORA-1: unique constraint (SVM900.F986110_PK) violated

Or

Error - ORA-01653: unable to extend table SVM910.F986110 by 1024 in tablespace SVM910T

JDB_DRVM.C1005 JDB9900401 - Failed to execute db request

JDB_EXET.C6109 JDB3400009 - Failed to perform Insert for F986110

JDEKNUBE.C1338 KNT0000086 - JDB_InsertTable failed for F986110

OR

OCI0000178 - Unable to execute - INSERT INTO SVM910.F986110 (JCJOBQUE, JCJOBPTY, JCJOBSTS,

JCENHV, JCUSER, JCPSWD, JCJOBTYPE, JCSBMDATE, JCSBMTIME, JCJOBNBR, JCEXEHOST, JCORGHOST,
JCPROCESSID, JCACTDATE, JCACTTIME, JCSRVBLOBA, JCFUNO, JCPRTQ, JCFNDFUF1, JCFNDFUF2) VALUES
(:BND1,:BND2,:BND3,:BND4,:BND5,:BND6,:BND7,:BND8,:BND9,:BND10,:BND11,:BND12,:BND13,:BND14,:BND15,:BND16
907/-171612464MAIN_THREAD Thu Jan 16 06:51:22.594494dbperfrq.c477
OCI0000179 - Error - ORA-01691: unable to extend lob

You should then investigate with help of your Database Administrator , why these errors such as ORA-01653 or ORA-1
appear in logs. E.g.

Refer Issue 3 below or refer following documents:

Doc ID 1025288.6 Troubleshooting Guide - 'Unable to Extend / Create' Errors and Doc ID 151994.1 Overview Of
ORA-01653: Unable To Extend Table %s.%s By %s In Tablespace %s

You may also refer ORA errors resolutions here : ORA ERROR REFERENCE

In the following sections you will find known issues. Some of these issues are specific to the server platform.

All Server Platforms

4 of 12 8/7/2022, 9:08 PM
Document 1502927.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

Issue 1: Invalid Job Queue

If for some reason the job queue the UBE defaults into does not exist in F986130 or in case of AS/400 servers is not
defined at the OS level, the job will fail to submit. This can be further verified by reviewing the UBE kernel log for
queries against table F986130. Typically in these cases you will find the following messages in the UBE kernel log:

OneWorld Xe and ERP8:

JOBQ "INVQUEUE" does not exist - the job was not submitted

EnterpriseOne 8.9 and later:

QUEUE05000030-Failed to FetchKeyed for ENTSERVER_6016_INVQUEUE_ from F986130

KNT0010080 - Queue ENTSERVER_6016_INVQUEUE_ is not defined in F986130

For more detailed information about how EnterpriseOne determines the appropriate Job Queue please review Doc ID
643483.1 E1: UBE: Job Queue Precedence and Inheritance for EnterpriseOne.

Changing the job queue to which the version defaults to or setting up the correct job queue in P986130 or AS/400
server will resolve the problem.

Also make sure that the appropriate queue type is defined in F986130 based on the underlying OS of server.

Issue 2: Invalid Enterprise Server name in F986130

If you try to change your enterprise server by assigning it an ALIAS in HOSTS file or DNS server you might run into
problems submitting UBEs to that enterprise server.

Usual symptom besides the inability to submit UBEs to that server are the following messages in UBE kernel / RUNUBE
log:

QUEUE05000030-Failed to FetchKeyed for SERVERNAME_6015_QUEUE_ from F986130

KNT0010080 - Queue SERVERNAME_6015_QUEUE_ is not defined in F986130

...
QUEUE00600010a -No queues defined in F986130 for server 'SERVERNAME' and port '6017'.

The reason this happens is because when server processes start they automatically retrieve the ACTUAL server name
from the operating system (gethostname). This process bypasses any alias you might have defined elsewhere. Oracle
support does not recommend you use a server alias. Make sure you the correct name at the time you install your
servers as changing the name after the fact might require updates in several EnterpriseOne tables and is not supported
by Oracle. For reference, some suggestions are given in the issue below Server Name Mismatch in F986130.

Issue 3: Unable to Insert Job Record in F989110 Because of Duplicate Job Number

This issue may happen when the UBE kernel is unable to obtain a job number from server map table F986111 (Job
Number File) or when the next job number in F986111 and job numbers already in F986110 (Job Table) are out of sync
or overlap. These are the errors you will likely find in the UBE kernel log file:

JDB3400009 - Failed to perform Insert for F986110

KNT000086 - JDB_InsertTable failed for F986110

In some cases if for some reason a job number cannot be retrieved from F986111, the UBE kernel may assume it to be
'0' (zero). What will happen then is that the very first UBE submitted to the server will run ok, but all subsequent jobs
will fail because they will all try to assume the number '0' and therefore fail to insert to table F986110. If you

5 of 12 8/7/2022, 9:08 PM
Document 1502927.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

encounter this issue, you should capture the UBE kernel debug logs and look for any issues around queries against
F986111. One known scenario that will lead to this error is on installs with multiple AS/400 servers and when
communication between the servers is required in order to access F986111. Refer to Doc ID 642116.1 for more details
on issue and resolution.

Sometimes restoring either table F986111 or F986110 from backup will also cause this issue as the next job number
will likely be out of sync with records already in F986110. To address this situation, use Work with Submitted Jobs
(WSJ) application to find the record with the highest job number in F986110. Then update the record in server map
table F986111 with that job number plus '1'. Refer to Doc ID 658577.1 E1: UBE: How to Reset Job Numbers of UBE
Reports Submitted to the Server - for information on how to update the job number in F986111.

Issue 4: Unable to Save Temporary Files on the Enterprise Server

EnterpriseOne will try to save temporary files as part of submitting and running UBEs on the server. The location where
these files are saved is controlled by the parameter netTemporaryDir in the server JDE.INI or if this parameter is not
defined, by environment variables defined at the server operating system leve.

If the jdenet, UBE kernel or RUNBATCH are unable to create and access these temporary files, they will fail. If you
encounter a sudden systematic failure to submit or run UBEs on your enterprise server verify the temporary location
and make sure there is enough disk space to create new files, that the directory has not reached its maximum number
of files, or that it points to a valid location on the server.

The parameter in JDE.INI is:

[JDENET]
netTemporaryDir=path

where path points to a valid folder on your enterprise server. Note the OS User ID which starts EnterpriseOne services
need to have full access to this directory. On AS/400 servers this points to a directory in IFS.

Issue 5: Security Server is Disabled in Local JDE.INI

You will not be able to submit UBEs from a Windows client and if a security server is not defined in the local JDE.INI.
The solution is to add a security server to your local JDE.INI:

[SECURITY]
SecurityServer=SERVERNAME

A clue of this issue is if you see the following message in the UBE kernel log:

Failed to get extended token: eSecInvalidToken: The security token is invalid

Get extended token failed.

Issue 6: Spec Errors When Submitting from EnterpriseOne Web Client

UBE Submission spec issues on web clients are caused by problems with serialized report specs. Up until EnterpriseOne
application release 8.12 if a report version was created on a Windows client, it was necessary to generate any new
report version before you could submit it from a web client. If the version was not generated, then users would get a
pop-up message saying "COULD NOT LOAD REPORT / Please user the latest Java generator to regenerate the
report.REPORTID":

6 of 12 8/7/2022, 9:08 PM
Document 1502927.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

With application release 8.12 and later object specs are generated on demand. This feature can however be disabled
through the jdbj.ini settings

autoDetectPackage=false
specGenerateOnDemand=false

If for some reason on-demand generation is disabled and a user tries to submit a new UBE version the job will fail to
submit and the following errors will be found in the jasroot log of your web server:

[METADATA] Cause exception com.jdedwards.base.install.JDEPackageInfoException: PackgeInfoAccess loading

fails.
[METADATA] JDESpec error code = SPEC_DATABASE_SERVICE_LOAD_FAILED
com.peoplesoft.pt.e1.base.metadata.dataAccess.JDESpecException: Database service class class
com.peoplesoft.pt.e1.metadata.dataAccess.SpecDBRepositoryImpl could not be loaded for [User : JDE
Environment : JDV812 Role : *ALL].
[METADATA] Cause exception java.lang.reflect.InvocationTargetException
[METADATA] JDESpec error code = SPEC_REP_LOAD_FAILED
com.peoplesoft.pt.e1.base.metadata.dataAccess.JDESpecException: Spec repository implementation could not
be loaded.
[JAS] SubmitUBE.launchUBE() : Exception thrown during UBE submission! | Report Name : R0006P, Version
Name : XJDE0001, Server Name : null, User Name : JDE java.lang.NullPointerException

To address this issue you can either manually generate the report version, or enable auto-generation by setting the
following parameters in the web server jdbj.ini:

[JDBj-RUNTIME PROPERTIES]
autoDetectPackage=true
specGenerateOnDemand=true

Refer to Doc ID 787291.1 E1: GEN: Frequently Asked Questions on Spec Generation on Demand and Package Discovery
for more information on these parameters.

Another possibility is that EnterpriseOne is configured to process UBE reports and business functions on different
servers. The Business Function B98305V must follow the default UBE mapping. This Business Function actually prompts
the installation of specs to the server it is running on. If this Business Function is not running on the same server where
the UBE is being processed, the specs will never get installed. If this is the case, map this business function to the
same server as the DEFAULT UBE OCM definition.

Issue 7: Not Enough Disk Space on Web Server

In the process of submitting a version from a web client, the version specs, processing options, printer information will
be stored in a temporary file on the web application server (the location is defined by parameter tempFileDir in jas.ini).
If there is not enough space to store this file, the job will fail to submit. The following errors accompany this issue:

[SEVERE] JDE - [METADATA] Retrieved JDENET.tempFileDir, using C:\JDE_HOME\targets\JASSERVER_PORT81\temp

[SEVERE] JDE - [METADATA] Cause exception java.io.IOException: There is not enough space on the disk.
java.io.IOException: There is not enough space on the disk.

[SEVERE] - [NET] JDENET can not write to temporary file /home/oracle/jde_home/SCFHA/targets

/JASSERVER_PORT81/temp/NET_TEMP135
[SEVERE] - [METADATA] Cause exception java.io.IOException: No space left on device

To address this problem make sure there is enough disk space on your web server. The directory also contains UBE

7 of 12 8/7/2022, 9:08 PM
Document 1502927.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

PDFs (copied when viewing output in WSJ) which are automatically cleaned up. If the PDFs remain, they can be
deleted.

Issue 8: "Not Authorized to Run Report" Errors in Server Process Log

Review application security records that might be preventing the user ID, role or *PUBLIC from running the UBE. Once
security is modified the user should no longer see any error when submitting the UBE using a server process.

Example of full error message found in RUNUBE command log:

user <USERID> is not authorized to run report <REPORTID>

Issue 9: Error "There was a problem with the server while running the business function IsXMLP2SPPresent"

This error is usually seen after upgrading the tools release to 8.97 or 8.98 on EnterpriseOne 8.11SP1 and 8.12. The
issue is related to an enhancement to embedded BI Publisher which require business function N95620A to be compiled
on the new tools release and to operate together with later release of object P98305W.

The problem can be addressed by applying the latest ESUs containing P98305W for your application release, building a
full package and re-serializing all object specs.

Refer to Doc ID 837395.1 for more details about issues, symptoms and resolution.

Issue 10: Error "There was a problem with the server while running the business function
IsPrinterMappingPresent"

Logs shows this error message: Business function load failed - COBJLIB - _IsPrinterMappingPresent@12

This error is usually seen if the source and/or header files of the BSFN N95620A are missing.

The problem can be addressed by applying the latest ESUs containing BSFN N95620A for your application release,
building a full package and re-serializing all object specs. Otherwise try to promote the specs for this BSFN from
working environments and building an update package.

Issue 11: Error "Security token not valid" when Submitting UBEs from a Windows/Fat Client

This error indicates the security token for the Windows client is expired.

A security token is issued to the EnterpriseOne client at the time user logs in. This security token has an expiration
date/time. When submitting UBEs to sever, this security token is used to validate the user session and authorize the
user to run the UBE on the server. If enough time has passed however, the token will have expired, resulting on this
error message.

There is an internal time setting - "Regular Token Lifetime" that is timing out. The default setting for this timeout is 12
hours. To resolve the issue, the user will need to logout and back in and only then submit the UBE.

To change the timeout setting value, please see "Setting Up a Token Lifetime Configuration Record" in the
EnterpriseOne Security Administration guide available from the Oracle Technology Network documentation sit

Issue 12: All UBEs fail with error, *ERRROR* LaunchUBE: LaunchUBE failed- JDEKDCL.h/UBEERRORCODE
error 22 user

8 of 12 8/7/2022, 9:08 PM
Document 1502927.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

jas log:

14 Aug 2020 00:44:58,179 [SEVERE] JDE - [KERNEL] *ERRROR* LaunchUBE: LaunchUBE failed-
JDEKDCL.h/UBEERRORCODE error 22 user:JDE Env:JPD910
14 Aug 2020 00:44:58,179 [SEVERE] JDE - [JAS] SubmitUBE.launchUBE() : Exception thrown during
UBE submission! | Report Name : R0006P, Version Name : XJDE0004, Server Name : <Server Name>,
User Name : JDE com.jdedwards.system.kernel.LaunchUBEException: LaunchUBE failed-
JDEKDCL.h/UBEERRORCODE error 22

UBE Kernel log

8814/1 MAIN_THREAD Fri Aug 14 12:07:51.566905 dbcolind.c141

OCI0000017 - Unable to execute statement for describe - SELECT * FROM DV910.F98740DV910FW WHERE
( ELPRDTYP = :KEY1 AND ELOBNM = :KEY2 ) ORDER BY ELPRDTYP ASC,ELOBNM ASC,ELVERS ASC,ELFMNM
ASC,ELCTRLID ASC,ELWEVENT ASC,ELERID3 ASC

8814/1 MAIN_THREAD Fri Aug 14 12:07:51.567126 dbcolind.c148

OCI0000018 - Error - ORA-00942: table or view does not exist

This issue could be due to incorrect setting in jde.ini,

• Make sure that the security server is enabled in jde.ini and pointing to the right server
• Make sure that the server jde.ini is pointing to the right pathcode.

Unix and Linux Server Platforms

Issue 1: Server Name Mismatch in F986130

This is a variation of the "Invalid Job Queue" problem described above. When UBE kernel looks for the job queue in
F986130 it tries to find the record based on three keys: job queue name, server name and jdenet port number.
Because Unix and Linux operating systems are case sensitive, if a server name is defined in upper case when installing
EnterpriseOne, queues in F986130 will also be in upper case. However a typical Unix or Linux server name will be in
lower case. This will lead to a mismatch and cause the query on F986130 to not return any result, making the UBE
kernel to interpret it as if the job queue was not correctly defined EnterpriseOne.

Just as before, this type of issue will result in the following message being written to the UBE kernel log:

QUEUE04900030-Failed to FetchKeyed for entserver_6015_QBATCH in F986130.

This issue can be addressed by changing the server name to match that which is used in EnterpriseOne, or by manually
updating any table and file that has the server name in uppercase to lowercase. The former process is usually simpler.
In Linux for example the server name is usually defined in file '/etc/sysconfig/network'. The later process is not
supported by GCS, but some clients reported successful results following these steps:

• Change client machines INI files to reflect the new enterprise server name.
• Change JDE.INI on Enterprise server, including sections [INSTALL] and [BSFN BUILDER].
• Update tables F986130, F986110 (Job Table), F00053, F000531, and F000532 (B73.2 and lower) to reflect the
server name.
• You might need to update F9650, F9651 and F96511 tables as well.
• You should also change the data source names.
• Update the host files.
• Be sure you can ping the Enterprise server by name.
• Update services file on the host machine.

Issue 2: All UBEs fail with error, *ERRROR* LaunchUBE: LaunchUBE failed[4] - Invalid Queuename - not defined

9 of 12 8/7/2022, 9:08 PM
Document 1502927.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

for server

Linux box was configured with the 'short' hostname as the FQDN name, whereas E1 was set up, P986130, to just use
"host" as the name (not FQDN). But the customer had 'host.example.com' in F986130.

User Specific JAS.log

06 Apr 2021 12:26:32,973[SEVERE][USER_ID][KERNEL]*ERRROR* LaunchUBE: LaunchUBE failed[4] - Invalid

Queuename - not defined for server. See version specs for queue override and queue definitions in
P986130 to correct.; job Number = 44 user:USER_ID Env:JDV920
06 Apr 2021 12:26:32,975[SEVERE][USER_ID][JAS]SubmitUBE.launchUBE() : Exception thrown during UBE
submission! | Report Name : R0006P, Version Name : XJDE0001, Server Name : null, User Name : USER_ID
com.jdedwards.system.kernel.LaunchUBEException: LaunchUBE failed[4] - Invalid Queuename - not defined
for server. See version specs for queue override and queue definitions in P986130 to correct.; job
Number = 44

UBE Kernel Log

11108 Tue Apr 6 12:29:44.400112 lanchube.c2991 LANCHUBE-0101-Failed to get queue type for
snrjdeent01d.snackinternal.com_6017_QBATCH
11108 Tue Apr 6 12:29:44.400707 queueapi.c221 QUEUE05000030-Failed to FetchKeyed for
snrjdeent01d.snackinternal.com_6017_QBATCH_ from F986130
11108 Tue Apr 6 12:29:44.400753 jdeknube.c1206 KNT0010080 - Queue
snrjdeent01d.snackinternal.com_6017_QBATCH_ is not defined in F986130

The PrimaryNode setting under the [CLUSTER] section tells the jdeGetHostName() API to use that name, instead of
what the OS-level 'gethostname()' API would return -- which, in this case, the gethostname() would return
host.example.com. There is no clustering, and this setting just acts as an override, allowing them to set the shortname
for E1, despite the OS being configured with the FQDN and the 'short' hostname.

Solution

1. Verify (in this case) FQDN lower case is set on Linux server (If FQDN is in lower case, verify value in Cluster is in
lower case)
2. Verified CLUSTER in JDE.INI setting has server name set to SHORT_HOST_NAME
3. Re-started ENT server
4. Tested by running R0006P
5. Version should run normally
6. Review WSJ and hostname, verify it was the same as the CLUSTER setting

JDE.INI Example
[CLUSTER]
PrimaryNode=shorthostname

AS/400 Server Platform

Issue 1: UBEs fail to Submit when SQL Server Mode is Enabled

Beginning with OneWorld Service Pack 23 and EnterpriseOne Tools Release 8.96 Bug 12520704, CLI SQL Server Mode
is enabled by default to support third party application Vertex 3.2.3 and later. This change caused some issues that
manifested themselves as issues submitting and running UBEs on AS/400 servers.

The majority of these issues are addressed either applying required IBM PTFs to server, or by disabling SQL Server
Mode when not using Vertex 3.2.3 or later, not using Vertex, or if using an application release prior to 8.12.

For detailed information about the different scenarios and issues related to SQL Server Mode review the following
documents:

Doc ID 661312.1 E1: UBE: Unable To Submit UBEs to AS/400 Server After Installing Service Pack 23 or Later
Doc ID 663627.1 E1: UBE: UBEs Fail to Run on EnterpriseOne 8.12 on AS/400 Server Due to Database Errors in
METADATA Kernel

10 of 12 8/7/2022, 9:08 PM
Document 1502927.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

Doc ID 664626.1 E1: UBE: UBEs Fail to Run on EnterpriseOne 8.12 on AS/400 Server Due to Database Errors in UBE
Kernel
Doc ID 662878.1 E1: UBE: Memory Pool, Priority and QAQQINI Settings Are Not Being Inherited from Batch Job

Issue 2: AS/400 User Permissions Issues

It is important that the user under which EnterpriseOne services run on the server have the adequate privileges to
perform database operations and access EnterpriseOne libraries and directories in IFS.

One clue of permission issues is if you find the following type of error messages in the UBE kernel log:

ODB0000164 - STMT:00 [42000][-551] [IBM][iSeries Access ODBC Driver][DB2 UDB]SQL0551 - Not authorized to
object F986110 in SVM900 type *FILE.
ODB0000164 - STMT:00 [42000][-551] [IBM][iSeries Access ODBC Driver][DB2 UDB]SQL0551 - Not authorized to
object F986111 in SVM900 type *FILE

To address this type of issue make sure user ONEWORLD, PSFT or JDE have *ALL object authority, for example:

OPR MGT EXIST ALTER REF

*PUBLIC *ALL X X X

JDE USER DEF X X X X X

Another scenario is when limited privileges prevents the use of the IBM i5/OS SwapUserProfile handle API to change
the job to run under the system user profile (proxy user) associated with the EnterpriseOne user account. In this case,
the UBE kernel will crash.
Refer to Doc ID 835577.1 E1: UBE: System Users Other Than JDE Cannot Run UBEs on IBM iSeries.

Issue 3: Custom Job Queue outside System Library on AS400

UBE fails to submit on the newly created custom Job queue on iseries in custom library.

Error in the JAS log:

[SEVERE] JDE [KERNEL] *ERRROR* LaunchUBE: LaunchUBE failed- JDEKDCL.h/UBEERRORCODE error 4; job Number =
1206500 user:JDE Env:JPY910
[SEVERE] JDE [JAS] SubmitUBE.launchUBE() : Exception thrown during UBE submission! | Report Name :
R98OWSECA, Version Name : XJDE0001, Server Name : null, User Name : JDE
com.jdedwards.system.kernel.LaunchUBEException: LaunchUBE failed- JDEKDCL.h/UBEERRORCODE error 4; job
Number = 1206500
[WARN ] JDE [RUNTIME] JASServiceException is occured in the SysFunctionStaement.launchBatchApp():Report
R98OWSECA_XJDE0001 has not been successfully submitted. The following JASServiceException has been
caught:Errors on JAS: Please check JAS.log for details.

Error in UBE Kernel Debug log

queueapi.c239 - QUEUE05000040-Native queue <queuename> does not exist

Cause: The new job queue is created in Custom Library, which is not added to the Library List.

Solution: In case of custom library you need to ensure that the library containing the jobq is in the library list in which
the job is being submitted. The custom library hosting the custom jobQ should be reachable via *LIBL

To Resolve:
1) Add the custom library to the job description NETJOBD in library E910SYS. This is the job description that the E1
services uses when launching the E1 kernels
2) Stop and Start the E1 services on the as400 via server manager. Alternatively, logon to the AS400 machine as

11 of 12 8/7/2022, 9:08 PM
Document 1502927.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

ONEWORLD user profiile and issue the ENDNET, CLRIPC and STRNET commands.
3) Retest by launching the batch job in custom job queue

Review Doc ID 2011153.1 E1: UBE: How to create custom Job Queue outside of System library list in IBM i (AS/400)

Issue 4: Other AS/400 Issues

Review the following document for other AS/400 related issues:

Doc ID 654980.1 Common UBE Issues On AS/400 Server

Other Less Common Issues

Doc ID 628191.1 E1: UBE: Unable to Submit Some UBEs from Web Client on OneWorld Xe, ERP8 or EnterpriseOne
Tools 8.95 and Older
Doc ID 638685.1 E1: UBE: Error "Failed to Validate Auth Token" When Submitting UBE's to Enterprise Server
Doc ID 646270.1 E1: UBE: Unable to Submit UBEs to AS/400 Enterprise Server Because Limited Access to QTEMP
Library
Doc ID 659422.1 E1: UBE: Submit UBE from Web Client Skips Printer Selection After Applying Baseline Tools ESU
JK14530 to EnterpriseOne 8.12
Doc ID 643398.1 E1: UBE: Unable to Submit UBEs from Custom Web Environment If Override Job Queue is Selected
Doc ID 1065903.1 E1: UBE: Intermittent Communication Problem on UBEs Submitting to Batch Server
Doc ID 1294416.1 E1: UBE: Unable to Submit UBEs to AS/400 Server Due to Database Error SQL7008 on Table
F986111
Doc ID 1374813.1 E1: UBE: Error "Local Submission Is Not Supported From Skinny Batch Versions/Menus" when
Submitting UBE from Standalone Client
Doc ID 1338447.1 E1: UBE: Unable to Submit UBEs Intermittently to AS/400 Server Because of Failure to Connect to
Server Map Data Source
Doc ID 1189698.1 E1: UBE: Unable To Submit UBEs to Server Receiving Error "IPC3400007 - startProcess
CreateProcess for runbatch.exe failed, err=2"

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start
a discussion in the Design Tools & Output Technologies - JDE1 Community
To look at upcoming or archived Advisor Webcasts review Doc ID 1450327.1 Advisor Webcast JD Edwards
EnterpriseOne Schedule and Archived Recordings. If your topic is not currently scheduled please suggest it.

REFERENCES

NOTE:1498831.1 - E1: UBE: Understanding UBE Submission Process

NOTE:1502974.1 - E1: UBE: Understanding UBE Execution Process
NOTE:1502985.1 - E1: UBE: Common UBE Execution and Runtime Issues
Didn't find what you are looking for?

12 of 12 8/7/2022, 9:08 PM