I will ask a question that should have been asked first time around. Is there a valid unit name of VIO?
Ed > On Sep 26, 2016, at 3:55 PM, Joe Reichman <[email protected]> wrote: > > Just NODECK but it still looked for SYSLIN I allocated with VIO but dummied > it got the Asssembly list > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Edward Gould > Sent: Monday, September 26, 2016 4:44 PM > To: [email protected] > Subject: Re: S99ERROR = 21C For &&OBJ UNIT=VIO > > What options did you pass to the assembler? > > Ed > >> On Sep 25, 2016, at 7:00 AM, Joseph Reichman <[email protected]> > wrote: >> >> Well >> >> I was able to allocate the datasets run Or BASSM to the assembler >> >> But I cann't find the sysprint dataset >> >> I had disp=(new,catlg) >> >> Thanks >> >> I am going to change the name and see >> >>> On Sep 25, 2016, at 7:52 AM, J R <[email protected]> wrote: >>> >>> SA23-1371-05 >>> >>> z/OS V2R2 MVS Authorized Assembler Services Guide >>> >>> Chapter 26. Requesting dynamic allocation functions >>> >>> Page 646. >>> >>> Sent from my iPhone >>> >>> On Sep 25, 2016, at 00:38, Paul Gilmartin > <[email protected]<mailto:0000000433f07816-dmar > [email protected]>> wrote: >>> >>> On Sun, 25 Sep 2016 02:02:43 +0000, J R wrote: >>> >>> From the FM: >>> >>> Verb code 01 - Dsname allocation text units >>> >>> Dsname specification - Key = '0002' >>> >>> DALDSNAM specifies the name of the data set to be allocated. The data set > name can contain special characters, if the data set name is enclosed in > apostrophes. The system cannot catalog a data set name enclosed in > apostrophes; it will use a disposition of KEEP instead. The data set name > can contain system symbols. See the information on using system symbols in > z/OS MVS Initialization and Tuning Reference for more information. >>> >>> The maximum length of the data set name is 44 characters, excluding any > enclosing apostrophes and compressing any double apostrophes within the data > set name. >>> >>> Example: To specify the temporary dsname &LOAD, code: KEY # LEN PARM >>> >>> 0002 0001 0005 50 D3 D6 C1 C4 >>> >>> Unless I'm badly missing the context (which FM?) this is an egregious >>> hodgepodge of Assembler syntax, JCL syntax, and DYNALLOC specification. >>> By experiment several decades ago: >>> >>> o I could create data sets with outrageous names; internal blanks, >>> NUL characters ... Administrators complained to me when they were >>> unable to scratch them with the utility they used. >>> >>> o I don't believe apostrophes, single or double, were necessary. >>> I could have built the DALDSNAM TU with a sequence of AL1(nnn) >>> constants. >>> >>> o '&' means nothing to DYNALLOC. The example simply refers to a data >>> set name beginning with the AL1(80) byte. Temporary DSNs and >>> DISP=PASS are handled by JCL and the initiator. >>> >>> o I don't know whether DYNALLOC substitutes system symbols (it came >>> about after my experiments). But I believe that's done (only?) by >>> JCL processing. >>> >>> o JCL, from an overabundance of caution, believes any data set name >>> surrounded by apostrophes is ineligible for catalog processing. >>> (I need to try DSN='SYS1.MACLIB' to see whether it works.) >>> >>> o DISABLE(DSNCHECK) profoundly changes the rules. I don't know which >>> services respect or enforce this. I doubt that JCL will allow >>> catalog processing of data set names containing special characters or >>> even consecutive periods or qualifiers longer than 8 characters >>> despite DISABLE(DSNCHECK)'s being in effect. >>> >>> -- gil >>> >>> --------------------------------------------------------------------- >>> - For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to >>> [email protected]<mailto:[email protected]> with the >>> message: INFO IBM-MAIN >>> >>> --------------------------------------------------------------------- >>> - For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to [email protected] with the message: INFO >>> IBM-MAIN >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, send >> email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
