Starting with clicking the 'Unix File' box on I've tried just about every >combination and permutation of setting, variations, options and flavors
the TSO File tab allows: fixed length, VB, Undefined, None and lengths of >160, 161 and 162 but nothing works; the output winds up as:
FIRST-SHORT-REC(X'25')SECONDREC DATA HERE AS FAR AS IT GOES(X'25')THIRD
REC HERE FOR SOME MORE(X'25)FOURTH RECORD AT THIS POINT (&c)
That kind of 'striping' of records usually happens when the output LRECL
and the input don't match (and that kind of fits in with X'25' delimiters >instead of X'0D0A'.
Is there a setting I'm missing... or is there a quick-and-dirty PC-based >utility that will get it from variable-length tab-delimited format to
LRECL 160 with space-padding?
On Thu, 2 Sep 2021 14:47:26 -0000 (UTC), docdwarf@panix.com () declaimed
the following:
Starting with clicking the 'Unix File' box on I've tried just about every >>combination and permutation of setting, variations, options and flavors
the TSO File tab allows: fixed length, VB, Undefined, None and lengths of >>160, 161 and 162 but nothing works; the output winds up as:
FIRST-SHORT-REC(X'25')SECONDREC DATA HERE AS FAR AS IT GOES(X'25')THIRD
REC HERE FOR SOME MORE(X'25)FOURTH RECORD AT THIS POINT (&c)
Any further processing might need one to write a script on the source
OS (I'd suggest Python, using one of the dialects of the "csv" module to >parse the input, and an output statement using fixed width formatting codes >-- you'll have to figure out what widths each field requires).
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 66:05:34 |
Calls: | 6,654 |
Files: | 12,200 |
Messages: | 5,331,879 |