Re: Using NOTE and POINT simulation macros on CMS?
On Wed, 8 Aug 2012 05:45:42 -0600, Paul Gilmartin paulgboul...@aim.com wrote: IIRC, there's an OS convention that setting the lowest byte (Z) of the TTRZ to '01'x causes reading of the block following the one POINTed to by the TTR. Does CMS respect this? When you POINT with Z=0, CMS decrements TTR by 1 and stores that as the 'last read' value. When you POINT with Z=1, CMS stores TTR as you supply it. (You guys made me find my BSAM test case, ca. 1992, and update it.) Alan Altmark IBM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using NOTE and POINT simulation macros on CMS?
On Wed, 8 Aug 2012 09:18:35 -0400, Shmuel Metz (Seymour J.) shmuel+...@patriot.net wrote: To increment the record number by one, add 256 to the TTR. ITYM add 256 to the TTRz. Yes, indeed. Alan Altmark IBM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using NOTE and POINT simulation macros on CMS?
On Aug 8, 2012, at 18:51, Shmuel Metz (Seymour J.) wrote: Does this mean that if the current record spans several blocks, setting the z byte causes enough intervening blocks containing enough segments to be skipped that the block read contains the first segment of the next record? No; TTR1 will access the next physical record. BSAM doesn't deal with the RDW. In: http://publibz.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/DGT2D4A0/3.8.7.8 (which I trimmed too much and, now that I read the outline hierarchy, refers to PDSEs), I read: 3.8.7 Processing a Member of a PDSE 3.8.7.8 Using the POINT Macro to Position to a Block The POINT macro positions to the first segment of a spanned record even if the NOTE was done on another segment. If the current record spans blocks, setting the z byte of the TTRz field to one lets you access the next record (not the next segment). So I conclude that if the current block (itself a slippery concept with PDSEs) contains only an interior segment of a spanned record, POINT to a TTRz will cause the following READ to read the block containing the first segment of that [logical] record, and POINT to a TTR1 will cause the following READ to read the block containing the first segment of the next [logical] record. It's still pretty amazing. THis could be a point of incompatibility between PDSE and PDS. Who keeps spanned records in a PDSE or PDS, anyway? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using NOTE and POINT simulation macros on CMS?
Paul Gilmartin wrote: | Who keeps spanned records in a PDSE or PDS, anyway? In or out of a PDSE spanned records make LRECL BLKSIZE possible. Attitudes toward RECFM=VBS probably reflect a mixture of 1) longevity and 2) experience with scientific computation. Unformatted FORTRAN i/o for the IBM 704 used them, and its implementation using 'green words' was essentially the same as the one in use today. They were devised to treat the problem of outputting, say, an array x(100,100) of 36-bit words, which would have been difficult to fit into a single tape record block of the time. John Gilmore, Ashland, MA 01721 - USA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using NOTE and POINT simulation macros on CMS?
On Thu, 2 Aug 2012 17:00:02 -0400, Thomas David Rivers riv...@dignus.com wrote: I'm having some issues with using the OS Simulation macros NOTE and POINT under VM/CMS. I've been scouring documentation to try and discover just what the CMS differences are... But, at the moment, I'm trying to simply do a BSAM OPEN (for READ)... Then, a NOTE to record the starting TTR of the file... Then - reading the file to the end (with regular BSAM READ+CHECK) Then, a POINT to return to the beginning of the file, using the TTR retrieved from just after the OPEN (with +1 added because the NOTE occurs after OPEN but before any READ.) Then - try and READ the blocks again... What I'm seeing is that the NOTE returns something that looks like a TTR. Then, the READs+CHECKs occur that read the file. The POINT supposedly returns us to the begining, but the next READ gets EOD. Clearly - the POINT hasn't worked. And, as you might expect - this approach works just great on z/OS. Does anyone know of any vagaries with the OS simulation of NOTE/POINT? I did see that you can't code TYPE=REL (or TYPE=anything for that matter.) But, I don't really care what the block address is... just that it is the valid block address for the beginning of the file. Thanks for any pointers! First pointer: We welcome your CMS questions over on IBMVM! ;-) Sorry I haven't been watching IBM-MAIN as closely as I should, but the TTR isn't. It's the CMS file system record number of the record that was just read (shifted left 8 bits) i.e. rr00. At OPEN, no records have been read, so the record number is zero. You NOTEd the zero value and added 1. Then you POINTed to 0x01, but that low-order byte isn't used, so you are effectively pointing to record zero.When a zero is passed to the lower-level CMS filesystem interfaces (FSREAD/FSWRITE), it means read or write next record. To increment the record number by one, add 256 to the TTR. To explicitly position to record 1, POINT to TTR 0x0100 Alan Altmark IBM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using NOTE and POINT simulation macros on CMS?
On Aug 8, 2012, at 01:04, Alan Altmark wrote: First pointer: We welcome your CMS questions over on IBMVM! ;-) Sorry I haven't been watching IBM-MAIN as closely as I should, but the TTR isn't. It's the CMS file system record number of the record that was just read (shifted left 8 bits) i.e. rr00. At OPEN, no records have been read, so the record number is zero. You NOTEd the zero value and added 1. Then you POINTed to 0x01, but that low-order byte isn't used, so you are effectively pointing to record zero. ... IIRC, there's an OS convention that setting the lowest byte (Z) of the TTRZ to '01'x causes reading of the block following thenone POINTed to by the TTR. Does CMS respect this? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using NOTE and POINT simulation macros on CMS?
In 8082333213958528.wa.alanaltmarkus.ibm@listserv.ua.edu, on 08/08/2012 at 02:04 AM, Alan Altmark alan_altm...@us.ibm.com said: Sorry I haven't been watching IBM-MAIN as closely as I should, but the TTR isn't. It's the CMS file system record number of the record that was just read (shifted left 8 bits) i.e. rr00. The TTR is shifted left 8 bits in z/OS as well; bit 31 serves as a next record indicator. That goes back to OS/360, so I would regard it as a bug if the OS simulation can't handle it. To increment the record number by one, add 256 to the TTR. ITYM add 256 to the TTRz. -- Shmuel (Seymour J.) Metz, SysProg and JOAT Atid/2http://patriot.net/~shmuel We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using NOTE and POINT simulation macros on CMS?
On Wed, 8 Aug 2012 09:18:35 -0400, Shmuel Metz (Seymour J.) shmuel+...@patriot.net wrote: To increment the record number by one, add 256 to the TTR. ITYM add 256 to the TTRz. Does this work when you cross a track boundary? I might expect it to work less well for TTRz than for relative block number. And, in Using Data Sets: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/dgt2d490/3.8.7.8 3.8.7.8 Using the POINT Macro to Position to a Block ... If the current record spans blocks, setting the z byte of the TTRz field to one lets you access the next record (not the next segment). Does this mean that if the current record spans several blocks, setting the z byte causes enough intervening blocks containing enough segments to be skipped that the block read contains the first segment of the next record? Wow! Does this apply to RECFM=VBS only? Does CMS support setting the z byte? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using NOTE and POINT simulation macros on CMS?
No, and a track boundary is not a multiple of 256. You have to compare the new record number to the maximum number of records that will fit on the track. Or, even more fun, if your records are variable-length, then you get to play with the track balance service to see if there is enough room left on the track for your next record regardless of its record number. When you cross a track boundary for whatever reason, the next sequential record number will be 1 and the track number will be one higher than the TT part of the previous TTR. Unless, of course, you have spanned records, and then it really gets fun. Bill Fairchild Programmer Rocket Software 408 Chamberlain Park Lane • Franklin, TN 37069-2526 • USA t: +1.617.614.4503 • e: bfairch...@rocketsoftware.com • w: www.rocketsoftware.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Wednesday, August 08, 2012 3:13 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Using NOTE and POINT simulation macros on CMS? On Wed, 8 Aug 2012 09:18:35 -0400, Shmuel Metz (Seymour J.) shmuel+...@patriot.net wrote: To increment the record number by one, add 256 to the TTR. ITYM add 256 to the TTRz. Does this work when you cross a track boundary? I might expect it to work less well for TTRz than for relative block number. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using NOTE and POINT simulation macros on CMS?
I have successfully used POINT, READ, and CHECK Macros on CMS to read MVS datasets, but never had a need for NOTE. How did you successfully use POINT without having first done a NOTE so that the POINT knows where to POINT? Bill Fairchild Programmer Rocket Software 408 Chamberlain Park Lane • Franklin, TN 37069-2526 • USA t: +1.617.614.4503 • e: bfairch...@rocketsoftware.com • w: www.rocketsoftware.com The TTR for POINT to use was calculated based on user input. We used to share a CA-TMS TMC between VM and MVS. VM:Tape had read/write access and users had read only access to the TMC file. We had a VM/CMS program that could read the TMC volume/dataset records and display the information using XMENU. The TMC contained control records at the beginning of the file with block offsets for the volser ranges that were defined. The LRECL and BLKSIZE of the TMC were used to calculate the number of blocks per track based on the device type, (was 3380, then later 3390). The user entered the volser of the tape they wanted to display and the TTR of the block/record was calculated, (based on the above info), and supplied to POINT, then a READ was issued to get the correct block/record. TMS was replaced with RMM, which of course does not have support for VM/CMS and to make it worse, RMM uses a VSAM file, which cannot even be read currently on VM/CMS. I created a QSAM extract file from RMM and a QSAM Index file, (that contained the tape volser and record number in the extract file), so the Index could be read from VM/CMS to calculate the TTR to use with the extract file. The extract and Index file are updated every 30 minutes so the data is not live like it was with the TMC. It's a kludge, but what else can you do when IBM doesn't support their operating systems equally and they don't understand the concept of sharing data between different systems. -- Dale R. Smith -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using NOTE and POINT simulation macros on CMS?
snip TMS was replaced with RMM, which of course does not have support for VM/CMS and to make it worse, RMM uses a VSAM file, which cannot even be read currently on VM/CMS. I created a QSAM extract file from RMM and a QSAM Index file, (that contained the tape volser and record number in the extract file), so the Index could be read from VM/CMS to calculate the TTR to use with the extract file. The extract and Index file are updated every 30 minutes so the data is not live like it was with the TMC. It's a kludge, but what else can you do when IBM doesn't support their operating systems equally and they don't understand the concept of sharing data between different systems. -- Dale R. Smith Just out of curiosity, what about writing an STC on z/OS to do the RMM command necessary to get the information you need. In addition, write a CMS program which uses some communication method (TCPIP? Perhaps HTTP protocol) to run the command to z/OS. I don't know how well that would work, in terms of response time. Perhaps, if on the same CEC, you could use a HiperSocket connection rather than actually hitting the LAN via an OSA (or other). Or maybe even do an LU0, LU2, or LU6 connection. If you actually *like* VTAM. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using NOTE and POINT simulation macros on CMS?
On Tue, 7 Aug 2012 11:24:58 -0500, McKown, John john.mck...@healthmarkets.com wrote: Just out of curiosity, what about writing an STC on z/OS to do the RMM command necessary to get the information you need. In addition, write a CMS program which uses some communication method (TCPIP? Perhaps HTTP protocol) to run the command to z/OS. I don't know how well that would work, in terms of response time. Perhaps, if on the same CEC, you could use a HiperSocket connection rather than actually hitting the LAN via an OSA (or other). Or maybe even do an LU0, LU2, or LU6 connection. If you actually *like* VTAM. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com I thought of doing something like that, but of course there was not enough time to create/test/implement such a solution. The systems are on different CECs and I probably would have gone with a TCPIP solution in phase two, if I was still there. Since I no longer work for the company that had the original TMS code or the company that they outsourced to, (where I wrote the RMM code), or the company that I was contracting with for the outsourcer after they released me, I doubt that it will ever happen. :-) I'm sure it would of have been some fun code to write! -- Dale R. Smith -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using NOTE and POINT simulation macros on CMS?
So presumably when the control records were created, CA software did a NOTE of the TTR of the beginning of each volser range and saved the results of the NOTE in the control record. This saved NOTE value was the base to which the offset, calculated from the user's input, was added. Bill Fairchild Programmer Rocket Software 408 Chamberlain Park Lane • Franklin, TN 37069-2526 • USA t: +1.617.614.4503 • e: bfairch...@rocketsoftware.com • w: www.rocketsoftware.com It's actually a relative block number, not a TTR. The TMS TMC file was originally fixed length 256 byte records that were unblocked. The first several records contained control information, (like volser ranges and relative block numbers), and other stuff, (like the relative block number for the start of the DSNB records). Let's say there were 3 control records in the TMC. That would mean the record for volser 01 would be the fourth record/block so the relative block offset would be 3. Volser 10 would be record/block 10 plus offset 3 so the volser record would be in the record/block 13, which would then be converted into a TTR value based on how many 256 byte blocks there are in a track. Years later, TMS was enhanced to support having the TMC file blocked so now you had to compute the offset into the block to get the correct volser record after reading the correct block. -- Dale R. Smith -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using NOTE and POINT simulation macros on CMS?
On 2012-08-07 11:11, Bill Fairchild wrote: So presumably when the control records were created, CA software did a NOTE of the TTR of the beginning of each volser range and saved the results of the NOTE in the control record. This saved NOTE value was the base to which the offset, calculated from the user's input, was added. Ah! Something that can't be converted to PDSE. Well, maybe you could if you kept it open all the time. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using NOTE and POINT simulation macros on CMS?
Can't keep TTRs in a PDS either because members move around when compressed or replaced. The CA-1 TMC is basically a fixed length BDAM file without keys. If it were to be replaced, I would expect either a VSAM RRDS or LDS. If an LDS, I wonder if it could be memory mapped into a common 64 bit addressable area. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Tuesday, August 07, 2012 3:01 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Using NOTE and POINT simulation macros on CMS? On 2012-08-07 11:11, Bill Fairchild wrote: So presumably when the control records were created, CA software did a NOTE of the TTR of the beginning of each volser range and saved the results of the NOTE in the control record. This saved NOTE value was the base to which the offset, calculated from the user's input, was added. Ah! Something that can't be converted to PDSE. Well, maybe you could if you kept it open all the time. -- gil -- 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: Using NOTE and POINT simulation macros on CMS?
At 22:24 -0500 on 08/06/2012, Dale R. Smith wrote about Re: Using NOTE and POINT simulation macros on CMS?: The first sentence under the NOTE Macro in the MVS/XA Reference contains this info: The NOTE macro instruction causes the system to return the position of the last block read from or written into a data set. All input and output operations using the same data control block must be tested for completion before the NOTE macro instruction is issued. So it sounds like the NOTE Macro will only work after a Read or a Write has been done to the dastaset, not after an OPEN Macro. If the system knows where the first record in the file is so that the first READ done after the OPEN will read it, it seems to me that a NOTE done prior to that READ but just after the OPEN should return the location of that first record. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using NOTE and POINT simulation macros on CMS?
On 2012-08-07 19:10, Robert A. Rosenberg wrote: At 22:24 -0500 on 08/06/2012, Dale R. Smith wrote about Re: Using NOTE and POINT simulation macros on CMS?: So it sounds like the NOTE Macro will only work after a Read or a Write has been done to the dastaset, not after an OPEN Macro. If the system knows where the first record in the file is so that the first READ done after the OPEN will read it, it seems to me that a NOTE done prior to that READ but just after the OPEN should return the location of that first record. Errr... no. After the first READ, it returns the location of the first record. Before the first read, for consistency, it would need to return the location of something before the first record. There is no such thing. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using NOTE and POINT simulation macros on CMS?
In 77142d37c0c3c34da0d7b1da7d7ca343415c8...@nwt-s-mbx2.rocketsoftware.com, on 08/07/2012 at 01:08 PM, Bill Fairchild bfairch...@rocketsoftware.com said: How did you successfully use POINT without having first done a NOTE so that the POINT knows where to POINT? Some obvious ways that it can be done: 1. Calculate the TTR 2. Extract the TTR from a directory entry or from a record; of course, some other program would have had to do a NOTE and a STOW or WRITE. Note that IEBCOPY compress will update note lists and the TTR section of a directory entry. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using NOTE and POINT simulation macros on CMS?
Shmuel Metz , Seymour J. wrote: In 501aea52.7000...@dignus.com, on 08/02/2012 at 05:00 PM, Thomas David Rivers riv...@dignus.com said: Then - reading the file to the end (with regular BSAM READ+CHECK) Does your code work in z/OS? What DCB bits are you resetting after EOF? Just to follow-up on the questions raised... The code does work on z/OS. The NOTE is performed before the first READ, it is performed immediately after the OPEN. This is been working fine since the era of OS/390 2.7... The scenario that operates (perhaps by fortune?) on z/OS is: BSAM OPEN NOTE to return the TTR at the start of the file (which kinda makes sense if the DD happens to be pointing at a PDS member, for example) READ+CHECK... READ+CHECK... READ+CHECK... until the EOD exit is driven POINT back to the beginning of the file using the TTR returned in the NOTE above READ+CHECK... READ+CHECK... READ+CHECK... until the EOD exit is drive There is no adjusting of DCB bits after the first EOD is driven. The sequences of READ+CHECKs return the same blocks (bytes) each time. But, when this exact code is done on CMS, the 2nd sequence of READ+CHECKs immediately drives EOD. Perhaps there _should_ be a resetting of a bit in the DCB? Also - the NOTE/POINT on z/OS is TYPE=REL, but that isn't listed as supported in the CMS simulation macros.. so for CMS there is no TYPE specified. We don't particular care _what_ the TTR returned might be, just that we remember it for returning back to the start of the file without suffering a new OPEN, etc... - Thanks! - - Dave Rivers - -- riv...@dignus.comWork: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using NOTE and POINT simulation macros on CMS?
On Fri, 3 Aug 2012 06:42:54 -0400, Shmuel Metz (Seymour J.) wrote: Are you referring to the OS rules or to the OS simulation in CMS? NOTE has always been valid in OS after a checked write. I stand corrected. READ or WRITE. But IIRC, the OP said he did NOTE before either I/O operation. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Using NOTE and POINT simulation macros on CMS?
I'm having some issues with using the OS Simulation macros NOTE and POINT under VM/CMS. I've been scouring documentation to try and discover just what the CMS differences are... But, at the moment, I'm trying to simply do a BSAM OPEN (for READ)... Then, a NOTE to record the starting TTR of the file... Then - reading the file to the end (with regular BSAM READ+CHECK) Then, a POINT to return to the beginning of the file, using the TTR retrieved from just after the OPEN (with +1 added because the NOTE occurs after OPEN but before any READ.) Then - try and READ the blocks again... What I'm seeing is that the NOTE returns something that looks like a TTR. Then, the READs+CHECKs occur that read the file. The POINT supposedly returns us to the begining, but the next READ gets EOD. Clearly - the POINT hasn't worked. And, as you might expect - this approach works just great on z/OS. Does anyone know of any vagaries with the OS simulation of NOTE/POINT? I did see that you can't code TYPE=REL (or TYPE=anything for that matter.) But, I don't really care what the block address is... just that it is the valid block address for the beginning of the file. Thanks for any pointers! - Dave Rivers - -- riv...@dignus.comWork: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using NOTE and POINT simulation macros on CMS?
I don't know, but isn't it necessary to reset the DCBOREOF bit in the DCB field DCBORBYT? I would have thought that even z/OS would need that. But I've never tried to READ once I had gotten an EOF. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using NOTE and POINT simulation macros on CMS?
OS simulation is dreadfully deficient. On 2012-08-02 15:00, Thomas David Rivers wrote: Then, a POINT to return to the beginning of the file, using the TTR retrieved from just after the OPEN (with +1 added because the NOTE occurs after OPEN but before any READ.) I believe that NOTE is specified to work only after a READ has been issued (but I haven't RTFM lately), and all outstanding READs have been CHECKed. And, as you might expect - this approach works just great on z/OS. Eons ago it used not to work for me. Does anyone know of any vagaries with the OS simulation of NOTE/POINT? OS simulation was implemented only to the extent necessary to support (some of) the supported utilities. For example, PDS member statistics (the user info area) were deemed unnecessary and not implemented. ISPF/VM goes to outrageous gyrations with side-files to simulate them. Long ago, a co-worker said VM would do well to abandon CMS and support MVT proper in a VM. But he's an acknowledged OS partisan. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using NOTE and POINT simulation macros on CMS?
paulgboul...@aim.com (Paul Gilmartin) writes: OS simulation was implemented only to the extent necessary to support (some of) the supported utilities. For example, PDS member statistics (the user info area) were deemed unnecessary and not implemented. ISPF/VM goes to outrageous gyrations with side-files to simulate them. Long ago, a co-worker said VM would do well to abandon CMS and support MVT proper in a VM. But he's an acknowledged OS partisan. cp67/cms group split off from science center, moved to the 3rd flr absorbing the ibm boston programming center (had been responsible for lots of stuff included cps ... converstational programming system that ran under mvt supporting both conversational basic PLI) ... and then morphing into vm370/cms group and growing fast. it outgrew the 3rd floor and moved out to the old sbc bldg in burlington mall (sbc going to control data in legal settlement). some of the people significantly enhanced o/s simulation ... at least doubling the amount of cms o/s simulation code .. creating joke that it simulated mvt much better than mvs (for less than 1% the code). provided o/s simulation both on cms filesystem as well on os/360 formated disks. now in the aftermath of future system failure ... some past posts http://www.garlic.com/~lynn/submain.html#futuresys and mad rush to get stuff back into 370 product pipelines (lots of 370 efforts had been killed off and/or at least suspended during future system period). part was qd 3033 ... remapping 168-3 logic to faster chips overlapped with 3081 which was some left-over pieces from future system effort. some more detail here http://www.jfsowa.com/computer/memo125.htm also head of POK convinced head of POK convinced corporate to kill off vm370, shutdown the burlington mall group, and move all the people to POK to work on mvs/xa (or otherwise mvs/xa wouldn't meet its ship date). they were woking on not letting vm370 group know until the last possible minute to minimize the number that might be able to escape the move. unfortantely the information leaked early, there was big witch hunt for the source of the leak ... and numerous excaped to various vendors in the area (joke that as result, head of POK was one of the major contributors to dec vax/vms). in all of the commotion, the o/s simmulation enhancements evaporate ... never to be seen again. endicott eventually managed to salvage the vm370/cms product mission, but had to reconstitute a development group from scratch. some amount of code quality comments on vmshare during the period reflects growing the new group. http://vm.marist.edu/~vmshare/ later when company declared CMS strategic interactive platform (and abondoned TSO for that purpose) ... there was quite a bit of efforts getting CMS running on MVS. it was operational but because of all sorts of structural issues in MVS ... it would never achieve human factors and interactive characteristics. -- virtualization experience starting Jan1968, online at home since Mar1970 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using NOTE and POINT simulation macros on CMS?
The Strategic Interactive Platform: On Thu, 2 Aug 2012 19:44:25 -0400, Anne Lynn Wheeler wrote: ... later when company declared CMS strategic interactive platform (and abondoned TSO for that purpose) ... there was quite a bit of efforts getting CMS running on MVS. it was operational but because of all sorts of structural issues in MVS ... it would never achieve human factors and interactive characteristics. Somehow this brings to mind Unix System Services (USS). -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
