Table Lock--SOC1

naive · New User Joined: 26 Apr 2005 Posts: 46 Location: LA

Guys

this is a real jam for me...
we have a DB2 table on which a column was added. The program using the column is failing repeatedly without giving any message!!
It is a SOC1 abend!!

Anyone help please!!

ranjitbhingare · New User Joined: 30 Nov 2005 Posts: 94 Location: PUNE

Hi,

As per my knowledge we get SOC1 when there is some logical error. I would suggest you to check the logic.

correct me if I am wrong!

Regards,
Ranjit....

ragshere · New User Joined: 20 Dec 2004 Posts: 70

Hi,
S0C1 will come for many reasons...It may not be occurred because of adding a column to a table. Just verify whether DCLGEN of the table contains this new column definition.

S0C1 explanation is here
S0C1 - OPERATION EXCEPTION - AN OPERATION CODE IS NOT ON THE MACHINE
--POSSIBLE CAUSE--
SUBSCRIPT ERROR - CLOBBERED CODE
TRIED TO READ A FILE THAT WAS NOT OPEN
MISSPELLED DDNAME
ERROR IN PARAMETERS PASSED TO SUBROUTINES
MISSING DD CARD
RECORDING MODE WAS WRONG, OR DENSITY WAS INCORRECT
BAD LOAD MODULE, POSSIBLE BAD OBJECT DECK OR MISSING SUBROUTINE

FORTRAN - MISSING DIMENSION STATEMENT, SAME NAME FOR ARRAY AND A SUBROUTINE

COBOL - SUBROUTINE PROG ID WAS THE SAME AS THE ENTRY NAME COBOL - TRIED TO CALL WITHIN COBOL F SORT INPUT/OUTPUT PROCEDURE
COBOL - TRIED TO CALL A SUBROUTINE WHICH COULD NOT BE FOUND COBOL - INCOMPLETE DCB FOR SORTIN COBOL - USING SORT VERB, DDNAME WAS NOT SORTOUT WHEN THE GIVING OPTION WAS USED. COBOL - EXECUTING SORT-USING AFTER OPENING SORTIN

check whether one of above will match your problem

Thanks
Raghavendra

naive · New User Joined: 26 Apr 2005 Posts: 46 Location: LA

thanks guys... figured out the problem... memory. program was in vscobol, so run below 24 byte line.The Db2 -IMS load module libraries had been mucked up.Now b2 is OK, but the systems programmer said IMS cant be compiled for a prog in VSCOB3700..