On 2/22/2012 9:47 AM, Paul Gilmartin wrote:
Why is a RDJFCB required at all? I'm primarily not an assembler
programmer, but I've coded a few OPENs successfully, but never
a RDJFCB. I would suggest that if RDJFCB fails, let FLOWASM,
not assembler, proceed with its OPEN and I/O processing.
While I can't speak to FLOWASM, I use RDJFCB (or occasionally
the equivalent of TIOT search and JFCB look-up) almost as often
as OPEN. I spent a lot of time working for ISVs and service
bureaus, and frequently wrote or modified utility programs.
Programmers unused to JCL, or new to the system, have some bad
habits. These include specification of a PDS name for intended
sequential output, specifying a member name when they should
not, misspelling an input member name, using incorrect DCB
values, etc.. It is fairly simple to use lower level system
functions (RDJFCB, LOCATE, OBTAIN, etc.) to validate a user
request, and provide a clear error message ('Member name XYZ on
DD SYSUT1 does not exist in data set r.s.t') rather than an S013
abend with an IEC020I message (and even the IEC message is a
later addition by IBM).
Gerhard Postpischil
Bradford, VT
