> Why in blazes don't you specify a legal LRECL The entire situation is more complex than a listserve note. There are many variables, unknowns, and tradeoffs. One automated process is generating JCL; another process over which I have less control is running under that JCL. I don't specify LRECL, etc., in the JCL because in some cases the automated process does not know in every case what the other process is expecting.
This problem is not unsolvable. I am not asking how to solve it. I have solved it. The points of my posts were 1. Initially, could someone who is more up-to-date on channel programs than I please decode the CCW gibberish for me? 2. And then, why the heck can't DFSMS put out a message like "illegal blocksize" rather than a message like 8000000000AC0004042084000000000000000000FF010F0000004EA00000AC00 FAILING PARAMETER LIST DATA = 8680000400AC000000AC000000000000. You guys wonder why the mainframe has fallen from favor and has a reputation for requiring the labor of guys with 40 years of experience to parse its entrails? Look no further than this message. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Rick Fochtman Sent: Monday, January 22, 2007 8:08 AM To: [email protected] Subject: Re: What is "command reject" trying to tell me? IIRC, from the beginning of this thread, the LRECL was specified as 0. Why in blazes don't you specify a legal LRECL for a FB dataset, plus DSORG=PS? Then the BLKSIZE won't BE set to zero by SDB and the whole problem goes away? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
