MVSFORUMS.com

[Jai]

Hi Friends,

One Program which is working fine in test region is failing in Prod Region with S0C4 internally S0C7 (U0086 )

in which we are moving
S9(3)V9(2) to S9(1)V9(2)
and S9(14) to S9(13)
VARIABLES and all are DClGEN Variables.
basically we need to get the data from one table and update into other but variables are declared differently in both the tables.

Now Facing this Problem and have to solve it as soon as possible..
Please mail me as soon as possible with all possible soluntions

Thanks in advance.
_________________
Have a Great Day.
Thanks & Regards,
Jai

[kolusu]

Jai,

I hope you have read the forum guidelines. The second rule is Avoid putting "urgent" or "urgently" in your topics. . so in future please avoid posting with urgent needs.

Just at the top of my head are any of the columns can contain null? if the column contains null then the host variable will have garbage which is an invalid packed decimal.

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

[Jai]

Thanks Kolusu,

I will surely take care of not putting Urgent in the subject further.

It is really urgent as I need to solve it as soon as possible.
All the Columns are not nullable here.
So null case should not come as per that.

Please try to find me other possible causes.

Thanks in advance.
_________________
Have a Great Day.
Thanks & Regards,
Jai

[kolusu]

Jai,

Something really weird , did you have both S0C4 & S0C7 abend for the program ?. It would be helpful if you post the sysout messages.

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

[vini]

Jai,

If you have Determined that SOC7 is the cause of the Abend ....

SOC7 usually is a result of the source Data Item not being INITIALISED .... even if it does not hold NULL values i.e. Something is causing no valid data to be moved to it and you would know best by either Expediting or using DISPLAY statements.

For example ..it may be a HOST variable (coming from table) but it could be missing from the SELECT statement itself AND the Table DCLGEN may not be initialised anyplace.

Also SOC7s owing to UNITIALISED DATA cannot be predicted ..it may be working for you today in TEST ...one fine day it may not. I have seen programs run for YEARS without abending but one fine day they hit a SOC7 ..when the problem always existed (Uninitialised Data) !

Also that move could potentially cause truncated data whenever the source data item value would be bigger than what the variable you are moving it to can hold. Why should you want to risk this is another issue though (not a cause of SOC7).

Vini

[Jai]

Hi Vani,

I have already initialized the Host Variables of all the Tables in Initialization Para in Test Region itself before moving to Prod.

As Practically, Data won't be greater than the smallest size declaration of both the tables, it won't be a problem after truncation also.

Please let me know, if you could trace anything else.


Hi Kolusu,

Please find the messages in sysout:
------------------------------------------
CEE3207S The system detected a data exception (System Completion Code=0C7).
From compile unit VEUSY06S at entry point VEUSY06S at statement 2487 at compile unit offset +00002E74 at
address 3516B03C.
<> LEAID ENTERED (LEVEL 09/02/1999 AT 08.41)
<> LEAID ABENDAID DD ALLOCATED BY CWBMAKDD DYNALLOC RC =00000

Please find the messages in SYSTSPRT:
------------------------------------------
DSN ENDED DUE TO ERROR+
SYSTEM ABEND CODE 0C4 REASON CODE 00000004

Please find the messages in Diagnostic Section:
------------------------------------------
* Diagnostic Section *
**********************


A Data Exception was caused by data referenced at displacement B79
from the start of TGT BLW cell 01 (X'1'). The field contains
X'0000'. Refer to the data division map in the program listing to
locate the field name.

The field causing the exception is located in Working-Storage of
program VEUSY06S.

Because the program is re-entrant, Working-Storage is located outside
of the program.

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

A Data Exception is caused when a computational-3 field has
an invalid digit (not 0-9), or its last byte contains an invalid
sign (not F, C, or D).


Please let me know, if you could trace the Problem.

Thanks in advance.
_________________
Have a Great Day.
Thanks & Regards,
Jai