Re: DFSORT V1R5 - ICE751I and ICE752I
Hi, Thanks everybody for the feedback. Somebody else was working on the problem today because I actually tried to get some sleep. So I forwarded all these postings to him and Dave , we would sent you the FULL output. Summary: I really would suggest that we make "IBM Software" more user friendly : a) Why not print a warning message to the User indicating that any SORTWK99 dataset will only use ONE volume b) Why not print a message to the user stating that the Memory allocation is too small. c) Why do we still have a limit in zOS with regards the Primary Cylinder allocation. Apparently it's 4000 Cylinders and I found this out the hard way last night. d) When abending, please tell me more. Currently you print messages that says "For the IBM support rep." I thought IBM stopped doing this in the 80's You do print how many records are about to be sorted, so you are half way there ( Don't take me halfway... I want it all and I want it now ) Anton _David Betten wrote: I already answered Anton in another post but I wanted to respond to this and make clear that DFSORT work files cannot span multiple volumes. If you coded UNIT=(SYSDA,10) on a SORTWKnn DD statement, DFSORT would still use only 1 volume for each SORTWK data set. Have a nice day, Dave Betten DFSORT Development, Performance Lead IBM Corporation email: [EMAIL PROTECTED] 1-240-715-4655, tie line 268-1499 DFSORT/MVSontheweb at http://www.ibm.com/storage/dfsort/ IBM Mainframe Discussion List wrote on 07/01/2007 02:10:23 PM: If necessary and the file is SMS managed add a volume parameter to the UNIT parameter, eg. UNIT=(SYSDA,10). It doesn't have to be SMS managed for the volume parameter to work. - Too busy driving to stop for gas! -- 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: DFSORT V1R5 - ICE751I and ICE752I
I already answered Anton in another post but I wanted to respond to this and make clear that DFSORT work files cannot span multiple volumes. If you coded UNIT=(SYSDA,10) on a SORTWKnn DD statement, DFSORT would still use only 1 volume for each SORTWK data set. Have a nice day, Dave Betten DFSORT Development, Performance Lead IBM Corporation email: [EMAIL PROTECTED] 1-240-715-4655, tie line 268-1499 DFSORT/MVSontheweb at http://www.ibm.com/storage/dfsort/ IBM Mainframe Discussion List wrote on 07/01/2007 02:10:23 PM: > >If necessary and the file is SMS managed add a volume parameter to > the UNIT parameter, eg. UNIT=(SYSDA,10). > > It doesn't have to be SMS managed for the volume parameter to work. > - > Too busy driving to stop for gas! > > -- > 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: DFSORT V1R5 - ICE751I and ICE752I
Anton Britz wrote: //SORTWK01 DD SPACE=(CYL,(4000,500)),UNIT=TMPDA, //DCB=(LRECL=2000,BLKSIZE=28000,RECFM=FB) You may want to change your block size to 0 and let the system determine the best size. Your size of 28000 is actually too big for 1/2 track blocking. The largest block size you have to get 1/2 track is 27,998. With 28000 you get 14 records per block, but only 1 block per track. For a record size of 2,000 the system determind to use 18,000, which gets you 9 records per block, but you can get 3 blocks per track which yields 27 records per track. Almost twice as much as you are getting!! Which mean you need about 1/2 of the sort work space you are allocating and my guess is you will cut your run time down as you are getting more records per I/O. -- 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: DFSORT V1R5 - ICE751I and ICE752I
And you used publicly mounted DASD. And that is the way it has always worked. Private volumes would need a vol ser list supplied. From: Ted MacNEIL [mailto:[EMAIL PROTECTED] Sent: Sun 7/1/2007 5:59 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: DFSORT V1R5 - ICE751I and ICE752I >No, but you would then have to supply the volume serial list or use volumes >mounted as Storage. Since when? I used UNIT=(SYSDA,nn) years ago! (1981). The point is that it worked before SMS. - Too busy driving to stop for gas! -- 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
OT Funny IT Movie
This link is good for 7 days from today 07/01/2007 http://download.yousendit.com/EBF5254746200B39 This is a funny movie (In Dutch if I am not mistaken) but it transcends language. -- 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: DFSORT V1R5 - ICE751I and ICE752I
Anton, If you send the entire sysout directly to my email ([EMAIL PROTECTED]) I can probably diagnose your abend easier.But at first glance, I suspect the very limited main storage you are allowing the sort (524288) is causing an intermediate merge and that's when you are running out of sortwork space. But again, I'd need to see the entire sysout to be sure. Dave Betten DFSORT Development, Performance Lead IBM Corporation email: [EMAIL PROTECTED] DFSORT/MVSontheweb at http://www.ibm.com/storage/dfsort/ IBM Mainframe Discussion List wrote on 07/01/2007 12:38:15 PM: > Yes... thanks for all the feedback and my initial posting was more out > of frustration with DFSORT and SMS. > > So here comes more detail : > > The Scene of the crime : > > Input Dataset contains 4,826,605 records of 2000 bytes each. > > The Sort Control Cards : > > ICE143I 0 BLOCKSET SORT TECHNIQUE SELECTED > ICE250I 0 VISIT http://www.ibm.com/storage/dfsort FOR DFSORT PAPERS, > EXAMPLES AN > ICE000I 1 - CONTROL STATEMENTS FOR 5694-A01, Z/OS DFSORT V1R5 - 03:58 ON > SUN JUL > SORT FIELDS=(49,6,A,59,8,A,91,6,A,99,8,A,81,2,A, > 97,2,A,1947,3,A,55,4,A,1950,2,A),FORMAT=CH > ICE201I E RECORD TYPE IS F - DATA STARTS IN POSITION 1 > ICE751I 0 C5-K90007 C6-K90007 C7-K9 C8-K90007 E4-K90007 C9-BASE > E5-K14794 > ICE193I 0 ICEAM1 ENVIRONMENT IN EFFECT - ICEAM1 INSTALLATION MODULE SELECTED > ICE088I 1 HWLK221A.STEP220 .SORT, INPUT LRECL = 2000, BLKSIZE = > 4000, TYPE = > ICE092I 0 MAIN STORAGE = (350,524288,524288) > ICE156I 0 MAIN STORAGE ABOVE 16MB = (458304,458304) > ICE127I 0 OPTIONS: OVFLO=RC0 ,PAD=RC0 ,TRUNC=RC0 > ,SPANINC=RC16,VLSCMP=N,SZERO=Y, > ICE128I 0 OPTIONS: > SIZE=524288,MAXLIM=2097152,MINLIM=524288,EQUALS=Y,LIST=Y,ERET > ICE129I 0 OPTIONS: VIO=N,RESDNT=ALL ,SMF=NO > ,WRKSEC=Y,OUTSEC=Y,VERIFY=Y,CHALT= > ICE130I 0 OPTIONS: RESALL=0,RESINV=0,SVC=109 > ,CHECK=Y,WRKREL=Y,OUTREL=Y,CKPT=N,S > ICE131I 0 OPTIONS: > TMAXLIM=5242880,ARESALL=0,ARESINV=0,OVERRGN=0,CINV=Y,CFW=Y,DS > ICE132I 0 OPTIONS: VLSHRT=N,ZDPRINT=Y,IEXIT=N,TEXIT=N,LISTX=N,EFS=NONE >,EXITC > ICE133I 0 OPTIONS: HIPRMAX=OPTIMAL,DSPSIZE=MAX > ,ODMAXBF=0,SOLRF=Y,VLLONG=N,VSAMI > ICE235I 0 OPTIONS: NULLOUT=RC0 > ICE084I 0 EXCP ACCESS METHOD USED FOR SORTOUT > ICE084I 0 EXCP ACCESS METHOD USED FOR SORTIN > ICE750I 0 DC 0 TC 9653212000 CS DSVVV KSZ 45 VSZ 45 > > Sort Step JCL : > > XXSORT PROC PROG=ICEMAN, > XXWTR1='*', > XXCYL=15, > XXDEVTYP=TMPDA, > XXRGIN=6M > XXSORT EXEC PGM=&PROG,REGION=&RGIN,PARM='SIZE=350' > IEFC653I SUBSTITUTION JCL - PGM=ICEMAN,REGION=6M,PARM='SIZE=350' > XXSYSOUT DD SYSOUT=&WTR1 > IEFC653I SUBSTITUTION JCL - SYSOUT=* > XXSYSOUX DD SYSOUT=&WTR1 > IEFC653I SUBSTITUTION JCL - SYSOUT=* > XXSYSLMOD DD SPACE=(3600,(20,20,1)),DSN=&&GOSET, > XX UNIT=&DEVTYP > IEFC653I SUBSTITUTION JCL - SPACE=(3600,(20,20,1)),DSN=&&GOSET,UNIT=TMPDA > XXSYSLIN DD SPACE=(80,(10,10,)),DSN=&&LOADSET, > XX UNIT=&DEVTYP > IEFC653I SUBSTITUTION JCL - SPACE=(80,(10,10,)),DSN=&&LOADSET,UNIT=TMPDA > XXSYSUT1 DD SPACE=(1000,(60,20)),UNIT=&DEVTYP > IEFC653I SUBSTITUTION JCL - SPACE=(1000,(60,20)),UNIT=TMPDA > //SORTWK01 DD SPACE=(CYL,(4000,500)),UNIT=TMPDA, > //DCB=(LRECL=2000,BLKSIZE=28000,RECFM=FB) > //SORTWK02 DD SPACE=(CYL,(4000,500)),UNIT=TMPDA, > //DCB=(LRECL=2000,BLKSIZE=28000,RECFM=FB) > X/SORTWK02 DD SPACE=(CYL,(&CYL,&CYL)),UNIT=&DEVTYP > IEFC653I SUBSTITUTION JCL - SPACE=(CYL,(750,750)),UNIT=TMPDA > //SORTWK03 DD SPACE=(CYL,(4000,500)),UNIT=TMPDA, > //DCB=(LRECL=2000,BLKSIZE=28000,RECFM=FB) > X/SORTWK03 DD SPACE=(CYL,(&CYL,&CYL)),UNIT=&DEVTYP > IEFC653I SUBSTITUTION JCL - SPACE=(CYL,(750,750)),UNIT=TMPDA > //SORTWK04 DD SPACE=(CYL,(2000,500)),UNIT=TMPDA, > //DCB=(LRECL=2000,BLKSIZE=28000,RECFM=FB) > X/SORTWK04 DD SPACE=(CYL,(&CYL,&CYL)),UNIT=&DEVTYP > IEFC653I SUBSTITUTION JCL - SPACE=(CYL,(750,750)),UNIT=TMPDA > //SORTWK05 DD SPACE=(CYL,(3000,500)),UNIT=TMPDA, > //DCB=(LRECL=2000,BLKSIZE=28000,RECFM=FB) > X/SORTWK05 DD SPACE=(CYL,(&CYL,&CYL)),UNIT=&DEVTYP > IEFC653I SUBSTITUTION JCL - SPACE=(CYL,(750,750)),UNIT=TMPDA > //SORTWK06 DD SPACE=(CYL,(3000,500)),UNIT=TMPDA, > //DCB=(LRECL=2000,BLKSIZE=28000,RECFM=FB) > X/SORTWK06 DD SPACE=(CYL,(&CYL,&CYL)),UNIT=&DEVTYP > IEFC653I SUBSTITUTION JCL - SPACE=(CYL,(750,750)),UNIT=TMPDA > //SORTWK07 DD SPACE=(CYL,(1000,500)),UNIT=TMPDA, > //DCB=(LRECL=2000,BLKSIZE=28000,RECFM=FB) > X/SORTWK07 DD SPACE=(CYL,(&CYL,&CYL)),UNIT=&DEVTYP > //* > IEFC653I SUBSTITUTION JCL - SPACE=(CYL,(750,750)),UNIT=TMPDA > //SYSPRINT DD SYSOUT=* > //SORTIN DD DSN=HWL.HWLK228P.ARCHIVE,DISP=OLD > //SORTOUT DD DSN=HWL.HWLKSORT.HWLK228P, > //DISP=(NEW,PASS,DELETE), > //STORCLAS=LRGETAPE,UNIT=3490, > //DCB=(HWG.PATTERN.RECL2000,BLKSIZE=0) > //SYSINDD * > //* > > The WORK packs available : >
Re: Background of disabling ISVs via JCL
(a new week, a slow start, ) Umm, DCBOFLGS (or DCBOFLG) bit 3 (x'10') is the "successful OPEN" indicator: DCBOFLGS DSBL1FLAGS USED BY OPEN ROUTINE DCBOFLWR EQU DCBBIT0IF ZERO, LAST I/O OPERATION WAS READ OR * POINT. IF ONE, LAST I/O OPERATION WAS * WRITE. DCBOFIOD EQU DCBBIT0DATA SET IS BEING OPENED FOR INPUT OR * OUTPUT (BDAM) DCBOFLRB EQU DCBBIT1LAST I/O OPERATION WAS IN READ BACKWARD * MODE DCBOFEOV EQU DCBBIT2SET TO 1 BY EOV WHEN IT CALLS CLOSE * ROUTINE FOR CONCATENATION OF DATA SETS * WITH UNLIKE ATTRIBUTES DCBOFOPN EQU DCBBIT3AN OPEN HAS BEEN SUCCESSFULLY COMPLETED ..so that code fragment should read: IF (LTR,R15,R15,Z),OR,(TM,DCBOFLG,X'10',O) WTO 'OPEN OK' ..or better still, using the DCBD mapping macro: IF (LTR,R15,R15,Z),OR,(TM,DCBOFLG,DCBOFOPN,O) WTO 'OPEN OK' At 11:42 PM 7/1/2007, you wrote: try to OPEN a particular DD-name and then examine the appropriate bit - I seem to remember DCBOFLG. If the OPEN succeeded, take action A; if the OPEN failed, take the binary alternative action B. That way it didn't matter whether or not the DD-statement was a DUMMY but it may as well be. IF (LTR,R15,R15,Z),OR,(TM,DCBOFLG,X'80',O) WTO 'OPEN OK' -- 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: Utility to print tracks
Clark Morris wrote on 2007-07-01 18:58:35: > >FDRDSF can print any track on a volume, by cylinder and head (or range) > Of course this facility should be highly restricted since this > probably bypasses all dataset access checking. This comment would > apply to the other programs mentioned as well. Indicting FDR on the basis of a "probably bypasses" premise is not fair. If the program does not do that gratuitously, restricting access can diminish productivity in your installation. There is no reason to apply restrictions to SPZAP. It makes no attempt to circumvent normal restrictions that apply to the data sets referenced by its SYSLIB ddname. Blindly restricting access to a few programs is false security. Bob Wright - MVS Service Aids -- 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
Looking for sample TRANSMIT output files
XMITMGR is nice but has some limitations. The version I downloaded off the www.cbttape.org website adds a blank line to every member I extract. If the member was itself the output from a transmit command, it can not be received. It was not working for the PDSE I transmitted. I believe the mirrored page states his goal was to work with the cbttape files. They are always PDS datasets. I previously had some PC based REXX code that would receive from a downloaded transmit file. It broke several years ago, maybe because I was using PDSE datasets. I just spent many hours (days) working on it and switched from IBM PC DOS 7.1 REXX to Open Object REXX to get it to work again. It may not be pretty, but I was able to receive members from a LOADLIB and using SPFPC get the same look under browse as I get from ISPF. I can handle a PDS, PDSE, and sequential dataset. I have lots of 3390 based transmit files to test with. I plan to include it in FILE760 on the CBTTAPE in August. The real value I see in it, is viewable source in how to handle the internal file formats. Major portions are already documented in the IBM manuals. I have some 'would like to do' changes someday. Including some kind of interface. Does anybody have 3330 (or even older), 3350, 3375, or 3380 transmit files with something more than a three record member in it? How about from a user defined 3390 size DISK (not 3390-1,3,9,27)? -- 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: Background of disabling ISVs via JCL
On Sun, 1 Jul 2007 15:42:42 +0200, Chris Mason <[EMAIL PROTECTED]> wrote: >Eric > >It's strange I never came across this sort of "switch" technique - but I've >been rather out of it for the last few years. > >There were some earlier posts which suggested - to me anyhow - that all the >program did was try to OPEN a particular DD-name and then examine the >appropriate bit - I seem to remember DCBOFLG. If the OPEN succeeded, take >action A; if the OPEN failed, take the binary alternative action B. That way >it didn't matter whether or not the DD-statement was a DUMMY but it may as >well be. > > It is up to the designer to code what they want. They need not open anything if they choose to just see if the DDNAME is allocated. Or they could make sure it is DUMMY. Philosophically, claiming the DDNAME is all we need should place no further restriction on what it is allocated to. I tend to experiment using REXX and merely check for the existence of the DDNAME allocated to my step and go no further. No open, no devtype. My design choice. -- 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: Utility to print tracks
On 29 Jun 2007 09:36:25 -0700, in bit.listserv.ibm-main you wrote: >FDRDSF can print any track on a volume, by cylinder and head (or range) Of course this facility should be highly restricted since this probably bypasses all dataset access checking. This comment would apply to the other programs mentioned as well. Clark Morris -- 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
FIN APAR Status Updates
I notice some FIN APARs for which I am on AST have been updated with availability notices, such as: In OA15305: The fix for this FIN APAR was shipped in the base for z/OS V1R9. Has this always been the practice? Is it done uniformly? If it's new and consistent, it's a welcome innovation. -- gil -- 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: DFSORT V1R5 - ICE751I and ICE752I
>No, but you would then have to supply the volume serial list or use volumes >mounted as Storage. Since when? I used UNIT=(SYSDA,nn) years ago! (1981). The point is that it worked before SMS. - Too busy driving to stop for gas! -- 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: DFSORT V1R5 - ICE751I and ICE752I
No, but you would then have to supply the volume serial list or use volumes mounted as Storage. From: Ted MacNEIL [mailto:[EMAIL PROTECTED] Sent: Sun 7/1/2007 2:10 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: DFSORT V1R5 - ICE751I and ICE752I >If necessary and the file is SMS managed add a volume parameter to the UNIT >parameter, eg. UNIT=(SYSDA,10). It doesn't have to be SMS managed for the volume parameter to work. - Too busy driving to stop for gas! -- 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: Windows application key from a vendor
On Sun, 1 Jul 2007 00:27:11 EDT, A. Harry Williams wrote: > >It's a "security" function of the PDF file. Look at the Document >Properties (Ctrl-D on Windows) and select the Security Tab. >For example, try copying from this > >http://www.share.org/client_files/docupload/Bit%20Bucket%2026%20(1A).pdf > Indeed. I can print it to a PostScript file, and I can render that PostScript with Ghostscript, but when I try: gs -sDEVICE=pdfwrite -sOutputFile=- Bit-Bucket-26-\(1A\).ps ... Ghostscript says: This PostScript file was created from an encrypted PDF file. Redistilling encrypted PDF is not permitted. ... but I have the source code. I wonder what I could do if I were willing to violate the DMCA? Might it be as simple as editing out the lock in the .ps? -- gil -- 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: File to PDF
Don't know if you've got SAS, but PROC ODS can produce PDF output at V9 level. ** See what's free at http://www.aol.com. -- 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: DFSORT V1R5 - ICE751I and ICE752I
>If necessary and the file is SMS managed add a volume parameter to the UNIT >parameter, eg. UNIT=(SYSDA,10). It doesn't have to be SMS managed for the volume parameter to work. - Too busy driving to stop for gas! -- 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: DFSORT V1R5 - ICE751I and ICE752I
Anton, A few questions, 1. How fragmented is your free work space? Defragging work work volumes might help. 2. Why are you not using SIZE=MAX as IBM recommends? 3. Why such a small region size? If you use Size=MAX and region=om, the job might still fail but you won't have to wait 2 hours. -- 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: IBM obsoleting mainframe hardware
The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well. [EMAIL PROTECTED] (Chris Mason) writes: > One of the presentations was someone from a big UK bank who defended > IBM having made the 155 and 165 available and relatively shortly > afterwards having announced the 158 and 168 - together with the > relatively expensive DAT box extension to the 155 and 165. I hope I'm > remembering the details about right. > > I heard about this only second-hand but I believe the argument was > that IBM was right to offer the enhanced performance of the 155 and > 165 as soon as it could in spite of the fact that it knew that the > virtual storage models were well advanced in development. I guess > there was a shadow of the "it's illegal to preannounce" principle > hanging over this. re: http://www.garlic.com/~lynn/2007n.html#31 IBM obsoleting mainframe hardware http://www.garlic.com/~lynn/2007n.html#34 IBM obsoleting mainframe hardware 370/165 ... announce jun70 http://www-03.ibm.com/ibm/history/exhibits/mainframe/mainframe_PP3165.html 370/168 ... announce aug72 http://www-03.ibm.com/ibm/history/exhibits/mainframe/mainframe_PP3168.html for virtual memory ... hacking virtual memory support into MVT (for VS2/SVS) was needed in addition to the virtual memory hardware retrofitted to 165s (there were significant software as well as hardware schedules). this is similar to previous comments about *crash* program to try and get out 370-xa (after FS project was killed) and POK in 1976, convincing the corporation to shutdown vm370 product and transfer all the developers to POK as part of being able to make mvs/xa (software) schedule (although Endicott was eventually able to save part of the vm370 product mission). i've mentioned before about (370 virtual memory) prototype work that went on in pok, using 360/67s and hacking "single address space" virtual memory into the side of MVT ... as well as cobbling in cp67's (ccw translation) CCWTRAN into MVT ... i.e. cp67 had started out having to build "shadow" channel programs with real addresses ... for the virtual machine's channel programs; all the (MVT) channel programs passed via EXCP ... would be equivalent "virtual address" channel programs ... requiring similar translation (and misc. other things like page locking/pinning) recent posts about using CP67's CCWTRANS as part of turning MVT into os2/svs http://www.garlic.com/~lynn/2007f.html#6 IBM S/360 series operating systems history http://www.garlic.com/~lynn/2007f.html#33 Historical curiosity question The other part ... was that there was a lot of work to retrofit virtual memory to 165 ... so much so that they ran into schedule problems. In order to buy back six months in the 165 virtual memory schedule, there was an escalation dropping several features from the original 370 virtual memory architecture. Once the 165 engineers had won that battle, then all the other processors (that had already completed their virtual memory implementations) ... had to go back and remove the dropped features. recent posts mentioning 165-ii schedule issues and impact on dropping features from original 370 virtual memory architecture http://www.garlic.com/~lynn/2007f.html#7 IBM S/360 series operating systems history http://www.garlic.com/~lynn/2007f.html#16 more shared segment archeology http://www.garlic.com/~lynn/2007j.html#43 z/VM usability http://www.garlic.com/~lynn/2007k.html#28 IBM 360 Model 20 Questions -- 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: DFSORT V1R5 - ICE751I and ICE752I
Yes... thanks for all the feedback and my initial posting was more out of frustration with DFSORT and SMS. So here comes more detail : The Scene of the crime : Input Dataset contains 4,826,605 records of 2000 bytes each. The Sort Control Cards : ICE143I 0 BLOCKSET SORT TECHNIQUE SELECTED ICE250I 0 VISIT http://www.ibm.com/storage/dfsort FOR DFSORT PAPERS, EXAMPLES AN ICE000I 1 - CONTROL STATEMENTS FOR 5694-A01, Z/OS DFSORT V1R5 - 03:58 ON SUN JUL SORT FIELDS=(49,6,A,59,8,A,91,6,A,99,8,A,81,2,A, 97,2,A,1947,3,A,55,4,A,1950,2,A),FORMAT=CH ICE201I E RECORD TYPE IS F - DATA STARTS IN POSITION 1 ICE751I 0 C5-K90007 C6-K90007 C7-K9 C8-K90007 E4-K90007 C9-BASE E5-K14794 ICE193I 0 ICEAM1 ENVIRONMENT IN EFFECT - ICEAM1 INSTALLATION MODULE SELECTED ICE088I 1 HWLK221A.STEP220 .SORT, INPUT LRECL = 2000, BLKSIZE = 4000, TYPE = ICE092I 0 MAIN STORAGE = (350,524288,524288) ICE156I 0 MAIN STORAGE ABOVE 16MB = (458304,458304) ICE127I 0 OPTIONS: OVFLO=RC0 ,PAD=RC0 ,TRUNC=RC0 ,SPANINC=RC16,VLSCMP=N,SZERO=Y, ICE128I 0 OPTIONS: SIZE=524288,MAXLIM=2097152,MINLIM=524288,EQUALS=Y,LIST=Y,ERET ICE129I 0 OPTIONS: VIO=N,RESDNT=ALL ,SMF=NO ,WRKSEC=Y,OUTSEC=Y,VERIFY=Y,CHALT= ICE130I 0 OPTIONS: RESALL=0,RESINV=0,SVC=109 ,CHECK=Y,WRKREL=Y,OUTREL=Y,CKPT=N,S ICE131I 0 OPTIONS: TMAXLIM=5242880,ARESALL=0,ARESINV=0,OVERRGN=0,CINV=Y,CFW=Y,DS ICE132I 0 OPTIONS: VLSHRT=N,ZDPRINT=Y,IEXIT=N,TEXIT=N,LISTX=N,EFS=NONE ,EXITC ICE133I 0 OPTIONS: HIPRMAX=OPTIMAL,DSPSIZE=MAX ,ODMAXBF=0,SOLRF=Y,VLLONG=N,VSAMI ICE235I 0 OPTIONS: NULLOUT=RC0 ICE084I 0 EXCP ACCESS METHOD USED FOR SORTOUT ICE084I 0 EXCP ACCESS METHOD USED FOR SORTIN ICE750I 0 DC 0 TC 9653212000 CS DSVVV KSZ 45 VSZ 45 Sort Step JCL : XXSORT PROC PROG=ICEMAN, XXWTR1='*', XXCYL=15, XXDEVTYP=TMPDA, XXRGIN=6M XXSORT EXEC PGM=&PROG,REGION=&RGIN,PARM='SIZE=350' IEFC653I SUBSTITUTION JCL - PGM=ICEMAN,REGION=6M,PARM='SIZE=350' XXSYSOUT DD SYSOUT=&WTR1 IEFC653I SUBSTITUTION JCL - SYSOUT=* XXSYSOUX DD SYSOUT=&WTR1 IEFC653I SUBSTITUTION JCL - SYSOUT=* XXSYSLMOD DD SPACE=(3600,(20,20,1)),DSN=&&GOSET, XX UNIT=&DEVTYP IEFC653I SUBSTITUTION JCL - SPACE=(3600,(20,20,1)),DSN=&&GOSET,UNIT=TMPDA XXSYSLIN DD SPACE=(80,(10,10,)),DSN=&&LOADSET, XX UNIT=&DEVTYP IEFC653I SUBSTITUTION JCL - SPACE=(80,(10,10,)),DSN=&&LOADSET,UNIT=TMPDA XXSYSUT1 DD SPACE=(1000,(60,20)),UNIT=&DEVTYP IEFC653I SUBSTITUTION JCL - SPACE=(1000,(60,20)),UNIT=TMPDA //SORTWK01 DD SPACE=(CYL,(4000,500)),UNIT=TMPDA, //DCB=(LRECL=2000,BLKSIZE=28000,RECFM=FB) //SORTWK02 DD SPACE=(CYL,(4000,500)),UNIT=TMPDA, //DCB=(LRECL=2000,BLKSIZE=28000,RECFM=FB) X/SORTWK02 DD SPACE=(CYL,(&CYL,&CYL)),UNIT=&DEVTYP IEFC653I SUBSTITUTION JCL - SPACE=(CYL,(750,750)),UNIT=TMPDA //SORTWK03 DD SPACE=(CYL,(4000,500)),UNIT=TMPDA, //DCB=(LRECL=2000,BLKSIZE=28000,RECFM=FB) X/SORTWK03 DD SPACE=(CYL,(&CYL,&CYL)),UNIT=&DEVTYP IEFC653I SUBSTITUTION JCL - SPACE=(CYL,(750,750)),UNIT=TMPDA //SORTWK04 DD SPACE=(CYL,(2000,500)),UNIT=TMPDA, //DCB=(LRECL=2000,BLKSIZE=28000,RECFM=FB) X/SORTWK04 DD SPACE=(CYL,(&CYL,&CYL)),UNIT=&DEVTYP IEFC653I SUBSTITUTION JCL - SPACE=(CYL,(750,750)),UNIT=TMPDA //SORTWK05 DD SPACE=(CYL,(3000,500)),UNIT=TMPDA, //DCB=(LRECL=2000,BLKSIZE=28000,RECFM=FB) X/SORTWK05 DD SPACE=(CYL,(&CYL,&CYL)),UNIT=&DEVTYP IEFC653I SUBSTITUTION JCL - SPACE=(CYL,(750,750)),UNIT=TMPDA //SORTWK06 DD SPACE=(CYL,(3000,500)),UNIT=TMPDA, //DCB=(LRECL=2000,BLKSIZE=28000,RECFM=FB) X/SORTWK06 DD SPACE=(CYL,(&CYL,&CYL)),UNIT=&DEVTYP IEFC653I SUBSTITUTION JCL - SPACE=(CYL,(750,750)),UNIT=TMPDA //SORTWK07 DD SPACE=(CYL,(1000,500)),UNIT=TMPDA, //DCB=(LRECL=2000,BLKSIZE=28000,RECFM=FB) X/SORTWK07 DD SPACE=(CYL,(&CYL,&CYL)),UNIT=&DEVTYP //* IEFC653I SUBSTITUTION JCL - SPACE=(CYL,(750,750)),UNIT=TMPDA //SYSPRINT DD SYSOUT=* //SORTIN DD DSN=HWL.HWLK228P.ARCHIVE,DISP=OLD //SORTOUT DD DSN=HWL.HWLKSORT.HWLK228P, //DISP=(NEW,PASS,DELETE), //STORCLAS=LRGETAPE,UNIT=3490, //DCB=(HWG.PATTERN.RECL2000,BLKSIZE=0) //SYSINDD * //* The WORK packs available : We have 7 work packs with the following FREE space : WORK00 9,800 Cylinders WORK01 9,861 Cylinders WORK02 9,555 Cylinders WORK03 2,288 Cylinders WORK04 3,321 Cylinders WORK05 4,222 Cylinders Work06 3,333 Cylinders JOB Log IEF233A M 3E00,R06331,,HWLK221A,SORT,HWL.HWLK228P.ARCHIVE IEF233A M 3600,PRIVAT,SL,HWLK221A,SORT,HWL.HWLKSORT.HWLK228P IEC502E K 3E00,R06331,SL,HWLK221A,SORT,HWL.HWLK228P.ARCHIVE IEC501A M 3E00,R03689,SL,COMP,HWLK221A,SORT.STEP220,HWL.HWLK228P.ARCHIVE IEC030I B37-04,IFG0554A,HWLK221A,SORT,SORTWK06,6223,WRK003,04210011,SYS07182.T +ICE097I 1 HWLK221A.STEP220 SORT RECOVERING FROM B37 ABEND ON SORTWK DATA SET IEC030I B37-04,IFG0554A,HWLK221A,SORT,SORTWK03,692C,WRK002,04210010,SYS07182.T +ICE097I 1 HWLK221A.STEP220 SORT RECOVERING FRO
Re: Navigating the control block maze
There was a lot of discussion of this same issue within the last year. Check the IBM-MAIN archives. Bill Fairchild Plainfield, IL ** See what's free at http://www.aol.com. -- 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: DFSORT V1R5 - ICE751I and ICE752I
Anton, If the B37 is on your output file that is one thing, however if it is on SORTWK then you probably need to add more. Just an FYI... For DFSORT it will only use the first volume of a SORTWK dd statement. So if you code //SORTWK01 DD UNIT=SYSDA,VOL=(,,,20),... then it will not use the other 19 volumes. Syncsort on the other hand I think honors that request. Just a thought. Lizette > Anton, > > I am not sure what is your issue. Not all IBM messages are documented > because some are for internal diagnostics by the IBM L2/L3 teams (if > needed). So I would not expect every message documented because it would > be > meaningless to me since I do not have access to the IBM Code for DFSORT. > > It seems to me you are upset over the fact that the job ran for 2 hours > before abending. That maybe a valid issue. Since you did not post any > specifics (SORT CONTROL CARDS, type of data being sorted or how much data > being sorted) it is hard to tell if the sort needs tuning. > > If you turned the DIAGs on for this job, then you probabaly need to open > an > ETR with IBM to resolve the B37 issue. > > Lizette > > > > Hi, > > > > I abended twice this weekend on SB37-04, after running for TWO hours and > > when I look at the output of the DFSORT , I see ICE751I and ICE752I > > messages. > > > > The IBM manual says : > > > > Explanation: DFSORT diagnostic message for use by IBM software support > > personnel. > > > > Conclusion : > > > > That sounds line "s'mee" but it still does not mean much. > > > > Can the IBM DFSORT team not hire a H1B visa person for $8 and hour and > > document all these possible output messages ? > > > > Anton -- 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: DFSORT V1R5 - ICE751I and ICE752I
Anton, Lizette is correct that the diagnostic messages are for use by our L2/L3 teams and that's why they are not documented. The ICE751I and ICE752I messages are informational (note they end with an I) and are issued for both successful and unsuccessful sorts. Usually when a sort fails, there is an ICExxxA message to indicate the cause. If you would like to send me the sysout of your failed sort, I'd be happy to look at it and help determine the cause of your abend. Have a nice day, Dave Betten DFSORT Development, Performance Lead IBM Corporation email: [EMAIL PROTECTED] DFSORT/MVSontheweb at http://www.ibm.com/storage/dfsort/ IBM Mainframe Discussion List wrote on 07/01/2007 11:27:46 AM: > Anton, > > I am not sure what is your issue. Not all IBM messages are documented > because some are for internal diagnostics by the IBM L2/L3 teams (if > needed). So I would not expect every message documented because it would be > meaningless to me since I do not have access to the IBM Code for DFSORT. > > It seems to me you are upset over the fact that the job ran for 2 hours > before abending. That maybe a valid issue. Since you did not post any > specifics (SORT CONTROL CARDS, type of data being sorted or how much data > being sorted) it is hard to tell if the sort needs tuning. > > If you turned the DIAGs on for this job, then you probabaly need to open an > ETR with IBM to resolve the B37 issue. > > Lizette > > > > Hi, > > > > I abended twice this weekend on SB37-04, after running for TWO hours and > > when I look at the output of the DFSORT , I see ICE751I and ICE752I > > messages. > > > > The IBM manual says : > > > > Explanation: DFSORT diagnostic message for use by IBM software support > > personnel. > > > > Conclusion : > > > > That sounds line "s'mee" but it still does not mean much. > > > > Can the IBM DFSORT team not hire a H1B visa person for $8 and hour and > > document all these possible output messages ? > > > > Anton > > > > -- > 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: DFSORT V1R5 - ICE751I and ICE752I
Anton, Forgive me if you already know this but since you abended twice I'll go ahead. The SB37-04 message pointed to the offending file which ran out of space. Simply increase the allocations. If necessary and the file is SMS managed add a volume parameter to the UNIT parameter, eg. UNIT=(SYSDA,10). This will allow the file to extend across as many as 10 volumes. 59 is the architectural limit. If the SB37 occurred on the sortwk files, simply add more sort work files. Sort work files will not extend across multiple volumes. At least they did not the last time I looked. , I abended twice this weekend on SB37-04, after running for TWO hours and when I look at the output of the DFSORT , I see ICE751I and ICE752I messages. -- 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: DFSORT V1R5 - ICE751I and ICE752I
Anton, I am not sure what is your issue. Not all IBM messages are documented because some are for internal diagnostics by the IBM L2/L3 teams (if needed). So I would not expect every message documented because it would be meaningless to me since I do not have access to the IBM Code for DFSORT. It seems to me you are upset over the fact that the job ran for 2 hours before abending. That maybe a valid issue. Since you did not post any specifics (SORT CONTROL CARDS, type of data being sorted or how much data being sorted) it is hard to tell if the sort needs tuning. If you turned the DIAGs on for this job, then you probabaly need to open an ETR with IBM to resolve the B37 issue. Lizette > Hi, > > I abended twice this weekend on SB37-04, after running for TWO hours and > when I look at the output of the DFSORT , I see ICE751I and ICE752I > messages. > > The IBM manual says : > > Explanation: DFSORT diagnostic message for use by IBM software support > personnel. > > Conclusion : > > That sounds line "s'mee" but it still does not mean much. > > Can the IBM DFSORT team not hire a H1B visa person for $8 and hour and > document all these possible output messages ? > > Anton > -- 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
DFSORT V1R5 - ICE751I and ICE752I
Hi, I abended twice this weekend on SB37-04, after running for TWO hours and when I look at the output of the DFSORT , I see ICE751I and ICE752I messages. The IBM manual says : Explanation: DFSORT diagnostic message for use by IBM software support personnel. Conclusion : That sounds line "s'mee" but it still does not mean much. Can the IBM DFSORT team not hire a H1B visa person for $8 and hour and document all these possible output messages ? Anton -- 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: the USS heresy
This thread deserves to die, I suspect indeed that it were better stillborn. -- Maybe I can inject a little humor into the death throes: A very fine lady was invited aboard a US Navy ship, to a reception after the conclusion of some multi-national naval maneuvers. While walking around, she noticed a number of abbreviations on the uniforms of the officers present. Approaching a US Navy officer, she inquired "What does the 'USS' stand for?" He replied "USS stands for United States Ship, ma'am". Wandering further, she met an officer of the Royal Navy, so she asked "What does 'HMS' stand for?" The British officer replied "HMS stands for Her Majesty's Ship, ma'am." Near the end of the reception, she met an Italian officer who was slightly "into his cups". She asked him "What does the 'IMB' on your hat stand for?" Wavering slightly, he replied "It'sa my boat"! - Moral of the story: Acronyms are VERY MUCH context-sensitive. If we can at least agree on that single point, then the so-called heresy pretty much ceases to exist, and it's only the obvious misuses that matter. And we can all pick them out, pretty much without a second thought. -- 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: NetView Automation of Console Message
Kevin Pat covered the possibility that some of the actions you may eventually decide to take may not need actually to use NetView. From my experience with NetView automation of more than 15 years ago - and it seems inconceivable that any of the functions could have been lost in the meantime - all of the actions you propose are, in principle, possible. I'm pretty sure that if you use the techniques I used to use, you would need to create an entirely new message of your own invention from within the message automation table or a Clist which could then have the attributes you wanted. Probably more flexibility has been introduced since I played with console messages but I seem to remember that messages were coloured by type rather than by individual message. I noticed specifically your desire to create a "retained" message. In my automation of system startup, system shutdown, and, for very special reasons, change of JES2 environment, I identified particular key events and placed a retained message[1] on the console in order to show that the event was pending. When the event had happened, say, JES2 had started, VTAM had started or CICS had started, the message was also "deleted" by the automation so that it disappeared off the console. You didn't say you wanted to do that but there's no reason why you shouldn't amaze your colleagues! Why did I go to the trouble of creating these status messages? I was teaching hands-on classes - which explains the JES2 environment issue by the way - and I was assisted by some colleagues. I have always delighted in getting rid of essentially useless messages, especially during system startup, and I had achieved total elimination with this fully automated environment - hurrah! Except that my colleagues now asked how the were they supposed to know what - if anything - was going on and whether my automation was actually doing what it should - given that there were probably four MVS systems starting up and relying on an underlying VM system which might be a bit - or more than a bit - overloaded because of activity from simultaneous classes. Since I happen still to have some presentation text which covers the logic for creating and deleting these messages and it's not too large, I've appended it to the post. Incidentally, the LCWTO Clist shrouds a mystery. Perhaps a wise man - or woman - who remembers NetView automation around 1990 has an explanation. Finally, NetView automation does cover the possibility to create a WTOR as well as a WTO (and a DOM) but, when I covered this topic teaching NetView automation facilities, I rather discouraged using WTOR. It seemed to me possible to achieve the same results simply using messages, commands and retaining status in global variables. Is it not significant that those products which used to run with outstanding WTORs - I believe IMS was one - or was it CICS, perhaps both - eventually got the option to use a MODIFY (F) (and probably STOP (P)) command as an alternative? That way the operator didn't need to go searching for the WTOR reply number. I remember that once I had found the QEDIT macro (the interface for F and P commands) for my trivial long-running programs, I never looked back. [1] Strictly a message which had the necessary bits set to ensure that it was a retained message. Chris Mason --- Flag System === FLAGON Clist /* REXX FLAGON */ trace e prefix = 'AUTO' if msgvar(1) = '?' then do 'CLEAR' say 'The FLAGON Clist is used to keep a retained message on the' say 'system console to indicate the status of vital automated' say 'procedures. The first parameter is the name of the "flag"' say 'and the second is the message to be retained.' say 'The "flag" message ID is kept in common global variable:' say 'prefix.FLAG.flagname' exit 0 end parse arg flagname flagmsg if flagname = '' then do say 'A "flag" name is required as the first parameter.' exit 0 end if flagmsg = '' then do say 'A "flag" message is required as the second parameter.' exit 0 end text = flagname' 'flagmsg 'GLOBALV PUTT TEXT' 'LCWTO' 'GLOBALV GETT WTOID' name = prefix'.FLAG.'flagname interpret name'='wtoid 'GLOBALV PUTC 'name exit 0 FLAGOFF Clist /* REXX FLAGOFF */ trace e prefix = 'AUTO' if msgvar(1) = '?' then do 'CLEAR' say 'The FLAGOFF Clist is used to remove a retained message from' say 'the system console. The retained message indicates the status' say 'of a vital automated procedure. The first, and only, parameter' say 'is the name of the "flag".' say 'The "flag" message ID is kept in common global variable:' say 'prefix.FLAG.flagname' exit 0 end parse arg flagname if flagname = '' then do say 'A "flag" name is required as the first parameter.' exit 0 end name = prefix'.FLAG.'flagname 'GLOBALV GETC 'name interpret 'smsgid='name 'DOM' exit 0 Notes: It may be noted in the previous Message Automation Table entries
Re: Background of disabling ISVs via JCL
Eric It's strange I never came across this sort of "switch" technique - but I've been rather out of it for the last few years. There were some earlier posts which suggested - to me anyhow - that all the program did was try to OPEN a particular DD-name and then examine the appropriate bit - I seem to remember DCBOFLG. If the OPEN succeeded, take action A; if the OPEN failed, take the binary alternative action B. That way it didn't matter whether or not the DD-statement was a DUMMY but it may as well be. Never let it be said I don't research my posts. I Googled for DCBOFLG and found the following - immersed in some undisplayable characters - one of 4 hits: IF (LTR,R15,R15,Z),OR,(TM,DCBOFLG,X'80',O) WTO 'OPEN OK' ELSE WTO 'OPEN FAIL' ENDIF It seems me memory isn't so bad! Chris Mason - Original Message - From: "Eric Spencer" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: Sent: Friday, June 29, 2007 4:21 PM Subject: Re: Background of disabling ISVs via JCL In general, you just do a DEVTYPE to see if the DD is allocated and if so is it DUMMY... nothing exotic. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Elardus Engelbrecht Sent: Friday, June 29, 2007 5:55 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Background of disabling ISVs via JCL Thanks T. MacNEIL and C.P. Vernooy for your kind answers. Another question, if the technique is via hooks, are SVCs involved? If so, do you insist to see the source of the SVCs before using the product? Groete / Greetings Elardus Engelbrecht -- 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: IBM obsoleting mainframe hardware
Bruce This reminds me of an IBM event for technical folk held in Madrid in 1971. One of the presentations was someone from a big UK bank who defended IBM having made the 155 and 165 available and relatively shortly afterwards having announced the 158 and 168 - together with the relatively expensive DAT box extension to the 155 and 165. I hope I'm remembering the details about right. I heard about this only second-hand but I believe the argument was that IBM was right to offer the enhanced performance of the 155 and 165 as soon as it could in spite of the fact that it knew that the virtual storage models were well advanced in development. I guess there was a shadow of the "it's illegal to preannounce" principle hanging over this. Why did I hear about this only second-hand. Well, the Prado and sites such as the Plaza Major were far more interesting! Chris Mason - Original Message - From: "Bruce Black" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: Sent: Friday, June 29, 2007 6:41 PM Subject: Re: IBM obsoleting mainframe hardware I worked for one company which had just signed a 7 year lease on a 370/155 without the DAT hardware. They wanted me to upgrade from DOS to MVS, so they had to pop for the DAT box and also extra memory (to the max of 2MB!!!) to get MVS to work. The guy who negotiated the lease was gone soon after -- Bruce Black Senior Software Developer Innovation Data Processing -- 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: Navigating the control block maze
On Sun, 1 Jul 2007 01:30:52 +0200 Lindy Mayfield <[EMAIL PROTECTED]> wrote: :>I know I shouldn't feel bad about asking this question because it seems so elementary. Anyway, can someone please briefly point me in the right direction? :>I have 3 basic questions that I would like to ask to help me fill some gaps in my knowledge. :>1) How do I know what control blocks or memory for another address space can be seen from my address space? :>In other words, for example, I can loop through ASCB chain and find the ASCB of other address spaces and see some control blocks that belong to them. Sometimes, though, when I think that I'm looking at them I end up looking at myself. :>What did I do wrong? Or what did I understand wrong? Or perhaps more technically, where in the IBM docs does it tell me (or hint to me) that I might fall into this trap? Those that are in a common subpool, typically 241 or 245. The control block description identifies the subpool. :>2) If I want to look at control blocks and memory and they are not in shared memory (is it shared memory? Is that the right term?), then what mechanism would I use to view that data? :>Just a hint to the docs would be great here. I haven't found what I'm looking for just yet. It will require getting "special" - in supervisor state. Once you have reached that state there are various ways of getting to the storage. The cleanest (as well as the purist approach) is via SRB. :>3) This is a generic "how to catch a fish" question. Say I want a piece of information and I know it is available because I see it in JES listings or SDSF or something like that. Let's take job accounting information as an example. How do you know where to find that? (Ok, that one I know, I just used it as an example. It is in the OUCB.) The Data Areas docs are great, but the comments telling you what is what aren't so clear. :>Right now I just dig for a few hours and if I don't find it I ask on a list like this one. Is there a better way? There are various programs on the CBT that display stuff. Look at SHOWMVS for good examples. -- Binyamin Dissen <[EMAIL PROTECTED]> http://www.dissensoftware.com Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. -- 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
