Loadlib problem

divate.dilip · New User Joined: 11 May 2009 Posts: 15 Location: Mumbai

in the production the issue came that the output flat file contain field is wrong.
so to test, I copied the program to test and compiled its running fine.Output is coming properly as expected.
( program contains on one input vsam file and one output file) nothing else.

I checked everything there is no issue in the program, only thing is loadlib when I use the production loadlib, output is wrong and when we use the test loadlib output is fine.

There seems to be problem with the compatibilty of Compiler. how we will come to know that the loadlib is having problem.

Is there any way to see the compiler has changed and the program has compiled using old compiled option.

Robert Sample · Posted: Thu Mar 25, 2010 5:45 pm

You need to contact your site support group and work with them. It is possible that the options used for compiling into production are different than what you used for testing. Some sites recompile for every move into production, some sites move the QA load library member into production. Since this is site specific, and we don't know your site, only your site support group can provide you with assistance.

divate.dilip · New User Joined: 11 May 2009 Posts: 15 Location: Mumbai

Actually the program has not changed from the last 7 years, and the problem has started since 6-7 Odd Months.

IS there any way looking at the Loadlib or anything we come to know what compiling option or which compiler is used.

Or any other way to know any other kind will be very helpful.

dick scherrer · Posted: Fri Mar 26, 2010 9:51 am

Hello,

divate.dilip · New User Joined: 11 May 2009 Posts: 15 Location: Mumbai

I ran the AMBLIST utility, using

//SYSLIB DD DSN=TEST.BATCH.LOADLIB,DISP=SHR
//SYSIN DD *
LISTLOAD DDN=SYSLIB,MEMBER=VCP003,
TITLE=('LISTING FOR NUCLEUS VCP003',25)

//SYSLIB DD DSN=PROD.BATCH.LOADLIB,DISP=SHR
//SYSIN DD *
LISTLOAD DDN=SYSLIB,MEMBER=VCP003,
TITLE=('LISTING FOR NUCLEUS VCP003',25)

Now in the output I got different control section CEEARLU,CEEBETBL likewise which shows the transalator, the mod and date..which say for the production is 03/28/2000 and for the test loadlib as 03/28/2007.

Is this related to the compiler version. I have attached the screen shot of it.

divate.dilip · New User Joined: 11 May 2009 Posts: 15 Location: Mumbai

sorry not able to add attachment. this is how it look like.

-PROD LOADLIB

----------------------------------------------
CONTROL SECTION: CEEARLU
USABILITY: UNSPECIFIED OVERLAY SEGMENT:
===== IDRL =====
TRANSLATOR VER MOD DATE
569623400 01 03 03/28/2000
PL/X-390 02 01 03/28/2000

-----------------------------------------------

TEST LOADLIB
-----------------------------------------------
CONTROL SECTION: CEEARLU
USABILITY: UNSPECIFIED OVERLAY SEGMENT:
===== IDRL =====
TRANSLATOR VER MOD DATE
569623400 01 05 03/28/2007
PL/X-390 02 03 03/28/2007

To cross check I have copied the production programs Load lib in test loadlib and ran again the same job. it displays in test loadlib the same 03/28/2000.

Could anyone please explain this? it will be very helpful.....

Anuj Dhawan · Posted: Fri Mar 26, 2010 2:33 pm

May be not the answer you're looking for, however in this,

Marso · Posted: Fri Mar 26, 2010 3:39 pm

Have you checked too if input is wrong ?

I mean, have you run your test with production data ?
or run the production program with test data ?

dbzTHEdinosauer · Posted: Sat Mar 27, 2010 12:32 am

CEEARLU,CEEBETBL are language environment (LE) modules.

may want to look them up in the Language Environment Manuals

divate.dilip · New User Joined: 11 May 2009 Posts: 15 Location: Mumbai

I am using the same input file and same program as present in production,

prepared the test job, and ran the job. The output file has having a field = zeros instead of 100$.

Now I overriden the steplib to pick my loadlib( the pgm is compiled without any changes) .. the output field = 100$.

Now I copied the production loadlib to test loadlib( only the particular pgm) and the output field = zeros.

There seems to be a problem with the production loadlib of pgm.

The program was last modified in production in 2004, there are no changes made till date and suddenly from last 7 odd months some output fields are coming zeros.

Ranjithkumar · New User Joined: 10 Sep 2008 Posts: 93 Location: India

@divate.dilip,

If you have FILEAID available in your shop, can you Map CSECTs in address order ( Option 3.1 A in FILEAID) and show us the results, for both PROD and TEST loads? That might help in debugging.