z/OS V1 R11 BINDER 04:18:20 THURSDAY SEPTEMBER 2, 2010
BATCH EMULATOR JOB(TESTRUN1) STEP(STEP020 ) PGM= IEWL
IEW2456E 9207 SYMBOL IGZCBSO UNRESOLVED. MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.
IEW2456E 9207 SYMBOL CEESTART UNRESOLVED. MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.
IEW2456E 9207 SYMBOL CEEBETBL UNRESOLVED. MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.
IEW2456E 9207 SYMBOL CEESG005 UNRESOLVED. MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.
Seems that the members are not present in none of the SYSLIB datasets contatinated. There is one more dataset in my shop SYS1.SCEELKED which I have concatinated and I get RACF dataset error as I do not have access to the SYS1.SCEELKED. If I am given access and I am assuming that the necessary members are found in the datset,then my link edit step would work is what I am assuming. Is there any way without requesting access to the dataset the link edit step can run fine. I am not sure of this , can anybody help me. Is there any other dataset I should look for the members which were not able to be resolved.
First thing which come to mind is - why don't you contact your site-support group. Such JCLs (processes) are specific to shops and must not be picked up from some on-line-reference.
Second, is this first time you compiled some program with this?
From manuals:
Quote:
IEW2456E SYMBOL symbol UNRESOLVED. MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.
Explanation: The 'symbol' displayed is not a member name in SYSLIB or in the designated call library, or errors were encountered when attempting to include the module. The symbol remains unresolved.
System Action: Processing continues.
User Response: Correct the reference or make the missing entry available to the Binder by (1) adding the member to SYSLIB, (2) adding an alias of that name to an existing member, (3) INCLUDEing a module which contains the missing entry point, (4) providing a LIBRARY control statement to direct the Binder to a different library during autocall processing, or (5) correct the source of the INCLUDE error.
Correct the symbol reference in the source program or make the missing entry available to the Binder. Making the entry available can include any of the following:
1. Adding the name as an alias or member to in SYSLIB.
2. Providing an AUTOCALL control statement pointing to a library that can resolve the name.
3. INCLUDEing a module that contains the missing entry point
4. Providing a LIBRARY control statement to direct the Binder to an additional library during final autocall processing.
5. Correcting an existing INCLUDE, AUTOCALL, or LIBRARY control statement.
6. If you are driving the binder from some other program, such as SMP/E or c89, you might need to correct or extend the library specifications you are providing to that program. If such a program generates AUTOCALL statements, they are applied before final autocall processing, and are not used recursively unless the library names are repeated.
_________________ Regards,
Anuj
Last edited by Anuj Dhawan on Fri Sep 03, 2010 4:41 am; edited 1 time in total
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
