Edit macro @PRINT Edit macro @PRINT Author: David McRitchie formatted on 1995/04/01 06:54 for assistance contact: D. McRitchie DMcRitchie@hotmail.com -------------------------------------------------------------------------------- Macro name. @PRINT users. PDF EDIT users particularly type. Edit Macro resides in SYS1.TSOCLIST, and in IS03.SPF2.MACROS for use on SPF/PC -------------------------------------------------------------------------------- @PRINT TSO PRINTOFF for member currently displayed in EDIT -------------------------------------------------------------------------------- related clists -- @VP @PRINTNX related commands -- PRINTOFF, VPSPRINT, PRINTDS -------------------------------------------------------------------------------- Obtain a printed listing of the member currently displayed in EDIT as an alter- native to typing in ===> TSO PRINTOFF 'datasetname(member)' -------------------------------------------------------------------------------- Since square brackets are not available, optional material is enclosed in European brackets <...>. ISREDIT @PRINT <....options...> -------------------------------------------------------------------------------- options, (optional) refer to TSO HELP PRINTOFF for added options. BATCH, will include library dsname(member) date and time in listing. and will utilize PGM=IEBGENER. The following are optional to the TSO command PRINTOFF but will have very little use for this edit macro application and our printers. LIST/NOLIST PRINT/NOPRINT FOLD/NOFOLD The following are optional both to PRINTOFF and to the BATCH job CLASS(x) DEST(xxxxxx) COPIES(x) VOLUME(xxxxxx) VOL(xxxxxx) PAGEDEF(x) HOLD/NOHOLD DEST(NnnRmmmm) DEST(NnnnRMMM) DEST(NnnnnnRmm) node and workstation DEST(Rnnnn) DEST(RMnnnn) DEST(RMTnnnn) remote terminal DEST(Unnn) local terminal routing The following will cause a BATCH job to be used. SCRIPT generates ,FCB=8X11,CHARS=GT12 FCB(xxxx) generates ,FCB=xxxx CHARS(xxxx) generates ,CHARS=xxxx DEST(xx.xx) generates ,DEST=nodename.userid on an OUTPUT statement PRINTOFF provides only for DEST=userid DOWN8 generates ,PAGEDEF=DOWN8,CHARS=GT15,CLASS=2 to print DOWN on our regular paper away from perfo- ration Defaults GT12 if no characters beyond 83, else defaults GT15 good for 103. Print beyond is trun- cated. DOWN10 generates ,PAGEDEF=DOWN10,CHARS=GT15,CLASS=2,LINECT=77 to print DOWN on our regular paper away from perfo- ration defaults GT15 good for 103. Print beyond is trun- cated. DOWN generates ,PAGEDEF=08081,CHARS=GT15,CLASS=2 to print down on our regular paper next to perforation Defaults GT12 if no characters beyond 93, else defaults GT15 good for 111. Print beyond is trun- cated. MA generates ,PAGEDEF=M13280,CHARS=GT20,CLASS=2 to print max across on regular paper next to perfo- ration MD generates ,PAGEDEF=M132C1,CHARS=GT20,CLASS=9 to print max down on regular paper next to perforation SYSTECH treated same as if entering DEST(P100E) The following will allow you to send data to PROFs, (see also SYSTECH SOP #4803) ===> @PRINT PROFS(MCRITCHI) ===> @PRINT PROFS(xxxxxxxx.MCRITCHI) This is equivalent to ===> @PRINT DEST(xxxxxxxx.MCRITCHI) BATCH If you have made changes without saving the following message will appear: ************************************************************************ * YOUR FILE HAS NOT BEEN SAVED AFTER MAKING CHANGES * * THE FILE PRINTED WILL NOT REFLECT CHANGES MADE IN CURRENT EDIT SESSION ************************************************************************ Related Items of interest: -------------------------------------------------------------------------------- Subject: Speeding up long listing jobs -- a handy hint (from John Kennedy) I have discovered that JES2 writes SYSOUT at a block size of about 4K, no matter what is specified in the job. This means that jobs with huge printouts run much slower when directed to SYSOUT=x than when directed to UNIT=TESTDISK,DCB=(RECFM=VBA,LRECL=137,BLKSIZE=23476) (for example). BROWSEing a file created this way is also much faster than using IOF. Large listings that are never printed at all -- perhaps they are only used if there is an error in the job, perhaps they are converted to microfiche -- run faster and use fewer system resources this way than when using JES2. Even if the listing is just probably not printed, it can still be worthwhile to run the job this way and use the TSO PRINTOFF command or some other device to get it to the printer when and if desired. -------------------------------------------------------------------------------- Internal Aspects: 1. Options converted to capitals using SET ... = &SYSCAPS(&AOPTIONS) 2. Data changes checked using ISREDIT (DCHG) = DATA-CHANGED 3. PRINTOFF command used if possible 4. BATCH job generated if "BATCH" option or if PRINTOFF cannot be used.