Ralph Kaden/Poughkeepsie/Contr/IBM is out of the office.
I will be out of the office starting 02/27/2009 and will not return until 01/03/2011. My contract at IBM has ended effective February 27, 2009. For assistance with Allocation, SMF, or Scheduler, please contact Roy Delanoy, Dan Roth, Greg Dixon, Michele Dinelli, or Shirley Jubinski. To contact me for personal matters, please email me at rka...@hvc.rr.com or call me at (845) 471-1800. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Way... Back question...
snip Hmmm Sample Code is available only to customers who have a license to IBM OS/390 (Qualified Customers). If you do not have a license to OS/390, you may NOT download the documentation or samples. No mention of z/OS anywhere in that document unsnip I just clicked on contact z/OS on that page and submitted a request to change the OS/390 references to z/OS. Probably took less time to do that than to type the above. (Sorry. I don't usually criticize on forums like this, but I'm a firm believer in it's better to fix it than to complain about it.) Regards, Ralph Ralph Kaden z/OS (MVS) Level 2 Support - Allocation and Scheduler (Converter/Interpreter, Initiator/Terminator, ENF, SJF, SMF, SSI, SWA Mgr) T/ L: 8/295-4096 External: 845-435-4096 VM: S390VM.v$i01029MVS: PLPSC.v$i316 External email: [EMAIL PROTECTED] Internal email: Ralph Kaden/Poughkeepsie/Contr/[EMAIL PROTECTED] Chase, John [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 08/20/2008 08:03 AM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject Re: Way... Back question... -Original Message- From: IBM Mainframe Discussion List On Behalf Of Gary Green I guess that's a perfect example of ask, and yee shall receive. :) Thanks John! -Original Message- From: IBM Mainframe Discussion List On Behalf Of John Eells snip You might find this enlightening: http://www-03.ibm.com/systems/z/os/zos/installation/sampdisc.html Hmmm Sample Code is available only to customers who have a license to IBM OS/390 (Qualified Customers). If you do not have a license to OS/390, you may NOT download the documentation or samples. No mention of z/OS anywhere in that document -jc- -- 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 -- 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
Re: DASD Space Allocation
And just to add 1 more level of complexity, Guaranteed Space allocates the Primary request on each volume. Ralph Kaden z/OS (MVS) Level 2 Support - Allocation and Scheduler (Converter/Interpreter, Initiator/Terminator, ENF, SJF, SMF, SSI, SWA Mgr) T/ L: 8/295-4096 External: 845-435-4096 VM: S390VM.v$i01029MVS: PLPSC.v$i316 External email: [EMAIL PROTECTED] Internal email: Ralph Kaden/Poughkeepsie/Contr/[EMAIL PROTECTED] L D Owen [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 08/18/2008 07:32 PM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject Re: DASD Space Allocation I was surprised to read that on second and subsequent volumes, allocation is based on SECONDARY amounts. Just to confuse everything, VSAM rules are just the opposite. For VSAM datasets, the Primary is used on each subsequent volume for the initial extent (s) on that volume, and then Secondary for the remaining extents. So: Non-VSAM: Volume 1 (Primary, then Secondary), Volumes 2-n (Secondary) 16 Extents per volume, Max 59 volumes VSAM: Volume 1 (Primary, then Seconary), Volumes 2-n (Primary, then Secondary) Watch me be wrong about this one (123 Extents Maximum), no limit per volume If I'm wrong about the VSAM extents, please correct me. ...L -- 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 -- 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
Re: SMF Subtype 132 record
Try this: To determine who's writing an SMF rectype: SL SET,IF,A=SYNCSVCD,L=(IGC0008C,64),DATA=(1R?+5,EQ,xx), SD=(ALLNUC,ALLPSA,CSA,GRSQ,LPA,RGN,SQA,SUM,TRT),END where xx = the SMF record type in hex You should then be able to check SYSTRACE to see who issued the SVC 83 (x'svc53'). In the case in which it's a branch entry, you should be able to follow the registers back to see who made the call. Regards, Ralph Ralph Kaden z/OS (MVS) Level 2 Support - Allocation and Scheduler (Converter/Interpreter, Initiator/Terminator, ENF, SJF, SMF, SSI, SWA Mgr) T/ L: 8/295-4096 External: 845-435-4096 VM: S390VM.v$i01029MVS: PLPSC.v$i316 External email: [EMAIL PROTECTED] Internal email: Ralph Kaden/Poughkeepsie/Contr/[EMAIL PROTECTED] Laine, Rogers [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 08/15/2008 08:40 AM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject Re: SMF Subtype 132 record Scott, This is what I see when dumping this SMF record. I see nothing that jumps out at me that would indicate who this belongs to. d k¬ SYSBOPER004 \ d k¬ SYSBOPER007 A| d SYSBOPER007 A| d SYSBOPER004 \ d SYSBOPER004 \ d SYSBOPER007 A| -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Scott Barry Sent: Thursday, August 14, 2008 10:25 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: SMF Subtype 132 record On Thu, 14 Aug 2008 20:52:01 -0500, Rogers Laine [EMAIL PROTECTED] wrote: We are trying to research what software is producing SMF subtype of 132? We see these records being created every 1-2 minutes when a TSO user is log on the system. Any ideas? Dump a few of these records and look for an eye-catcher in the header, presuming you are looking for SMF type 132. You can use some DFSORT / COPY and IDCAMS PRINT utility commands - example JCL below: //S1 EXEC PGM=SORT,PARM=ABEND //SYSOUT DD SYSOUT=* //SORTIN DD DISP=SHR,DSN=_your_smf_input_file_ //SORTOUT DD DSN=amp;SORTTEMP, // UNIT=SYSDA,SPACE=(CYL,(10,10)), // DISP=(NEW,PASS) //SYSINDD * OPTION STOPAFT=5 SORT FIELDS=COPY INCLUDE COND=(6,1,BI,EQ,132) /* //DUMP EXEC PGM=IDCAMS //IN1 DD DISP=(OLD,DELETE),DSN=amp;SORTTEMP //SYSPRINT DD SYSOUT=* //SYSINDD * PRINT INFILE(IN1) DUMP /* Scott Barry SBBWorks, Inc. -- 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 Confidentiality Notice: This E-Mail transmission (and/or the documents accompanying it) may contain information belonging to the sender which is confidential, privileged and/or exempt from disclosure under applicable law. The information is intended only for the use of the individual(s) or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this E-Mail transmission in error, please immediately notify us by return E-Mail or telephone to arrange for return of its contents including any documents. -- 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 -- 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
Re: SMF Subtype 132 record
In IPCS option 6, enter SYSTRACE and do a find for ' 53 ' That should take you to the SVC 83 entry, but there could, conceivably, be multiple SVC 83 entries, so you'll need to check Reg1 to be sure it's pointing to a type132 record. Regs in SYSTRACE follow the PSW and are in the sequence R15, R0, and R1. If you need more help than this, please see if someone can give you a short lesson in the IPCS commands you'll need or take an IPCS course. Regards, Ralph Ralph Kaden z/OS (MVS) Level 2 Support - Allocation and Scheduler (Converter/Interpreter, Initiator/Terminator, ENF, SJF, SMF, SSI, SWA Mgr) T/ L: 8/295-4096 External: 845-435-4096 VM: S390VM.v$i01029MVS: PLPSC.v$i316 External email: [EMAIL PROTECTED] Internal email: Ralph Kaden/Poughkeepsie/Contr/[EMAIL PROTECTED] Laine, Rogers [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 08/15/2008 01:37 PM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject Re: SMF Subtype 132 record Ralph, How would I go about checking SYSTRACE? Rogers -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ralph Kaden Sent: Friday, August 15, 2008 9:56 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: SMF Subtype 132 record Try this: To determine who's writing an SMF rectype: SL SET,IF,A=SYNCSVCD,L=(IGC0008C,64),DATA=(1R?+5,EQ,xx), SD=(ALLNUC,ALLPSA,CSA,GRSQ,LPA,RGN,SQA,SUM,TRT),END where xx = the SMF record type in hex You should then be able to check SYSTRACE to see who issued the SVC 83 (x'svc53'). In the case in which it's a branch entry, you should be able to follow the registers back to see who made the call. Regards, Ralph Ralph Kaden z/OS (MVS) Level 2 Support - Allocation and Scheduler (Converter/Interpreter, Initiator/Terminator, ENF, SJF, SMF, SSI, SWA Mgr) T/ L: 8/295-4096 External: 845-435-4096 VM: S390VM.v$i01029MVS: PLPSC.v$i316 External email: [EMAIL PROTECTED] Internal email: Ralph Kaden/Poughkeepsie/Contr/[EMAIL PROTECTED] Laine, Rogers [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 08/15/2008 08:40 AM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject Re: SMF Subtype 132 record Scott, This is what I see when dumping this SMF record. I see nothing that jumps out at me that would indicate who this belongs to. d k¬ SYSBOPER004 \ d k¬ SYSBOPER007 A| d SYSBOPER007 A| d SYSBOPER004 \ d SYSBOPER004 \ d SYSBOPER007 A| -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Scott Barry Sent: Thursday, August 14, 2008 10:25 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: SMF Subtype 132 record On Thu, 14 Aug 2008 20:52:01 -0500, Rogers Laine [EMAIL PROTECTED] wrote: We are trying to research what software is producing SMF subtype of 132? We see these records being created every 1-2 minutes when a TSO user is log on the system. Any ideas? Dump a few of these records and look for an eye-catcher in the header, presuming you are looking for SMF type 132. You can use some DFSORT / COPY and IDCAMS PRINT utility commands - example JCL below: //S1 EXEC PGM=SORT,PARM=ABEND //SYSOUT DD SYSOUT=* //SORTIN DD DISP=SHR,DSN=_your_smf_input_file_ //SORTOUT DD DSN=amp;SORTTEMP, // UNIT=SYSDA,SPACE=(CYL,(10,10)), // DISP=(NEW,PASS) //SYSINDD * OPTION STOPAFT=5 SORT FIELDS=COPY INCLUDE COND=(6,1,BI,EQ,132) /* //DUMP EXEC PGM=IDCAMS //IN1 DD DISP=(OLD,DELETE),DSN=amp;SORTTEMP //SYSPRINT DD SYSOUT=* //SYSINDD * PRINT INFILE(IN1) DUMP /* Scott Barry SBBWorks, Inc. -- 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 Confidentiality Notice: This E-Mail transmission (and/or the documents accompanying it) may contain information belonging to the sender which is confidential, privileged and/or exempt from disclosure under applicable law. The information is intended only for the use of the individual(s) or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this E-Mail transmission in error
Re: DASD Space Allocation
I'm not sure I understand what you mean; if the default volume is a 3380 and the allocation is satisfied on a 3390, a larger volume, how would the space allocation be increased for the larger 3390. Found the following info in DFSMSdfp Storage Administration Reference (SC26-4920-01) in Chapter 3 (Creating the Base Configuration), Topic 3.2 (Defining the Base Configuration), subtopic 3.2.3 (Specifying the Default Device Geometry): When allocating space for a new data set on DASD, SMS converts all space requests in tracks (TRK) or cylinders (CYL) into requests for space in KB or MB. If a generic device type such as the 3380 is specified, SMS uses the device geometry for that generic device to convert tracks or cylinders into KB or MB. If an esoteric device type such as SYSDA or no UNIT is specified, SMS uses the default device geometry to convert tracks and cylinders into KB or MB. If the users in your installations specify space in tracks or cylinder units, and they specify an esoteric UNIT or no UNIT you must specify a default device geometry prior to converting these allocations to system-managed data sets. . After SMS converts space requests to KB or MB, the space values are passed to the ACS routines. The values are later used to determine the number of tracks or cylinders to allocate for the data set. The default device geometry does not apply to objects or data sets allocated on tape. . There is only one Default Device Geometry for the entire SMS complex. Default Device Geometry is an installations' definition of how much space is represented by a TRK or a CYL when an esoteric unit or no unit is specified. . The device geometry for a 3380 is 47476 bytes/track, 15 tracks/cylinder. The device geometry for a 3390 is 56664 bytes/track, 15 tracks/cylinder. . It is up to each installation to decide what values to use. From MVS Storage Management Library: Managing Data Sets (SC26-4408): Using Default Device Geometry: In an SMS environment, you use default device geometry to convert track and cylinder allocation requests to bytes. This can be used for both SMS- and non-SMS-managed data sets. Using default device geometry isolates users from actual physical devices; the amount of allocated space will be consistent, regardless of which device is used. If you specify a default device geometry, it will be used for a new data set allocation as follows: - When the data set is SMS-managed and a generic UNIT has not been explicitly specified. - When an esoteric UNIT name is specified for a non-SMS-managed data set. - When no UNIT name is specified for a non-SMS-managed data set, and the default unit is esoteric. If the default unit is generic (e.g., 3390), then the device geometry of this unit is used for space calculations. Ralph Kaden z/OS (MVS) Level 2 Support - Allocation and Scheduler (Converter/Interpreter, Initiator/Terminator, ENF, SJF, SMF, SSI, SWA Mgr) T/ L: 8/295-4096 External: 845-435-4096 VM: S390VM.v$i01029MVS: PLPSC.v$i316 External email: [EMAIL PROTECTED] Internal email: Ralph Kaden/Poughkeepsie/Contr/[EMAIL PROTECTED] William F Besnier [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 08/14/2008 10:07 PM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject Re: DASD Space Allocation I'm not sure I understand what you mean; if the default volume is a 3380 and the allocation is satisfied on a 3390, a larger volume, how would the space allocation be increased for the larger 3390. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Tom Marchant Sent: Thursday, August 14, 2008 6:05 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: DASD Space Allocation On Thu, 14 Aug 2008 17:22:35 -0400, William F Besnier wrote: Situation came up on a client site where they received a very large file, 2.988 million records, and allocate the file size at (cyl,(2500,100)) with a unit parameter of sysda,10; the file is received across 2 volumes in 20 extents totaling 4,331 cylinders. I am not concerned about the extents, what I don't understand is the space allocation. If SMS is configured with a default volume specified as 3380 and the space allocation is satisfied on a 3390, the amount allocated will be adjusted to account for the larger cylinders on a 3390. -- Tom Marchant -- 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
Re: Historical question -- GDG allocation
From Info APAR II08285: NOTE: Starting in z/OS 1.6 (HBB7709) non-SMS GDGs do NOT require a model DSCB. If DCB=dsname is not provided, Allocation will look for a model DSCB with the GDG base name. If not found, Allocation will NOT fail the job, but will assume that the DCB information will be provided from other sources at OPEN time. See PDDB item BDC33660 for the documentation changes to the JCL User's Guide. (Note that most of the information in the following Reader's Comment Form (RCF) never made it into the manuals, so I have resubmitted the RCF.) From PDDB item BDC33660: Here is the revised documentation, which I am submitting as an RCF: Ref: Title: z/OS V1R6.0 MVS JCL User's Guide Document Number: SA22-7598-04 Re1: APPENDIX1.2.2.3 -- Defining Attributes for Non-SMS-Managed Generation Data Sets Remove the following: Another requirement (in addition to a GDG base entry) for a GDG is a data set label. The system uses this label to refer to DCB attributes and the EXPDT value when you create a new generation data set. Add the following in its place: Beginning in z/OS 1.6, it is no longer a requirement that a data set label exist in order to create a generation data set. It is now sufficient simply to supply DCB attributes in the same manner as is done for non-GDG data sets. Under DCB attributes can be supplied in one of the following ways:, change the word the in point # 3 to the word another. That is, Remove the following: 3. Specify LIKE= or REFDD= to use attributes from the DD statement or specify DATACLAS to use attributes specified for the data class. Add the following in its place: 3. Specify LIKE= or REFDD= to use attributes from another DD statement or specify DATACLAS to use attributes specified for the data class. Add the following as # 4: 4. Specify DCB attributes on the DD statement or on the DCB in the program which creates the data set. Under Attributes can be supplied before you catalog a generation, when you catalog it, or at both times, as follows: change the word either in point # 2 to the word any. That is, Remove the following: 2. You do not need to create a model data set label if either of the following is true: Add the following in its place: 2. You do not need to create a model data set label if any of the following is true: Add the following as letter 'c' under that point # 2: c. The DCB attributes are specified on the DD statement or on the DCB in the program which creates the data set. Re2: APPENDIX1.2.2.4 -- Creating a Non-SMS-Managed Generation Data Set In the first sentence of the last paragraph change the word must to the word may. That is, Remove the following: If a model data set label does not exist, you must use the label for a cataloged data set. Add the following in its place: If a model data set label does not exist, you may use the label for a cataloged data set. Add the following as the final sentence of that last paragraph: Alternatively, simply code DCB=(list of attributes) and supply all of the desired DCB attributes. Ralph Kaden z/OS (MVS) Level 2 Support - Allocation and Scheduler (Converter/Interpreter, Initiator/Terminator, ENF, SJF, SMF, SSI, SWA Mgr) T/ L: 8/295-4096 External: 845-435-4096 VM: S390VM.v$i01029MVS: PLPSC.v$i316 External email: [EMAIL PROTECTED] Internal email: Ralph Kaden/Poughkeepsie/Contr/[EMAIL PROTECTED] Rick Fochtman [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 08/12/2008 12:04 PM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject Re: Historical question -- GDG allocation -snip--- The model was required with operating systems MFT amd MVT. The model requirement went away when IDCAMS became available. I don't think so! I've only worked with MVS up, and I learned the hard way about models being required. unsnip- As far back as I can remember, there were always two ways to provide a model. 1. Create a zero-space dataset, with the appropriate characteristics, of the same name as the Generation Index, on the same volume as the catalog containing the Generation index. 2. use the DCB=dsname construct, with appropriate characteristics, on the allocating DD statement. Many shops use this approach, pointing to a single model DSCB that was the same name for everyone. So, some sort of model is required, but not necessarily a model named the same as the generation index. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET
Re: zOs 1.7 JCL concatenation question ?
From the JCL reference manual under the DDNAME parameter: Location of DD Statements for Concatenated Data Sets To concatenate data sets to a data set defined with a DDNAME parameter, the unnamed DD statements must follow the DD statement that contains the DDNAME parameter, not the referenced DD statement that defines the data set. In this sequence, the unnamed DD * follows the CMWKF02 DD statement and so is not picked up as part of the concatenation: 80 XXCMSYNIN DD DDNAME=SYSIN 81 //CMWKF02 DD DSN=SYS3.APRCB.PROD.UNDUP(+1), //DISP=(NEW,PASS,DELETE), //UNIT=SYSDA,SPACE=(TRK,(20,2),RLSE), //DCB=SYS3.PATTERN.RECL0020 82 //SYSINDD DSN=SYS3.ANATP.LOGON,DISP=SHR 83 // DD * INPUT /* In this sequence, the unnamed DD * follows the CMSYNIN DD statement and so is picked up as part of the concatenation: 80 XXCMSYNIN DD DDNAME=SYSIN 81 //SYSINDD DSN=SYS3.ANATP.LOGON,DISP=SHR 82 // DD * INPUT /* 83 //CMWKF02 DD DSN=SYS3.APRCB.PROD.UNDUP(+1), //DISP=(NEW,PASS,DELETE), //UNIT=SYSDA,SPACE=(TRK,(20,2),RLSE), //DCB=HWG.PATTERN.RECL0020 Regards, Ralph Ralph Kaden z/OS (MVS) Level 2 Support - Allocation and Scheduler (Converter/Interpreter, Initiator/Terminator, ENF, SJF, SMF, SSI, SWA Mgr) T/ L: 8/295-4096 External: 845-435-4096 VM: S390VM.v$i01029MVS: PLPSC.v$i316 External email: [EMAIL PROTECTED] Internal email: Ralph Kaden/Poughkeepsie/Contr/[EMAIL PROTECTED] Anton Britz [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 08/12/2008 03:41 PM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject zOs 1.7 JCL concatenation question ? Hi, Why do we not see the concatenated SYSIN when we code the JCL the following way : 80 XXCMSYNIN DD DDNAME=SYSIN 81 //CMWKF02 DD DSN=SYS3.APRCB.PROD.UNDUP(+1), //DISP=(NEW,PASS,DELETE), //UNIT=SYSDA,SPACE=(TRK,(20,2),RLSE), //DCB=SYS3.PATTERN.RECL0020 82 //SYSINDD DSN=SYS3.ANATP.LOGON,DISP=SHR 83 // DD * INPUT /* But if we code it this way, the second SYSIN concatenation is seen by the program : 80 XXCMSYNIN DD DDNAME=SYSIN 81 //SYSINDD DSN=SYS3.ANATP.LOGON,DISP=SHR 82 // DD * INPUT /* 83 //CMWKF02 DD DSN=SYS3.APRCB.PROD.UNDUP(+1), //DISP=(NEW,PASS,DELETE), //UNIT=SYSDA,SPACE=(TRK,(20,2),RLSE), //DCB=HWG.PATTERN.RECL0020 -- 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 -- 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
Re: Converting / Copying a dataset from RECFM=UA to RECFM=FB
How about taking advantage of the thing which has gotten so many installations in trouble over the years and opening the dataset for output (DISP=MOD) specifying on the output DD stmt the DCB parameters you want the dataset to have? Since IEBGENER won't allow you to change RECFM or LRECL, you'll have to have a small program that does nothing more than: OPEN (dcbname,OUTPUT) CLOSE dcbname Ralph Kaden z/OS (MVS) Level 2 Support - Allocation and Scheduler (Converter/Interpreter, Initiator/Terminator, ENF, SJF, SMF, SSI, SWA Mgr) T/ L: 8/295-4096 External: 845-435-4096 VM: S390VM.v$i01029MVS: PLPSC.v$i316 External email: [EMAIL PROTECTED] Internal email: Ralph Kaden/Poughkeepsie/Contr/[EMAIL PROTECTED] Rahul Karsija [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 08/07/2008 10:29 AM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject Re: Converting / Copying a dataset from RECFM=UA to RECFM=FB Hi My original program sends out data to the spool and then the report is printed. My task is to send the data to a dataset, and then email this dataset. The email program (IKJEFT1A) doesn't support such datasets and requires FB or VB as input I had also created the dataset using IEFBR14 - //STEP01 EXEC PGM=IEFBR14 //DD1 DD DSN=MY.DATASET, //DISP=(NEW,CATLG,DELETE),SPACE=(CYL,(125,50),RLSE), //DCB=(RECFM=FB,LRECL=133,BLKSIZE=0) //SYSPRINT DD SYSOUT=* //SYSINDD DUMMY //SYSUDUMP DD SYSOUT=* Then, I used this dataset in my original program, with DISP=OLD. The program converts it to RECFM=UA (undefined length record) while writing out data to it. Regards Rahul Karsija On Thu, Aug 7, 2008 at 6:38 PM, Chris Mason [EMAIL PROTECTED] wrote: Rahul I'm a bit rusty on theses matters since I don't have systems to play with these days. However, if I wanted to set up an existing data set with DCB parameters other than those currently assigned, I'd try the following: First of all I'd be using IEBGENER as the program. Then I'd define the input data set with DCB parameters which overrode the stored DCB parameters with the DCB parameters I wanted the program to adopt and hence to try to use. Naturally I'd define the output data set with the same DCB parameters so that those became the stored DCB parameters for the new data set. I could guess that the records in the data set are 133 bytes long, that there is one record per block and that the records are print lines which have an ASA - if I remember correctly what A means - character as the first character, the carriage control character. I'm ignoring the defined stored block size of 101 which looks spurious. //... JOB ... //GENER EXEC PGM=IEBGENER //SYSUT1 DD DSN=input,DCB= (BLKSIZE=133,LRECL=133,RECFM=FBA),DISP=OLD //SYSUT2 DD DSN=output,DCB=(BLKSIZE=133,LRECL=133,RECFM=FBA),DISP= (NEW,KEEP) //SYSIN DD DUMMY Chris Mason ably assisted by John Austin On Thu, 7 Aug 2008 15:36:53 +0530, Rahul Karsija [EMAIL PROTECTED] wrote: Hi I need to convert a dataset from RECFM=UA to RECFM=FB. I tried to copy it using IDCAMS but was unsuccessful. I also wrote a small program to read the input records and then write them to output file but that did not work either. Using SORT with OPTION COPY was also not helpful, got message - ICE043A 3 INVALID DATA SET ATTRIBUTES SPECIFIED SORTIN RECFM Given below are the parameters of the input file - Organization . . . : PS Record format . . . : UA Record length . . . : 133 Block size . . . . : 101 1st extent cylinders: 1 Secondary cylinders : 50 Have also tried using IBM TRSMAIN (first PACK and then UNPACK) but that also creates the final output file as UA. Please help me. Thanks Regards Rahul Karsija -- 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 -- 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 -- 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
Re: SYS PROG
John, you sent this reply to the entire list. If you don't want people to know you're looking, perhaps you should respond to Jim directly. Just a thought. (On the other hand, if you're trying tofrighten your boss into giving you a raise, maybe this is the way to do it.) Regards, Ralph Ralph Kaden z/OS (MVS) Level 2 Support - Allocation and Scheduler (Converter/Interpreter, Initiator/Terminator, ENF, SJF, SMF, SSI, SWA Mgr) T/ L: 8/295-4096 External: 845-435-4096 VM: S390VM.v$i01029MVS: PLPSC.v$i316 External email: [EMAIL PROTECTED] Internal email: Ralph Kaden/Poughkeepsie/Contr/[EMAIL PROTECTED] Eatherly, John D [EQ] [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 07/30/2008 08:37 PM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject Re: SYS PROG My wife's family is from up there. Most of my experience is support of 20+ images. The last year I have been doing z/Linux and a little z/VM. We are running RedHat right now. I am the primary person on z/OS and z/Linux maintenance. I do quarterly on z/Linux and monthly on z/OS. Does this sound like I might have a chance if I am interested? I have been working as a SYSPROG since 1989 for one company. Thanks John Eatherly 972.254.5441 972.830.3627 From: Marshall, James D [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 30, 2008 7:26 PM To: Eatherly, John D [EQ] Subject: RE: SYS PROG Not sure what you mean permanently. The period remaining on this contract is another three years renewing on Friday. The company has had it for the last 20+ years competing every 5 years. There is no reason to believe in 3 years they would not win it again. At times we are bleeding edge only because of need. IBM has come to us because we were doing things before they were. We have a great relationship with IBM even though in the DC area they label me the cranky old guy. I was around in DC in the 1970s and early 80s where I built the Pentagon, while in the Air Force, into an almost all IBM shop from the biggest Honeywell site in the world. If you are talking about coming into OPM and they looking around to apply for a Federal job either here or elsewhere in Uncle Sugar's many operations, that is the beauty of being a civilian (unlike the military). My position is the only Gov IBM SYSPROG and I can not touch the systems. I act as the Coach and not a Player Coach. My job is to keep the techies focused on the technology, I deflect the politics, and get us the best equipment and tools as I can. Could have retired (again) two years ago, and it is too much fun to stop now. Not sure if I answered your question. Oh yes, the contractor is Compuware Services. jim Jim Marshall, Software Engineer US Office of Personnel Management 1900 E Street NW - Room BH04 Washington DC 20415 (w) 202-606-1261 (f) 202-606-2092 -Original Message- From: Eatherly, John D [EQ] [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 30, 2008 8:06 PM To: Marshall, James D Subject: SYS PROG Jim, I was just wondering if it has any chance of becoming a permanent job? I have a job here and I have a chance of working remotely. But if that does not work out I would definitely be looking in the area. I have been doing this a quite a while. Thanks. John Eatherly System Z Development and Support EMBARQ Infrastructure Services Voice: 972.254.5441 | Cell: 972.897.6883 | Alt Work Number: 972.830.3627 Email: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] -- 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 -- 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
