Re: use of CLOSE UNIT FOR REMOVAL
From: Frank Swarbrick (Frank.Swarbrick_at_efirstbank.com)
Date: 03/08/04
- Next message: Frank Swarbrick: "Re: use of CLOSE UNIT FOR REMOVAL"
- Previous message: 0.8913502593874477: "Urgent: 5000 Euro Reward (0.3150507894353367)"
- In reply to: mircea: "Re: use of CLOSE UNIT FOR REMOVAL"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 8 Mar 2004 10:47:07 -0700
Hi Mircea,
Actually, following your link I was able to find other link which gave the
the answer I was looking for. That link is:
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&newwindow=1&threadm=B0000
107577%40apps.escape.net.au&rnum=1&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DUTF
-8%26newwindow%3D1%26selm%3DB0000107577%2540apps.escape.net.au
This link may only apply to VSE, but anyway the answer is very simple. So
simple it's embarassing, actually! Basically, it's just the following:
CLOSE filename REEL FOR REMOVAL
CLOSE filename
OPEN INPUT filename
What I had been trying to do was eject the tape and process the next tape as
part of the "same file", kind of as if it was a single file spanning more
than one tape. The above way simply treats the new tape as, well, a new
tape. Which is the way the program was working in the first place, with the
only difference being the old way was something like:
CLOSE filename
STOP "OPERATOR: Please eject current tape and enter new tape, then press
Enter"
OPEN INPUT filename
Thanks for the pointer! I had done a google groups search but had not seen
what I was looking for.
---
Frank Swarbrick
Senior Developer/Analyst - Mainframe Applications
FirstBank Data Corporation - Lakewood, CO USA
>>> mircea<mircea_tamas@yahoo.com> 3/7/2004 8:27:29 AM >>>
Frank
your problem seems to mirror my problem about "Tape load/unload from
within a Cobol/MVS program" at
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&threadm=5f25b5cf
.0301230204.71170b4c%40posting.google.com&rnum=1&prev=/groups%3Fhl%3Den%26lr
%3D%26ie%3DUTF-8%26oe%3DUTF-8%26selm%3D5f25b5cf.0301230204.71170b4c%2540post
ing.google.com
I had to write an undefinite number of tapes, every tape containing
one file with same structure. You have to read the same thing.
The clue is dynamic allocation of tapes through an Assembler
subroutine.
In my program, after the first tape is allocated to program, file it's
written, file closed and tape deallocated. Now the second tape can be
mounted, allocated to program and so on.
I don't know if dynamic allocation is allowed under VSE, this can be
really sad.
Another push to upgrade. ;)
Regards,
Mircea
- Next message: Frank Swarbrick: "Re: use of CLOSE UNIT FOR REMOVAL"
- Previous message: 0.8913502593874477: "Urgent: 5000 Euro Reward (0.3150507894353367)"
- In reply to: mircea: "Re: use of CLOSE UNIT FOR REMOVAL"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
