View previous topic :: View next topic
|
Author |
Message |
Sasi Kiran Patha Warnings : 2 New User
Joined: 19 Nov 2006 Posts: 73 Location: Hyederabad
|
|
|
|
hi,
I have a VS COBOL program to be converted to COBOL/370 version.
In the program the record (01 level) INTERFACE-RECORD is in a copy book that is of variable lenth [2393]. The record contains both numeric and alphanumeric fields.
COBOL/370 is not allowing the initialization of INTERFACE-RECORD.
In VS COBOL spaces are moved to INTERFACE-RECORD.
While executing a move statement in COBO/370 version:
MOVE INTERFACE-RECORD to ws-record [pic x(937)] S0C7 is encountered.
how do we solve this.
regards,
Sasi Patha. |
|
Back to top |
|
|
trgk03
New User
Joined: 20 Jan 2006 Posts: 12 Location: kochi
|
|
|
|
Hi Patha,
I think you cannot move INTERFACE-RECORD to ws-record [pic x(937)] directly instead you need to move the individual variables one by one into ws-record.(define similar variables under ws-record of same size as that of interface-record)
I think this abend code SOC7 is comming becz u are moving variables of incompatiable type.
Regards,
Ds |
|
Back to top |
|
|
Sasi Kiran Patha Warnings : 2 New User
Joined: 19 Nov 2006 Posts: 73 Location: Hyederabad
|
|
|
|
hi,
I was able to debug the issue.
the interface-record was variable length because of a table having depending upon clause. The depending upon variable was not intitialized in the COBOL program. done it and successfully executed.
Thank u for reply.
regards,
Sasi Patha. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Just want to add a bit of clarification -
The 0c7 was not caused by the move of unequal lengths. Group moves are alphanumeric and will not give an 0c7.
The abend was most likely due to using a "numeric" field that was corrupted by the mis-matched move.
Good catch finding your abend |
|
Back to top |
|
|
|