That's what querydub tells you. --- QDB_DUB_MAY_FAIL The task has not been dubbed; an attempt to dub the task may fail. The most likely reason for failure may be a missing or incomplete user security profile; or the lack of an OMVS segment. ---
If the spot you put it in reports that the program is already dubbed, then you know you need to move it earlier in the program. i.e. wherever you put it, you want it to report QDB_DUB_OKAY or QDB_DUB_MAY_FAIL and take some action based on that. In article <[email protected]> you wrote: > > I understood the original question to be how to avoid OMVS > Not exactly. (I love OMVS!) For the original requirement I am going to take > the liberty of quoting here @Tony Harminc's explanation of the problem. > > Back 10+ years ago our problem was that we'd ship our product to a new > > customer, or an existing customer would install it on a new image, and > > they'd overlook our (well documented with examples) requirement for a > > userid with a UNIX (OMVS) segment. So we'd get running, open config > > files, attach various subtasks, initialize a log, etc. etc.and then at > > some point we'd go to open a socket, and Bang! We'd issue a lame > > message about a TCP/IP return code, and keep retrying at intervals. > > Eventually the customer would call support, and someone would work > > from the TCP/IP error code to the actual problem and then walk them > > through fixing up the userid. > Prodded by that thread I want to add some call to our code for the purpose > of explicitly diagnosing the lack of an OMVS segment. The initialization > sequence for a complex product is of course complicated and I wanted to get > the test call in the right place: as late in the initialization as possible > so that as many other diagnostic facilities are available as possible > ("printed" listing, for example) but before any function that would require > OMVS and spoil the whole intent of this exercise. I can run an experiment > but of course a particular situation may not exercise every code path > through initialization. > I am wondering if this is not worthy of an RCF to the C library reference. > Here is a significant prerequisite for some fraction of the calls and it is > at best documented by implication and folklore. > Charles > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of David Griffiths1 > Sent: Wednesday, March 8, 2017 6:29 AM > To: [email protected] > Subject: Re: Which C library functions imply dub? > I understood the original question to be how to avoid OMVS and you almost > certainly need OMVS for printf. For Metal C I wrote my own printf subset > that calls WTO - you at least have varargs. -- Don Poitras - SAS Development - SAS Institute Inc. - SAS Campus Drive [email protected] (919) 531-5637 Cary, NC 27513 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
