Re: SDSF and Carriage Control
Is - part of the ASA standard or is it an IBMism? --
Peter Hunkeler
It's pretty hard to find a definitive document. I'd have greater trust in one
that wasn't published by IBM.
While reading RFC 959 (FTP) for some other reasons, I stumbled across the
following text:
Quote3.1.1.5.2. CARRIAGE CONTROL (ASA)
The file contains ASA (FORTRAN) vertical format control
characters. (See RFC 740 Appendix C; and Communications
of the ACM, Vol. 7, No. 10, p. 606, October 1964.) In a
line or a record formatted according to the ASA Standard,
the first character is not to be printed. Instead, it
should be used to determine the vertical movement of the
paper which should take place before the rest of the
record is printed.
The ASA Standard specifies the following control
characters:
Character Vertical Spacing
blank Move paper up one line
0 Move paper up two lines
1 Move paper to top of next page
+ No movement, i.e., overprint
/Quote
Then looking at RFC 740 (NETRJS) I read in appendix C
QuoteCarriage Control
The carriage control characters sent in a printer channel by NETRJS
conform to IBM's extended USASI code, defined by the following table:
CODE ACTION BEFORE WRITING RECORD
Blank Space one line before printing
0 Space two lines before printing
- Space three lines before printing
+ Suppress space before printing
1 Skip to channel 1
2 Skip to channel 2
3 Skip to channel 3
4 Skip to channel 4
5 Skip to channel 5
6 Skip to channel 6
7 Skip to channel 7
8 Skip to channel 8
9 Skip to channel 9
A Skip to channel 10
B Skip to channel 11
C Skip to channel 12
/Quote
So, I conclude that the - indeed is an IBM extension.
--
Peter Hunkeler
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SDSF and Carriage Control
I'm not using it currently, but have done quite recently. It's broadly very similar to SDSF, although it took me months to get used to doing =I to access it instead of =S. And one you're there some of the line commands are different - SDSF's ? is S, whereas SDSF's S is B. One feature I did like is that each entry on the screen is indexed with a number to the left. So instead of having to tab down to the entry you want you just enter that number on the command line and press enter. Very simple and time saving. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: 13 August 2015 21:04 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SDSF and Carriage Control IOF is a SPOOL display product from Fischer International https://urldefense.proofpoint.com/v2/url?u=http-3A__www.fisc.com_products_iof_d=BQIBaQc=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSIr=e3tYBLyxxv2bm6qKB_Bu6i8laFMVOfQGTujvsDqIvKUm=v-s5jwzv02bqaMwQtNQXOPvNnoymejublx_dPMVLf4Us=gTfJyDVlPgCbobAgq4orGc-rVElxWvV74jiaT9eMHbQe= . Interactive Output Facility according to the site. I have a vague memory of it. It is not an SDSF work-alike but, back when I used it, it had some good features. On Thu, Aug 13, 2015 at 2:58 PM, Peter Hunkeler p...@gmx.ch wrote: IOF does and has for at least 14 years support carriage control emulated display (both RECFM=A or M), except for overprinting. Pardon my ignorance, but what is IOF? -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Schrodinger's backup: The condition of any backup is unknown until a restore is attempted. Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be. He's about as useful as a wax frying pan. 10 to the 12th power microphones = 1 Megaphone Maranatha! John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Console messages which has precedence and related questions
Hi, If you have an extended console installed in your program via MCSOPER/MCSOPMSG Does the issuing program get the message before it is displayed on the console If so can you delete before it is displayed via dom Secondly can you search for specific message e.g. IEE... or the best you can do is search for command responses those operator/system messages that require a response Thirdly is the data space created in the home address space I would assume so why would it be in common thanks -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
DFHSM Recovery question
Full volume dumps occur once/week and incremental backups are taken nightly.
Week1 Week2
i.e. DII DII(D=Full Volume DUMP, I=INCREMENTAL)
A recovery test was performed with week 2 day 3 as the recovery date, yet
during DFHSM volume recovery,
DFHSM generated individual dataset recover commands for data created *AND*
migrated prior to the dump for Week2.
i.e. the data was *not* on the volume as of the expected dates involved.
(Week2 Day1-Day3).
Reading in the DFSMShsm Storage Administration Guide( SC23-6871-02), under the
topic
Full-volume restore with update (pp 317 - 320) I find:
DFSMShsm creates a list of candidate data sets from either or both the dump
and backup VTOC
copy data sets to control the volume recovery process. (pp 318).
It is not clear which vtoc/dumpvtoc copies are included.
I would have expected the dumpvtoc copies from the 2nd week and the appropriate
vtoc copies for the incrementals to be used in the
recovery process, but it seems that the dumpvtoc copies from week 1 were also
included when preparing the candidate list.
I have verified that no vtoc copies from week 1 existed at the time of the
recovery.
Can anyone confirm or refute that *both* dumpvtoc copies would be used in this
scenario?
The DUMPCLASS definition used is as follows:
DEFINE DUMPCLASS( /* DEFINE A DUMPCLASS */+
xx /* NAME OF DUMPCLASS */+
DISPOSITION('USER CRITICAL') /*IDENTIFY DUMPS FOR OFFSITE */+
DAY(0)AUTOREUSE NODATASETRESTORE FREQUENCY(7) +
NORESET RETPD(15) STACK(100) UNIT(FAST) VTOCCOPIES(2))
The RECOVER commands issued were as follows:
HSEND RECOVER * TOVOLUME(xx) UNIT(3390) -
REPLACE FROMDUMP(APPLYINCREMENTAL)
Thanks in advance for you time and attention,
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: .Re: Catalog Entry Deletion using a String
The z/OS needs to be at z/OS V1.11 or higher I think for this mask process to work. Lizette -Original Message- From: Lizette Koehler stars...@mindspring.com Sent: Aug 14, 2015 4:00 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: .Re: Catalog Entry Deletion using a String So in TSO HELP DELETE there are two options MASK - The entryname is a MASK filter used to select a range of catalog entries to be deleted. NOMASK - the entryname is the name of a catalog entry to be deleted. I have not worked with MASK yet, but might be worth a check out. Or HLQ.** should work as well. Lizette -Original Message- From: Mike Schwab mike.a.sch...@gmail.com Sent: Aug 14, 2015 3:18 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: .Re: Catalog Entry Deletion using a String Correct. HLQ.** (two asterisks) covers 0-22 levels of qualifiers. On Fri, Aug 14, 2015 at 5:05 PM, DanD mvs-j...@sympatico.ca wrote: Is my head back in the 70's? It used to be that DELETE HLQ.* would only delete the single level after HLQ. If the DSN was HLQ.ONE.TWO it would NOT be deleted. I couldn't see anything in H DELETE under TSO to explain how it handles generics. Dan D -Original Message- From: Lizette Koehler Sent: Thursday, August 13, 2015 12:14 PM Newsgroups: bit.listserv.ibm-main Subject: Re: Catalog Entry Deletion using a String Yes. As others stated, look at the HELP DELETE under TSO. I always back up what I am going to delete just in-case there is something in there I want to keep. You can also use DFDSS to DUMP DELETE as well. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter Sent: Thursday, August 13, 2015 8:20 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Catalog Entry Deletion using a String Hello All, Is it possible to delete a catalog entry using a first HLQ alone ? Like deleting all entry of ZOS21.** instead of specifying each and every qualified dataset ? Peter -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
.Re: Catalog Entry Deletion using a String
Is my head back in the 70's? It used to be that DELETE HLQ.* would only delete the single level after HLQ. If the DSN was HLQ.ONE.TWO it would NOT be deleted. I couldn't see anything in H DELETE under TSO to explain how it handles generics. Dan D -Original Message- From: Lizette Koehler Sent: Thursday, August 13, 2015 12:14 PM Newsgroups: bit.listserv.ibm-main Subject: Re: Catalog Entry Deletion using a String Yes. As others stated, look at the HELP DELETE under TSO. I always back up what I am going to delete just in-case there is something in there I want to keep. You can also use DFDSS to DUMP DELETE as well. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter Sent: Thursday, August 13, 2015 8:20 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Catalog Entry Deletion using a String Hello All, Is it possible to delete a catalog entry using a first HLQ alone ? Like deleting all entry of ZOS21.** instead of specifying each and every qualified dataset ? Peter -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: .Re: Catalog Entry Deletion using a String
Correct. HLQ.** (two asterisks) covers 0-22 levels of qualifiers. On Fri, Aug 14, 2015 at 5:05 PM, DanD mvs-j...@sympatico.ca wrote: Is my head back in the 70's? It used to be that DELETE HLQ.* would only delete the single level after HLQ. If the DSN was HLQ.ONE.TWO it would NOT be deleted. I couldn't see anything in H DELETE under TSO to explain how it handles generics. Dan D -Original Message- From: Lizette Koehler Sent: Thursday, August 13, 2015 12:14 PM Newsgroups: bit.listserv.ibm-main Subject: Re: Catalog Entry Deletion using a String Yes. As others stated, look at the HELP DELETE under TSO. I always back up what I am going to delete just in-case there is something in there I want to keep. You can also use DFDSS to DUMP DELETE as well. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter Sent: Thursday, August 13, 2015 8:20 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Catalog Entry Deletion using a String Hello All, Is it possible to delete a catalog entry using a first HLQ alone ? Like deleting all entry of ZOS21.** instead of specifying each and every qualified dataset ? Peter -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: .Re: Catalog Entry Deletion using a String
So in TSO HELP DELETE there are two options MASK - The entryname is a MASK filter used to select a range of catalog entries to be deleted. NOMASK - the entryname is the name of a catalog entry to be deleted. I have not worked with MASK yet, but might be worth a check out. Or HLQ.** should work as well. Lizette -Original Message- From: Mike Schwab mike.a.sch...@gmail.com Sent: Aug 14, 2015 3:18 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: .Re: Catalog Entry Deletion using a String Correct. HLQ.** (two asterisks) covers 0-22 levels of qualifiers. On Fri, Aug 14, 2015 at 5:05 PM, DanD mvs-j...@sympatico.ca wrote: Is my head back in the 70's? It used to be that DELETE HLQ.* would only delete the single level after HLQ. If the DSN was HLQ.ONE.TWO it would NOT be deleted. I couldn't see anything in H DELETE under TSO to explain how it handles generics. Dan D -Original Message- From: Lizette Koehler Sent: Thursday, August 13, 2015 12:14 PM Newsgroups: bit.listserv.ibm-main Subject: Re: Catalog Entry Deletion using a String Yes. As others stated, look at the HELP DELETE under TSO. I always back up what I am going to delete just in-case there is something in there I want to keep. You can also use DFDSS to DUMP DELETE as well. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter Sent: Thursday, August 13, 2015 8:20 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Catalog Entry Deletion using a String Hello All, Is it possible to delete a catalog entry using a first HLQ alone ? Like deleting all entry of ZOS21.** instead of specifying each and every qualified dataset ? Peter -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: LOADING An AMODE64 Program
On Tue, 11 Aug 2015 07:27:06 -0500, John McKown wrote: I will chime in with my _opinion_ that now is the time to start using a STG to an AD field. It is a cheap way to future proof your program for when IBM finally allows RMODE(64). Unless, like someone I knew back in the Amen. And all new control blocks should use 64-bit addresses. 1970's who didn't want to calculate leap years at run time. So she had a hard coded table in her program. It went up to her planned retirement date. Did she then use a binary search, or linear? And in the mid 1980's I was unable to persuade my design team to allow 4 digits for year. Their refutation was that we'd be unable to populate such a field because IBM APIs we needed to use supplied only 2 then. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
