|
View previous topic :: View next topic
|
| Author |
Message |
rrlogu
Warnings : 1
New User
Joined: 13 Sep 2006
Posts: 13
|
|
|
|
Hi,
i have a small problem in handling line sequential file. In FD entry i declared the file length as 120 and in JCL i am passing file with lrecl = 120,FB and i am trying to open in output mode then the jcl is abending with U1035 (i am getting error with file status 90.)
I tried with RECFM=FB/VB and LRECL=120/122/118, and i'm getting the same probl.
i have read in net that Line Sequential files have 2 extra characters in each record for CR/LF.
Some body can help to overcome this problem.
Following are the code details.
COBOL:
.................
.................
SELECT FILEIN ASSIGN TO INFILE
ORGANIZATION IS LINE SEQUENTIAL
ACCESS MODE IS SEQUENTIAL.
.................
.................
FD FILEIN
RECORDING MODE IS F
RECORD CONTAINS 120 CHARACTERS
BLOCK CONTAINS 0 RECORDS
DATA RECORD IS IN-FILE.
01 IN-FILE PIX X(120).
.................
.................
PROCEDURE DIVISION
OPEN OUTPUT FILEIN.
JCL:
//INFILE DD DSNAME=TEST.PS1,DISP=(MOD,CATLG,DELETE),
//* SPACE=(TRK,(10,10),RLSE),LRECL=120,UNIT=SYSDA,RECFM=F |
|
| Back to top |
|
 |
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
That does NOT look like a proper allocation for an HFS Line-Sequential file.
This section of the Enterprise COBOL for z/OS, Version 3.4, Programming Guide gives some more details for using Line-Sequential files.
| rrlogu wrote: |
| i have read in net that Line Sequential files have 2 extra characters in each record for CR/LF. |
That would seem to be a false statement:
| Quote: |
Line-sequential files reside in the hierarchical file system (HFS) and contain only printable characters and certain control characters as data. Each record ends with an EBCDIC new-line character (X'15'), which is not included in the record length.
|
|
|
| Back to top |
|
|
rrlogu
Warnings : 1
New User
Joined: 13 Sep 2006
Posts: 13
|
|
|
|
| With this information i am unable to resolve my problem. Please suggest me a way to over come the U1035 abend for the above code. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
It might help if You straightened up a little bit Your terminology...
line sequential is a, unixese term  , sequential file residing on an hfs file structure
but from Your jcl it seem to be a simple sequential dataset residing on a standard mvs volume
so... allocate the file on an HFS volume, and run under the USS environment
or... do not declare as line sequential and run in a standard MVS environment |
|
| Back to top |
|
|
rrlogu
Warnings : 1
New User
Joined: 13 Sep 2006
Posts: 13
|
|
|
|
| Please confirm, is the Line Sequential is related to Mainframe or not? |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| YES it is, but, reread what we posted, and the manual |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Yes, line sequential is related to the mainframe.
Why do you believe you need to work with a line sequential file?
What specification or requirement is there that caused you to believe this?
If all you need to do is write some data into a file to transfer to some other system, a line sequential file is very possibly not needed. We create hundreds of files to send to win-based and unix targets and to date have not used any line sequential files. |
|
| Back to top |
|
|
|
|
