06-05-2013 08:46 AM
we tested the product for batch environment, but we get the following message :
+NO CONFIG FILE AVAILABLE
+viidb : module SASVK loaded 500 times for task SASXKERN
+viidb : module SASVK loaded 1000 times for task SASXKERN
+viidb : module SASVK loaded 1500 times for task SASXKERN
+viidb : module SASVK loaded 2000 times for task SASXKERN
IEA995I SYMPTOM DUMP OUTPUT 060
SYSTEM COMPLETION CODE=0C1 REASON CODE=00000001
TIME=14.39.06 SEQ=00053 CPU=0000 ASID=001A
PSW AT TIME OF ERROR 078D2000 80000002 ILC 2 INTC 01
NO ACTIVE MODULE FOUND
DATA AT PSW 00000000 - 000A0000 000130E1 00000000
GR 0: 1A67C379 1: 1A8D47C0
2: 000000C4 3: 1A8D4528
4: 00038580 5: 00037C9C
6: 00057330 7: 1A8D8020
8: 00000000 9: 00000000
A: 1A705688 B: 1A6FF000
C: 800510F0 D: 1A8D4710
E: 80038186 F: 00000000
END OF SYMPTOM DUMP
Thanks in advance for your help
06-05-2013 08:50 AM
I haven't seen a OC1 in a long time.
You got some bad data there - and it looks like it was not SAS doing it because the program name is not in the error message.
Usually, a 0C1 is caused by reading a character value in a numeric field - and it usually happens in a COBOL or ASSEMBLER language program. Is your SAS code calling something written in another language?
Brings back my youth.....
06-05-2013 09:41 AM
It would be better to see the program itself. I think it may be doing something "old-school", like calling
a COBOL or ASSEMBLER program. I have never seen the SAS program itself generate a S0C1
error, but most other mainframe programs can and do (a lot).
I also have heard of pass through SQL's doing it as well, but the cause is at the "other end".