Fixes are available
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
The Cobol Container support only works in a 31 bit server. 31 bit servers are not supported in version 9 so there is no COBOL container support in WebSphere Application Server for z/OS Version 9.0. When you try to submit a job to drive COBOL in a 64 bit server a java.lang.UnsatisfiedLinkError: LECENV (Not found in java.library.path) will occur. java.lang.RuntimeException: java.lang.ExceptionInInitializerError at com.ibm.ws.batch.ilc.sample.ILCDataTypes.createJobStep(ILCDataTy pes.java:135) at com.ibm.ws.gridcontainer.batch.impl.StepManagerImpl.setupStep(St epManagerImpl.java:307) at com.ibm.ws.gridcontainer.security.actions.SetupStepBatchUserPriv ilegedAction.executeAction(SetupStepBatchUserPrivilegedAction.ja va:45) at com.ibm.ws.gridcontainer.security.AbstractUserPrivilegedAction.r unWithoutSecurity(AbstractUserPrivilegedAction.java:66) at com.ibm.ws.gridcontainer.services.impl.WASRunUnderCredentialServ iceImpl.runUnderUserCredential(WASRunUnderCredentialServiceImpl. java:134) at com.ibm.ws.gridcontainer.services.impl.WASRunUnderCredentialServ iceImpl.runActionUnderUserCredential(WASRunUnderCredentialServic eImpl.java:367) at com.ibm.ws.gridcontainer.batch.impl.JobManagerImpl._setupStep(Jo bManagerImpl.java:878) at com.ibm.ws.gridcontainer.batch.impl.JobManagerImpl._sequentialSt epScheduling(JobManagerImpl.java:775) at com.ibm.ws.gridcontainer.batch.impl.JobManagerImpl.executeJob(Jo bManagerImpl.java:199) at com.ibm.ws.batch.BatchJobControllerWork._runJob(BatchJobControll erWork.java:329) at com.ibm.ws.batch.BatchJobControllerWork.run(BatchJobControllerWo rk.java:231) at com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java :281) at java.security.AccessController.doPrivileged(AccessController.jav a:594) at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:747) at com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithE xecutionContextImpl.java:222) at com.ibm.ws.asynchbeans.ABWorkItemImpl.run(ABWorkItemImpl.java:20 6) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892) Caused by: java.lang.ExceptionInInitializerError at java.lang.J9VMInternals.ensureError(J9VMInternals.java:141) at java.lang.J9VMInternals.recordInitializationFailure(J9VMInternal s.java:130) at com.ibm.ws.batch.ilc.impl.ILContainerImpl.<init>(ILContainerImpl .java:105) at com.ibm.websphere.batch.ilc.ILContainerFactory.create(ILContaine rFactory.java:81) at com.ibm.ws.batch.ilc.sample.ILCDataTypes.createJobStep(ILCDataTy pes.java:97) ... 16 more Caused by: java.lang.RuntimeException: java.lang.UnsatisfiedLinkError: LECENV (Not found in java.library.path) at com.ibm.ws.batch.ilc.impl.LEChildEnvironment.<clinit>(LEChildEnv ironment.java:65) ... 19 more Caused by: java.lang.UnsatisfiedLinkError: LECENV (Not found in java.library.path) at java.lang.ClassLoader.loadLibraryWithPath(ClassLoader.java:1344) at java.lang.ClassLoader.loadLibraryWithClassLoader(ClassLoader.jav a:1314) at java.lang.System.loadLibrary(System.java:552) at com.ibm.ws.batch.ilc.impl.LEChildEnvironment.<clinit>(LEChildEnv ironment.java:58) ... 19 more
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V9.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: COBOL container support in WebSphere * * Application Server for z/OS version * * 9.0 does not work. * **************************************************************** * RECOMMENDATION: * **************************************************************** In releases before version 9 the Cobol Container support only worked in a 31 bit server. 31 bit servers are not supported in version 9 so there is no COBOL container support in WebSphere Application Server for z/OS Version 9.0. When a job is submitted to drive COBOL in a 64 bit server a java.lang.UnsatisfiedLinkError: LECENV (Not found in java.library.path) occurs.
Problem conclusion
Updated the code so the cobol container support will run in a 64 server. APAR PI69833 is currently targeted for inclusion in Fix Pack 9.0.0.2 of WebSphere Application Server for z/OS. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI69833
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-09-29
Closed date
2016-10-27
Last modified date
2016-10-27
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R900 PSY
UP
Document Information
Modified date:
03 May 2022