|
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| UNIX for Dummies Questions & Answers If you're not sure where to post a UNIX or Linux question, post it here. All UNIX and Linux newbies welcome !! |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Cobol File Status 41 & 42 | WS-NFG | UNIX for Dummies Questions & Answers | 2 | 10-12-2007 09:23 AM |
| Installing RedHat 8.0 onto Dell PowerEdge SC1425 - hdc: status error: status = 0x58 | fishsponge | Red Hat | 5 | 07-14-2006 03:53 PM |
| check the status and send an email with status | isingh786 | Shell Programming and Scripting | 3 | 12-29-2005 07:22 PM |
| Couldn't open status file /var/samba/STATUS.LCK | macdonto | UNIX for Dummies Questions & Answers | 2 | 08-08-2001 09:42 AM |
| file status during FTP | sean76 | UNIX for Dummies Questions & Answers | 3 | 07-01-2001 11:06 PM |
 |
Powered by 
|
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
08-02-2006
|
||||
|
||||
|
COBOL file status 39
When I execute a COBOL load module, I get the following error:
HTML Code:
$ a.out
IWZ200S Error detected during OPEN for file 'ABE-INPUT'. File status is: 39.
Message routine called from offset 0x38 of routine iwzWriteERRmsg.
iwzWriteERRmsg called from offset 0x3c4 of routine _iwzCallUseProc.
_iwzCallUseProc called from offset 0xaf0 of routine _iwzBSeqOpen.
_iwzBSeqOpen called from offset 0x2ec of routine _iwzGenericOpen.
_iwzGenericOpen called from offset 0x25c of routine ABEPREP.
IWZ901S Program exits due to severe or critical error.
IOT/Abort trap(coredump)
This program runs sucessfully on an AS400 so I know the length is correct. The file ABE-INPUT has a record lenght of 132 but obviously, UNIX does not think so. How can I tell what UNIX thinks it is? Thanks in advance. |
|
08-02-2006
|
||||
|
||||
|
Errors like that can get snarfled on UNIX. On unix the first thing to check is datafile permissions, and does it actually exist? Next thing is the SELECT statement. Code:
SELECT MSGTEXT-FILE ASSIGN TO MSGTEXT
ORGANIZATION IS LINE SEQUENTIAL.
IF you have a SELECT with ASSIGN like this, you need to have an enviromnent variable like this: Code:
MSGTEXT=/path/to/actual_datafile And if it is a file length problem, you need to be sure the real datafile does not have carriage control characters in it for fixed record length (LRL) files. Otherwise you have to use something like the above SELECT stsatement to be able to read the file. I really think it's one of the first two things I mentioned. |
|
08-03-2006
|
||||
|
||||
|
I changed my assign statement from
SELECT ABE-INPUT ASSIGN TO STL-ABEMTHFULL to SELECT ABE-INPUT ASSIGN TO ABEMTHFULL This worked. Thanks a bunch. I cant believe how fast this machine is. It processed 660,000 132 byte records in about 10 seconds. This in a program that contains some pretty decent tabling. I'm impressed. Do you know anything about running the IDEBUG debugger? |
|
08-03-2006
|
||||
|
||||
|
No. But you should consider making sure all of the cobol compiles correctly i.e., better than rc=8.
You can use DISPLAY statements placed strategically to get a lot of "debug" work done. |
|
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
Hybrid Mode
