IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

File status 90: When opening the file


IBM Mainframe Forums -> COBOL Programming
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
MoLong

New User


Joined: 07 Feb 2007
Posts: 32
Location: Chennai

PostPosted: Sat Feb 17, 2007 10:18 am
Reply with quote

Hi
I have a ps with lrecl=23.
In my cobol prg i have fd with e cols(10,10,3).
when i try to open the open the file i get file status 90 error.
can some one tell me why this happens and how i must solve it.
Back to top
View user's profile Send private message
William Thompson

Global Moderator


Joined: 18 Nov 2006
Posts: 3156
Location: Tucson AZ

PostPosted: Sat Feb 17, 2007 3:22 pm
Reply with quote

MoLong wrote:
I have a ps with lrecl=23.
In my cobol prg i have fd with e cols(10,10,3).
when i try to open the open the file i get file status 90 error.
can some one tell me why this happens and how i must solve it.
You have a little work in front of you.
File status 90:
Quote:
1. For multithreading only: A CLOSE of a VSAM or QSAM file was attempted on a thread that did not open the file.
2. Without multithreading: For VSAM only: See the information on VSAM return codes in the Enterprise COBOL Programming Guide.

From the Enterprise COBOL Programming Guide
Quote:
Often the two-character FILE STATUS code is too general to pinpoint the disposition of a request. You can get more detailed information about VSAM input or output requests by coding a second status area:

FILE STATUS IS data-name-1 data-name-8

The variable data-name-1 specifies the two-character COBOL file status key. The variable data-name-8 specifies a 6-byte data item that contains the VSAM return code when the COBOL file status key is not 0.

You can define the second status area, data-name-8, in the WORKING-STORAGE SECTION as in VSAM-CODE here:
Code:
01 RETURN-STATUS.
   05 FS-CODE PIC X(2).
   05 VSAM-CODE.
      10 VSAM-R15-RETURN PIC S9(4) Usage Binary.
      10 VSAM-FUNCTION PIC S9(4) Usage Binary.
      10 VSAM-FEEDBACK PIC S9(4) Usage Binary.
COBOL for OS/390 & VM uses data-name-8 to pass information supplied by VSAM.
Which you are going to have to add the additional file status areas and rerun your job and display the three vsam numbers from the error.

Good luck
Back to top
View user's profile Send private message
MoLong

New User


Joined: 07 Feb 2007
Posts: 32
Location: Chennai

PostPosted: Sat Feb 17, 2007 5:26 pm
Reply with quote

Hi william,
my data is this
AAAAAAAAAATRAINER 100
BBBBBBBBBBSALESSALES250

It is a normal ps. not vsam.
my ddspec is
//go.ddstu dsn=...,disp=shr
no other params specified. should i give them.
when i created the ps i gave reclen 23.
Back to top
View user's profile Send private message
William Thompson

Global Moderator


Joined: 18 Nov 2006
Posts: 3156
Location: Tucson AZ

PostPosted: Sat Feb 17, 2007 5:38 pm
Reply with quote

Why "go,ddstu"?
What is the select?
Open input or output?
what is the recfm?
Back to top
View user's profile Send private message
MoLong

New User


Joined: 07 Feb 2007
Posts: 32
Location: Chennai

PostPosted: Sat Feb 17, 2007 5:50 pm
Reply with quote

I'm calling it from IGYWCLG so //go.ddstu
The select entry is
-----
SELECT STU-FILE ASSIGN TO DDSTU
ORGANIZATION IS LINE SEQUENTIAL
FILE STATUS IS FS
ACCESS MODE IS SEQUENTIAL.
------
i'v not specified dsorg.
just
//go.ddstu dd dsn=...,disp=shr
Back to top
View user's profile Send private message
William Thompson

Global Moderator


Joined: 18 Nov 2006
Posts: 3156
Location: Tucson AZ

PostPosted: Sat Feb 17, 2007 5:56 pm
Reply with quote

How was the line sequential file created?
Open input or output?
Back to top
View user's profile Send private message
MoLong

New User


Joined: 07 Feb 2007
Posts: 32
Location: Chennai

PostPosted: Sat Feb 17, 2007 5:58 pm
Reply with quote

i've even tried
-----
//GO.DDSTU DD DSN=DMKSP04.SEQ.STUDAT,DISP=SHR,
// DCB=(LRECL=23,RECFM=FB,DSORG=PS)
......
still no use.
OPEN INPUT STU-FILE.
Back to top
View user's profile Send private message
MoLong

New User


Joined: 07 Feb 2007
Posts: 32
Location: Chennai

PostPosted: Sat Feb 17, 2007 6:00 pm
Reply with quote

i typed the data in ISPF editor.
First i tried to create the file.got the same error. so i tried to read after creating the PS. still same error.
Back to top
View user's profile Send private message
William Thompson

Global Moderator


Joined: 18 Nov 2006
Posts: 3156
Location: Tucson AZ

PostPosted: Sat Feb 17, 2007 6:00 pm
Reply with quote

How was the line sequential file created?
Back to top
View user's profile Send private message
MoLong

New User


Joined: 07 Feb 2007
Posts: 32
Location: Chennai

PostPosted: Sat Feb 17, 2007 6:09 pm
Reply with quote

i typed the data in ISPF editor.
Back to top
View user's profile Send private message
William Thompson

Global Moderator


Joined: 18 Nov 2006
Posts: 3156
Location: Tucson AZ

PostPosted: Sat Feb 17, 2007 6:14 pm
Reply with quote

From the FM
Quote:
Line-sequential organization
In a line-sequential file, each record contains a sequence of characters ending with a record delimiter. The delimiter is not counted in the length of the record.
Try the select without the "line"....
Back to top
View user's profile Send private message
MoLong

New User


Joined: 07 Feb 2007
Posts: 32
Location: Chennai

PostPosted: Sat Feb 17, 2007 6:33 pm
Reply with quote

Thanks a lot it now works.
I o you one.
But expect many more questions.
Back to top
View user's profile Send private message
William Thompson

Global Moderator


Joined: 18 Nov 2006
Posts: 3156
Location: Tucson AZ

PostPosted: Sat Feb 17, 2007 6:39 pm
Reply with quote

Ok.
Back to top
View user's profile Send private message
piyush2129

New User


Joined: 26 Sep 2006
Posts: 4

PostPosted: Wed Sep 23, 2009 2:30 pm
Reply with quote

Hi I am having this issue while running my JCL:

THE OPEN OF FILE WITH SYSTEM-NAME OACTL (ON VSAM) WAS UNSUCCESSFUL. AN ABEND OCCURRED IN VSE LIOCS DURING OPEN PROCESSING.THERE WAS AN UNSUCCESSFUL OPEN OR CLOSE OF FILE OACTL IN PROGRAM OAU000 AT RELATIVE LOCATION X'0B74'.NEITHER FILE STATUS NOR AN ERROR DECLARATIVE WERE SPECIFIED. THE STATUS CODE WAS 90.FROM COMPILE UNIT OAU000 AT ENTRY POINT OAU000 AT STATEMENT 701 AT COMPILE UNIT OFFSET +00000B74 AT ADDRESS 00600BEC.

Please Help.
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6248
Location: Mumbai, India

PostPosted: Wed Sep 23, 2009 2:40 pm
Reply with quote

As you've searched through this thread already -- did you check on the lines what William has suggested long back.
Back to top
View user's profile Send private message
piyush2129

New User


Joined: 26 Sep 2006
Posts: 4

PostPosted: Wed Sep 23, 2009 2:45 pm
Reply with quote

Hi Anuj i have checked all possible reason but not able to locate the problem as we are using Z/VSE instead of Z/OS and I am new for this OS.
Back to top
View user's profile Send private message
Terry Heinze

JCL Moderator


Joined: 14 Jul 2008
Posts: 1248
Location: Richfield, MN, USA

PostPosted: Wed Sep 23, 2009 10:11 pm
Reply with quote

Could this be the problem? publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IGY3PG30/1.10.3.8?DT=20050628164603
See last sentence.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> COBOL Programming

 


Similar Topics
Topic Forum Replies
No new posts Unable to interpret a hex value to De... COBOL Programming 4
No new posts how to eliminate null indicator value... DB2 7
No new posts Format Binary file to EBCDIC JCL & VSAM 4
No new posts Binary File format getting change whi... All Other Mainframe Topics 7
No new posts How to turn off 'ACTION' SDSF output ... TSO/ISPF 2
Search our Forums:

Back to Top