Up to Discussions in VAGen Migration to EGL Hub
5 Replies Last post: Sep 18, 2008 6:49 AM by kezakis  
Click to view kezakis's profile  
kezakis
14 posts since
Jul 19, 2008

Sep 12, 2008 11:49 AM

Generation probelm after migration


Dear Forum,

I found a strange generation problem after Migration from VAGen.
After successfuly migration and Buildserver configuration I found the strange situatioon that RBD
insists that the gneration failed, althow it succeded in reality.

Has anybody expirianced similar Problems?

I attach the Generation result of one of my generation attamps as an example (the associated Generation is marked as failure in RBD):

CCUI-015
The build job has been queued by the server.Position is 1.
08/09/11 12:19:08

CCUI-014
Job 'CCUMVS0.JOB06260' has been started by the server.
08/09/11 12:19:12 *** Success ***08/09/11 12:19:12 CCUI-003
Program Name : 'IEFBR14 '.

PARM : ''.

CCUI-004The MVS step 'UPLOAD' return code is '000000'.CCUI-003Program Name : 'DSNHPC '. PARM : 'HOST(COB2),SOURCE,APOSTSQL,QUOTE,XREF'.

CCUI-004The MVS step 'P' return code is '000000'.CCUI-003
Program Name : 'DFHECP1$'. PARM : 'COBOL2,QUOTE,NOSEQ,SP,DBCS'. CCUI-004The MVS step 'T' return code is '000000'.
CCUI-003Program Name : 'IGYCRCTL'.

PARM : 'NOSEQ,QUOTE,LIB,RENT,NODYNAM,OPT,DBCS,ARITH(EXTEND),TRUNC(BIN),NUMPROC(NOPFD),NOLIST,DATA(24)'.

CCUI-004
The MVS step 'C' return code is '000004'.
CCUI-003
Program Name : 'IEWL '.
PARM : 'RENT,REUS,LIST,XREF,MAP,AMODE(31),RMODE(ANY)'.

CCUI-004
The MVS step 'L' return code is '000004'.

Bind:

08/09/11 12:19:19 *** Success ***
08/09/11 12:19:19

CCUI-003Program Name : 'IEFBR14 '.
PARM : ''.

CCUI-004
The MVS step 'UPLOAD' return code is '000000'.CCUI-003
Program Name : 'IKJEFT01'. PARM : ''. CCUI-004
The MVS step 'B' return code is '000000'.
CCUW-002
Warning: File DD:SYSPRINT is empty.
CCUW-002
Warning: File DD:SYSOUT is empty.
CCUW-002
Warning: File DD:REPORT is empty.

Click to view banerjee's profile  
banerjee
45 posts since
Jun 30, 2008
1. Sep 12, 2008 4:07 PM Up Image in response to: kezakis
Re: Generation probelm after migration

Hi,

Is this happening with other generations as well, or only with this one?

Can you check if the bind step was actually successful in the host. There should be print listings down loaded if you set CCUEXTB=CCUOUT in the build descriptor as a symparm..


Click to view kezakis's profile  
kezakis
14 posts since
Jul 19, 2008
2. Sep 15, 2008 3:31 AM Up Image in response to: banerjee
Re: Generation probelm after migration

Hello Banerjee,

thanks for your reply, The problem happens with almost all Generations. The bind step seems to work without error.
We get the following Report:

READY
TSOLIB ACTIVATE DA('DSN710.SDSNLOAD')
READY
ALLOC FI(DBRMLIB) SHR DA('KA00180.ZOSCICS.DBRMLIB' 'ELA.V6R0M1.SELADBRM')
READY
DSN SYSTEM(DSN)
DSN
BIND PACKAGE (CTADV) MEMBER(AHE10) LIBRARY('KA00180.ZOSCICS.DBRMLIB') EXPLAIN(YES) RELEASE(COMMIT) ENABLE
(CICS) CICS(CICST) ACT(REP) VALIDATE(BIND) ISOLATION(CS) OWNER(#A00180)
DSNT254I - DSNTBCM2 BIND OPTIONS FOR
PACKAGE = ATJKUN00.CTADV.AHE10.()
ACTION REPLACE
OWNER #A00180
QUALIFIER #A00180
VALIDATE BIND
EXPLAIN YES
ISOLATION CS
RELEASE COMMIT
COPY
DSNT255I - DSNTBCM2 BIND OPTIONS FOR
PACKAGE = ATJKUN00.CTADV.AHE10.()
SQLERROR NOPACKAGE
CURRENTDATA YES
DEGREE 1
DYNAMICRULES
DEFER
NOREOPT VARS
KEEPDYNAMIC NO
IMMEDWRITE NO
DBPROTOCOL DRDA
OPTHINT
ENCODING EBCDIC(00273)
PATH
DSNT232I - SUCCESSFUL BIND FOR
PACKAGE = ATJKUN00.CTADV.AHE10.()
DSN
DSN
END

The only Generation that return a success message are 3270 Map Generation.

Is there the posibility that we run into an timeout Problem?

Thanks in advance

Kezakis


Click to view banerjee's profile  
banerjee
45 posts since
Jun 30, 2008
3. Sep 15, 2008 10:55 AM Up Image in response to: kezakis
Re: Generation probelm after migration

Hi,

Can you please send me the generated program parts and the results. I will take a look a look and see if i notice something. The behavior you are reporting is strange indeed.

It is probably best to generate into a new folder, and after completion, zip up the folder and send to me.

My email id is dbanerje@us.ibm.com

Thanks


Click to view banerjee's profile  
banerjee
45 posts since
Jun 30, 2008
4. Sep 18, 2008 6:28 AM Up Image in response to: banerjee
Re: Generation probelm after migration

Stephan,

As we found out from our email exchanges, the problem was due to setting CCUEXTx=CCUSTD in the build scripts.

When CCUEXTx=CCUOUT, the listing files are downloaded to the pc.

When CCUEXTx=CCUSTD, the listing files are downloaded to the pc AND also put on the console. There is no real advantage of using CCUSTD as the listing files are long. Also in that case the build results file contains the listing and the XML parser that processes the results file goes through the listings contents. What happened for you is that in some listings there were characters which the XML parser could not process, and reported the build as failure.

The problem doe not occur with CCUEXTx=CCUOUT.


Click to view kezakis's profile  
kezakis
14 posts since
Jul 19, 2008
5. Sep 18, 2008 7:41 AM Up Image in response to: banerjee
Re: Generation probelm after migration
Hi Dev,

I already confirmed that setting CCUEXT to CCUOUT solves the reported problem.


Thanks a lot.

Actions

More Like This

Bottom Banner