Re: [OT] EBCDIC to ASCII OPTCD=Q? (JCL)

In article <s%CPg.28511$jS4.18972@xxxxxxxxxxxxxxxxxxxxxx>,
William M. Klein <wmklein@xxxxxxxxxxxxxxxxx> wrote:
A couple of answers (to you and other posts).

1) IBM mainframe (currently) only supports CODESET and OPTCD=Q for TAPE
datasets. I *think* that if you use BOTH CODESET clause and OPTCD=Q, then you
SHOULD be able to produce an ASCII TAPE output.

Gah. Thanks much, Mr Klein; I am trying to do this entirely by
utilities/JCL and I hope to avoid a dedicated COBOL program... if my hopes
are in vain then I'll start down this path.


2) My best guess from the symptoms reported is that this MIGHT be a "label
records standard" issue. I think COBOL OPTCD=Q files. Check out:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/igy3pg31/1.9.7

Most valuable... thanks much!

[snip]

4) Will you have any COMP-3 or non-USAGE DISPLAY output (with sign is
separate).
If so, make certain that you (or the person who signs your check) knows
what is
REALLY wanted.

'Victory's father is the guy who signs the time***, defeat's daddy is
The Consultant'... or something like that.


5) All of this assumes a COBOL application. If you want a DFSort answer, I can
make certain that Frank Yeager knows about your post and he can probably
provide
additional DFSort information.

Not necessarily DFSORT, *any* JCL/utility stream which will not require
the creating of a special program full of obscure constructs and arcane
references. The reason for this is, of course, that the less 'stuff' one
needs to get past folks in order to get Prod implementation the less stuff
there is for someone to look at and say 'I don't understand this... so it
doesn't go in.'

(for some reason folks here are more willing to let utilities/JCL
constructs with which they are unfamiliar into Prod - I've put in the
first jobs using things like referbacks and ICETOOL that this shop seems
to have seen - than they are willing to let unfamiliar COBOL constructs
pass in a similar manner)

Thanks much!

DD
.