IMHO the problem is with using file utilities for datasets.
File - understood as MS-DOS, unix or Windows file - it is just (ordered)
set of bytes. No internal structure like blocks or records. File formats
like XLS, TXT, DOC are interpretation of some applications, it is not
visible
Dataset - set of block which may contain records. Structure, which is
lost every time you transfer dataset from host to PC or when you
transfer from host ...to host using file oriented tool like ftp.
Note when you download a dataset from host, i.e. using IND$FILE or ftp,
you always convert dataset to PC file. That could mean EBCDIC-ASCII
translation or not, but it always mean lost of dataset format. So, when
you want to upload the file to host again you have to provide "metadata"
like FB 80 or so. Othwerwise you'll get corrupt file - the content is
almost the same, but records are not.
Of course ftp or IND$FILE can handle FB dataset with no problem, it also
can handle VB datasets (in many cases). However RECFM=U datasets are
(for my humble knowledge) simply not handled properly. Excepions may
happen, but I never seen them. Nor working procedure how to transfer
RECFM=U dataset.
Remarks:
1. It has nothing to do with ADRDSSU. It is not problem of DSS, it is
just problem with RECFM=U, regardless of the tool which created dataset.
2. Usually the simplest solution of to "pack" RECFM=U dataset to some FB
dataset. Methods are TERSE or just XMIT. In both cases you get some FB
dataset, which can be downloaded from host to PC file and then uploaded
from PC file to host *with some additional information* about RECFM and
LRECL.
3. Maybe there are other tricks or methods. I'm glad to learn them.
--
Radoslaw Skorupka
Lodz, Poland
======================================================================
Jeśli nie jesteś adresatem tej wiadomości:
- powiadom nas o tym w mailu zwrotnym (dziękujemy!),
- usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś
na dysku).
Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać
tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza)
tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać
karze.
mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950
Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st.
Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 0000025237,
NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na
01.01.2019 r. wynosi 169.347.928 złotych.
If you are not the addressee of this message:
- let us know by replying to this e-mail (thank you!),
- delete this message permanently (including all the copies which you have
printed out or saved).
This message may contain legally protected information, which may be used
exclusively by the addressee.Please be reminded that anyone who disseminates
(copies, distributes) this message or takes any similar action, violates the
law and may be penalised.
mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950
Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital
City of Warsaw, 12th Commercial Division of the National Court Register, KRS
0000025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN
169.347.928 as at 1 January 2019.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
