Re: Which fonts are being actually used?
retired mainframer wrote: :: As far as I know RACF provides sufficient granularity to define access controlled resources for these purposes, so I think it'd work well. :: Via access using program modules, yes. The last time it was discussed on RACF-L, there was no RACF processing at the member level. Did 2.1 add something new? Not AFAIK for 2.1. You're correct about member level. But I should have added in my comment that access to datasets via program modules is via WHEN(PROGRAM(mod)) in PERMIT statement. AFAIK fonts are not in program modules, but in members and no specific access checks to members are available unless you use a RYO checks. If the OP wants to checks font members, AFAIK, for now the OP should check access to whole datasets. Sorry for confusing you, but you have a good point. Many thanks! Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
SL SA and range parameter
I have attempted to set a storage alteration PER trap. I was interested in several 4 byte areas distributed across maybe 2 pages. My intention was to disable SA monitoring for everything except those 4 byte areas, similar to the way it is described for IF traps: SL SET,SA,D,ASIDSA=SA,JOBNAME=,RA=(1E92D2A0,1E92E4A8),A=TRACE, TD=(STD,REGS,1E92D2A0,+8,1E92D4A0,+8,1E92D6A0,+8),id=bn1,e IEE727I SLIP TRAP ID=BN1 SET SL SET,SA,D,ASIDSA=SA,JOBNAME=,RA=(1E92D2A8,1E92D49F),A=IGNORE, ID=BN2,E IEE739I RANGEPARAMETER IGNORED FOR SLIP ID=BN2 Am I getting this wrong or is this actually not supported? Any hint will be appreciated. Barbara ps: I ended up with sa-monitoring the full range and only tracing the fields I was interested in. I get a lot of false (uninteresting) entries that way. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Allocating file in Rex exec
:: -Original Message-
:: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
:: Behalf Of Micheal Butz
:: Sent: Tuesday, March 25, 2014 6:50 PM
:: To: IBM-MAIN@LISTSERV.UA.EDU
:: Subject: Allocating file in Rex exec
::
:: Hi
::
:: I am allocating a dataset in a Rex exec using the following syntax
::
:: Alloc fi(myddnam) da('my.pds.name(member)') shr
::
:: I get an error routine not found
Does your exec issue the ADDRESS TSO instruction?
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Support is ending for Windows XP - Microsoft Windows
W dniu 2014-03-26 04:54, Ed Gould pisze: On Mar 25, 2014, at 5:55 PM, Joel C. Ewing wrote: On 03/25/2014 04:50 PM, R.S. wrote: W dniu 2014-03-25 21:41, Ed Gould pisze: I have friends who bought a new PC and it came with windows 8. They went out and bought a license for XP and installed XP. People are doing this widespread as WINDOWS 8 (and 7 apparently) are HATED. And the relationship to the IBM-MAIN topic is ? Maybe they are still using XP systems for TN3270 sessions to a mainframe. Then keystroke capture malware on their un-maintained and compromised XP systems could compromise mainframe logon security and mainframe data. Joel: Thanks. I try not to pay attention to the rude types. Now you are rude type. Oh, what was your point about WIn XP? What was the value added for the group? Relationship to mainframes? rhetorical Are you able to explain it? -- Radoslaw Skorupka Lodz, Poland --- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorized to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. mBank S.A. z siedzib w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: kont...@mbank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. Wedug stanu na dzie 01.01.2014 r. kapita zakadowy mBanku S.A. (w caoci wpacony) wynosi 168.696.052 zote. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Allocating file in Rex exec
On Wed, 26 Mar 2014 00:30:31 -0700, retired mainframer wrote:
::
:: I am allocating a dataset in a Rex exec using the following syntax
::
:: Alloc fi(myddnam) da('my.pds.name(member)') shr
::
:: I get an error routine not found
Does your exec issue the ADDRESS TSO instruction?
Hmmm...
o If the EXEC was started under TSO, ADDRESS TSO is the default;
probably unnecessary.
o If the EXEC was started other than under TSO (IRXJCL, UNIX), ADDRESS
TSO doesn't work. Unfortunately, the ADDRESS TSO instruction appears
to work. However, the next command fails with RC=-3.
-- gil
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Allocating file in Rex exec
On Wed, 26 Mar 2014 13:22:39 +0800, David Crayford wrote: Oops! I did a Shmuel; I followed up without reading ahead to see that I was largely repeating your answer. Shame on you :^) Damn I love this list sometimes. Shane ... -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JFCB LBI Blocksize
Interesting: JFCB appears in its entirety in SMF 14 and 15: I extract things like member name from it in my code. I'm wondering how to get the LBI Blksize from SMF 14 / 15. Maybe I can't. If I figure it out I'll try to write it up (or point to any existing write up). Cheers, Martin Martin Packer, zChampion, Principal Systems Investigator, Worldwide Banking Center of Excellence, IBM +44-7802-245-584 email: martin_pac...@uk.ibm.com Twitter / Facebook IDs: MartinPacker Blog: https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker From: Mike Schwab mike.a.sch...@gmail.com To: IBM-MAIN@listserv.ua.edu Date: 25/03/2014 21:04 Subject:Re: JFCB LBI Blocksize Sent by:IBM Mainframe Discussion List IBM-MAIN@listserv.ua.edu http://pic.dhe.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ibm.zos.r12.idad400%2Fblksz.htm Do not use the BLKSIZE field in the DCB. The system uses it. Use the BLKSIZE field in the DCBE. For more information about DCBE field descriptions see z/OS DFSMS Macro Instructions for Data Sets. http://pic.dhe.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ibm.zos.r12.idad500%2Fdcbem.htm 28(1C) 4 DCBEBLKSI BLKSIZE coded on DCBE macro or, if BLKSIZE=0 was coded, value set by OPEN. After OPEN, this field is valid only if OPEN set DCBESLBI on. On Tue, Mar 25, 2014 at 3:12 PM, Chris Cantrell chris.cantr...@palmettogba.com wrote: I have a COBOL program which flows through MVS storage areas to get the DSN, VOLSERs, etc. for any open DD. I am currently getting the LRECL and BLOCKSIZE from the JFCB area. I always get the LRECL. However, for LBI files ( 32k blocksize) I always get zero for the BLOCKSIZE. This doesn't surprise me because the field in the JFCB is only 2 bytes long. Does anyone know how I would go about getting the larger block size? Thanks! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Allocating file in Rex exec
Micheal Butz wrote:
I am allocating a dataset in a Rex exec using the following syntax
Rex, uhhmmm, sorry, Michael, it is REXX, not Rex. :-)
Alloc fi(myddnam) da('my.pds.name(member)') shr
Is thus litteraly so (copy/paste intact) or did you redacted the actual dataset
and member name?
I have two live examples of Allocation statements in my REXX programs:
ALLOC DA('TSOID.TMON.REPORT(INPUT)') F(INVOER) SHR REUSE
(HLQ slightly renamed for posting)
Note: Double Quote (One Character) before ALLOC and again after REUSE
Note: Single Quote before dataset and again after member
or
ALLOK:
STRING = 'ALLOC DA('''DSN''') F(INVOER) SHR REUSE'
INTERPRET STRING
RETURN
Where DSN has been pre-populated with a full dataset name (and optionally a
member name too, it depends)
Note: Single Quote (x'7D') and then Double Quote (One Character, x'7F') before
ALLOC
Note: Three Single Quotes before DSN and also Three Single Quotes after DSN.
Last: Double Quote (One Character) and Single Quote after REUSE.
I get an error routine not found
Please post it! We're not going anywhere without it!
Groete / Greetings
Elardus Engelbrecht
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JFCB LBI Blocksize
Hi Martin, SMF14LBS has the LBI BLKSIZE in SMF14/15. Best Regards, Yifat Oren -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Martin Packer Sent: Wednesday, March 26, 2014 10:19 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JFCB LBI Blocksize Interesting: JFCB appears in its entirety in SMF 14 and 15: I extract things like member name from it in my code. I'm wondering how to get the LBI Blksize from SMF 14 / 15. Maybe I can't. If I figure it out I'll try to write it up (or point to any existing write up). Cheers, Martin Martin Packer, zChampion, Principal Systems Investigator, Worldwide Banking Center of Excellence, IBM +44-7802-245-584 email: martin_pac...@uk.ibm.com Twitter / Facebook IDs: MartinPacker Blog: https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker From: Mike Schwab mike.a.sch...@gmail.com To: IBM-MAIN@listserv.ua.edu Date: 25/03/2014 21:04 Subject:Re: JFCB LBI Blocksize Sent by:IBM Mainframe Discussion List IBM-MAIN@listserv.ua.edu http://pic.dhe.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ibm.zos.r 12.idad400%2Fblksz.htm Do not use the BLKSIZE field in the DCB. The system uses it. Use the BLKSIZE field in the DCBE. For more information about DCBE field descriptions see z/OS DFSMS Macro Instructions for Data Sets. http://pic.dhe.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ibm.zos.r 12.idad500%2Fdcbem.htm 28(1C) 4 DCBEBLKSI BLKSIZE coded on DCBE macro or, if BLKSIZE=0 was coded, value set by OPEN. After OPEN, this field is valid only if OPEN set DCBESLBI on. On Tue, Mar 25, 2014 at 3:12 PM, Chris Cantrell chris.cantr...@palmettogba.com wrote: I have a COBOL program which flows through MVS storage areas to get the DSN, VOLSERs, etc. for any open DD. I am currently getting the LRECL and BLOCKSIZE from the JFCB area. I always get the LRECL. However, for LBI files ( 32k blocksize) I always get zero for the BLOCKSIZE. This doesn't surprise me because the field in the JFCB is only 2 bytes long. Does anyone know how I would go about getting the larger block size? Thanks! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- 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: Support is ending for Windows XP - Microsoft Windows
Radoslaw Skorupka wrote: And the relationship to the IBM-MAIN topic is ? and Relationship to mainframes? My opinion: Some z/OS systems are blocked to access IBM sites for PTFs, etc. WinXP placed between outside internet and z/OS can then be used to do transfers or browsing IBM websites (and library server too). So far, at least for SP3 (WinXP 32bit), it was proved stable enough. Some of our users are [still !!!] using vendor 3270 emulators which are still working on WinXP, not on newer micro$oft toys. Those users need to upgrade really fast because of SSL issues. ;-) BTW: on some of our Win7 (64bit) laptops we have problems with some vendors 3G cards. That cards are working 100% on WinXP (32bit and 64bit) and Win7 (32bit). We use 3G cards to access z/OS when not in office. So, it is about stability, relability, etc. Your usual FUD... ;-D Oh, BTW, I don't know of anyone here who is using Win8. Just my badly eroded rusted 2 cents... Groete / Greetings Elardus Engelbrecht ( Climate Change? Nah, make it Climate Confusion! ;-D ) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Support is ending for Windows XP - Microsoft Windows
W dniu 2014-03-26 10:01, Elardus Engelbrecht pisze: Radoslaw Skorupka wrote: And the relationship to the IBM-MAIN topic is ? and Relationship to mainframes? My opinion: Some z/OS systems are blocked to access IBM sites for PTFs, etc. WinXP placed between outside internet and z/OS can then be used to do transfers or browsing IBM websites (and library server too). So far, at least for SP3 (WinXP 32bit), it was proved stable enough. Some of our users are [still !!!] using vendor 3270 emulators which are still working on WinXP, not on newer micro$oft toys. Those users need to upgrade really fast because of SSL issues. ;-) BTW: on some of our Win7 (64bit) laptops we have problems with some vendors 3G cards. That cards are working 100% on WinXP (32bit and 64bit) and Win7 (32bit). We use 3G cards to access z/OS when not in office. So, it is about stability, relability, etc. Your usual FUD... ;-D Oh, BTW, I don't know of anyone here who is using Win8. Just my badly eroded rusted 2 cents... Groete / Greetings Elardus Engelbrecht ( Climate Change? Nah, make it Climate Confusion! ;-D ) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Elardus, I know people (including my humble person) using Win 9x far after it was out of support. Some of them used the PC to connect to mainframe. So? I just dropped my 3174's - they had no support contract for 10+ years. I have/had some equipment or software which doesn't work with newer systems. For example, PCOMM 5.8.x installation is blocked by Win7 (wih some service, AFAIK vanilla Win7 does not block it). However it's still PC environment. There is no scare to use unsupported system especially the support does not prevent you form being hacked, support does not fix new holes, all the holes exist now (even as uknown). Last but not least: there are closed system, like laptop inside HDS dasd box or PC inside EMC dasd box. Sometimes they are really ancient, but completely unconnected to rest of the world with little chance to have new (to new to be supported) hardware. And this is also not related to the mainframe itself ;-) I have no objection for discussion about weather report for next Share (although I've never been on any), or even offshore economy.. ;-) It's just off-topic. I just wanted to point out two things: 1. Win XP EOS is not related to mainframes. 2. The EOS date is not death date. After the EOS date all the WinXP won't stop working or get hacked, or start claiming 2+2=5. Last, but not least, good advice to Win8 haters: Try to use Classic Shell freeware. I did it on my Win7 and it looks like Windows 98 ;-))) I spent a lt of time on Win7 customization and now I see no big difference between Win7 and WinXP (I use both on different machines) BTW: I sill use IBM Bookreader (this 16-bit, for Win 3.1) on my Win7 32-bit. . -- Radoslaw Skorupka Lodz, Poland --- Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorized to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: kont...@mbank.pl Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2014 r. kapitał zakładowy mBanku S.A. (w całości wpłacony) wynosi 168.696.052 złote. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the
Re: JFCB LBI Blocksize
Thanks Yifat! That should be particularly easy to extract. Cheers, Martin Martin Packer, zChampion, Principal Systems Investigator, Worldwide Banking Center of Excellence, IBM +44-7802-245-584 email: martin_pac...@uk.ibm.com Twitter / Facebook IDs: MartinPacker Blog: https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker From: Yifat Oren yi...@tmachine.com To: IBM-MAIN@listserv.ua.edu Date: 26/03/2014 08:51 Subject:Re: JFCB LBI Blocksize Sent by:IBM Mainframe Discussion List IBM-MAIN@listserv.ua.edu Hi Martin, SMF14LBS has the LBI BLKSIZE in SMF14/15. Best Regards, Yifat Oren -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Martin Packer Sent: Wednesday, March 26, 2014 10:19 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JFCB LBI Blocksize Interesting: JFCB appears in its entirety in SMF 14 and 15: I extract things like member name from it in my code. I'm wondering how to get the LBI Blksize from SMF 14 / 15. Maybe I can't. If I figure it out I'll try to write it up (or point to any existing write up). Cheers, Martin Martin Packer, zChampion, Principal Systems Investigator, Worldwide Banking Center of Excellence, IBM +44-7802-245-584 email: martin_pac...@uk.ibm.com Twitter / Facebook IDs: MartinPacker Blog: https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker From: Mike Schwab mike.a.sch...@gmail.com To: IBM-MAIN@listserv.ua.edu Date: 25/03/2014 21:04 Subject:Re: JFCB LBI Blocksize Sent by:IBM Mainframe Discussion List IBM-MAIN@listserv.ua.edu http://pic.dhe.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ibm.zos.r 12.idad400%2Fblksz.htm Do not use the BLKSIZE field in the DCB. The system uses it. Use the BLKSIZE field in the DCBE. For more information about DCBE field descriptions see z/OS DFSMS Macro Instructions for Data Sets. http://pic.dhe.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ibm.zos.r 12.idad500%2Fdcbem.htm 28(1C) 4 DCBEBLKSI BLKSIZE coded on DCBE macro or, if BLKSIZE=0 was coded, value set by OPEN. After OPEN, this field is valid only if OPEN set DCBESLBI on. On Tue, Mar 25, 2014 at 3:12 PM, Chris Cantrell chris.cantr...@palmettogba.com wrote: I have a COBOL program which flows through MVS storage areas to get the DSN, VOLSERs, etc. for any open DD. I am currently getting the LRECL and BLOCKSIZE from the JFCB area. I always get the LRECL. However, for LBI files ( 32k blocksize) I always get zero for the BLOCKSIZE. This doesn't surprise me because the field in the JFCB is only 2 bytes long. Does anyone know how I would go about getting the larger block size? Thanks! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- 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 Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Support is ending for Windows XP - Microsoft Windows
Radoslaw Skorupka wrote: I know people (including my humble person) using Win 9x far after it was out of support. Some of them used the PC to connect to mainframe. So? I just dropped my 3174's - they had no support contract for 10+ years. I have/had some equipment or software which doesn't work with newer systems. For example, PCOMM 5.8.x installation is blocked by Win7 (wih some service, AFAIK vanilla Win7 does not block it). It reminds me of those years where I was asked to write a Turbo Pascal program to interact with OS/390 so datasets could be XMITted to stiffies for my users. All the while when Win98 and FTP were available. Last but not least: there are closed system, like laptop inside HDS dasd box or PC inside EMC dasd box. Sometimes they are really ancient, but completely unconnected to rest of the world with little chance to have new (to new to be supported) hardware. And this is also not related to the mainframe itself ;-) Same with out of support OS/2 used in one of our robots handling 3490 cartridges. I have no objection for discussion about weather report for next Share (although I've never been on any), or even offshore economy.. ;-) It's just off-topic. I just read them for fun. I just wanted to point out two things: 1. Win XP EOS is not related to mainframes. 2. The EOS date is not death date. After the EOS date all the WinXP won't stop working or get hacked, or start claiming 2+2=5. Agreed. If 2+2 is 5, then we will get welcome rain. ;-D Last, but not least, good advice to Win8 haters: Try to use Classic Shell freeware. I did it on my Win7 and it looks like Windows 98 ;-))) Hmm, today I learned something new. Thanks! I still have a Pentium 450 with Win98 to play ancient DOS games. Space Quest I, II, etc. are waiting for me. ;-) I spent a lt of time on Win7 customization and now I see no big difference between Win7 and WinXP (I use both on different machines) Regedit (win7+winxp) is my friend and enemy. Friend, because of my absolute insane hacking. Enemy, because I had to do format+clean install because of insane hacking. ;-D BTW: I sill use IBM Bookreader (this 16-bit, for Win 3.1) on my Win7 32-bit. I'm using IBM SoftCopy Librarian v4.4 on WinXp 32 bit. Seemed you and me are practising evil ancient art of computing. ;-D Groete / Greetings Elardus Engelbrecht ( Climate Change? Nah, make it Climate Confusion! ;-D ) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SL SA and range parameter
Barbara Nitz wrote: I have attempted to set a storage alteration PER trap. I was interested in several 4 byte areas distributed across maybe 2 pages. My intention was to disable SA monitoring for everything except those 4 byte areas, similar to the way it is described for IF traps: On what z/OS version? SL SET,SA,D,ASIDSA=SA,JOBNAME=,RA=(1E92D2A0,1E92E4A8),A=TRACE, TD=(STD,REGS,1E92D2A0,+8,1E92D4A0,+8,1E92D6A0,+8),id=bn1,e IEE727I SLIP TRAP ID=BN1 SET Weird slippery slip, but then you have a good reason for that. ;-) SL SET,SA,D,ASIDSA=SA,JOBNAME=,RA=(1E92D2A8,1E92D49F),A=IGNORE, ID=BN2,E IEE739I RANGEPARAMETER IGNORED FOR SLIP ID=BN2 Am I getting this wrong or is this actually not supported? Any hint will be appreciated. As documented in MVS System Commands (v1.12): RANGE is not valid for error event traps. RANGE cannot be specified on an ACTION=IGNORE storage alteration PER trap. I believe this could be the reason for IEE739I. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Reflexivity (was: NJE Clarifications)
In 9607598388776077.wa.paulgboulderaim@listserv.ua.edu, on 03/25/2014 at 11:46 AM, Paul Gilmartin paulgboul...@aim.com said: A single TCP/IP stack can communicate with itself. You're still evading the question, although I'm not sure what you mean by communicate in this context[1], or why you would want it to. Can an FTP server communicate with itself? [1] Certain two TCP/IP applications using the same stack can communicate with each other, but that has nothing to do with the stack communicating with itself, just properly forwarding packets. If you are referring to two applications using the same stack, how does that differ from two applications using the same VTAM? -- 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: Doug Nadel's ISPFHTML - retired
In s4p2j9dgh6f8nhqc0vdjfhc2biva2rk...@4ax.com, on 03/25/2014 at 01:13 PM, Binyamin Dissen bdis...@dissensoftware.com said: Did not realize he was close to O100 years old I thought that retirement age was '41'x years old. -- 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: Support is ending for Windows XP - Microsoft Windows
Goodby WinXT, hello Linux! Too bad IBM dumped OS/2. Gary Gary L. Shiminsky Senior zVM/zVSE Systems Programmer Mainframe Technical Support Group Department of Information Technology State of New Hampshire 27 Hazen Drive Concord, NH 03301 603-271-1509 Fax 603-271-1516 Statement of Confidentiality: The contents of this message are confidential. Any unauthorized disclosure, reproduction, use or dissemination (either whole or in part) is prohibited. If you are not the intended recipient of this message, please notify the sender immediately and delete the message from your system. -Original Message- From: Ed Finnell efinnel...@aol.com Reply-To: IBM List IBM-MAIN@LISTSERV.UA.EDU Date: Tuesday, March 25, 2014 at 3:32 PM To: IBM List IBM-MAIN@LISTSERV.UA.EDU Subject: Support is ending for Windows XP - Microsoft Windows http://windows.microsoft.com/en-us/windows/end-support-help?ocid=xp_eos_cl ie nt -- 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: Metal C vs. HLASM - for C callable subroutine?
How much cross-platform C code do you do? With Metal C, it is possible to use cross-platform code in z/OS environments that do not allow LE. In my opinion Metal C is VERY useful. Lloyd From: Gord Tomlin gt.ibm.li...@actionsoftware.com To: IBM-MAIN@LISTSERV.UA.EDU Sent: Tuesday, March 25, 2014 11:38 PM Subject: Re: Metal C vs. HLASM - for C callable subroutine? On 2014-03-25 22:11, David Crayford wrote: I find that I rarely need Metal/C. What I do want to do is inline assembler into LE code. I have found Metal to be useful in a few situations where it is desirable to have a self-contained program with inline Assembler and no dependencies on the LE runtime. Admittedly these occasions are not that common; in my experience it's not very often that a situation presents itself where C with inline Assembler is preferable to pure Assembler. -- Regards, Gord Tomlin Action Software International (a division of Mazda Computer Corporation) Tel: (905) 470-7113, Fax: (905) 470-6507 -- 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: Which fonts are being actually used?
Since the SMF Type 42 record was enhanced to include PDS member info, maybe that might be helpful? Or maybe a product like SOFTAUDT (or whatever it is called today) might help. I am a little fuzzy on fonts and whether or not the member is actually touched to generate either a TYPE42 or other SMF data. Is it possible the fonts are loaded in storage and then use when needed? If so, the above will not work. Other than for the start of the Printer address space. Or refresh in VPS. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Elardus Engelbrecht Sent: Tuesday, March 25, 2014 11:13 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Which fonts are being actually used? retired mainframer wrote: :: As far as I know RACF provides sufficient granularity to define access controlled resources for these purposes, so I think it'd work well. :: Via access using program modules, yes. The last time it was discussed on RACF-L, there was no RACF processing at the member level. Did 2.1 add something new? Not AFAIK for 2.1. You're correct about member level. But I should have added in my comment that access to datasets via program modules is via WHEN(PROGRAM(mod)) in PERMIT statement. AFAIK fonts are not in program modules, but in members and no specific access checks to members are available unless you use a RYO checks. If the OP wants to checks font members, AFAIK, for now the OP should check access to whole datasets. Sorry for confusing you, but you have a good point. Many thanks! Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Reflexivity (was: NJE Clarifications)
On Tue, 25 Mar 2014 18:39:55 -0400, Shmuel Metz (Seymour J.) wrote: In 9607598388776077.wa.paulgboulderaim@listserv.ua.edu, on 03/25/2014 at 11:46 AM, Paul Gilmartin paulgboul...@aim.com said: A single TCP/IP stack can communicate with itself. You're still evading the question, although I'm not sure what you mean by communicate in this context[1], or why you would want it to. Can an FTP server communicate with itself? OK. An FTP server can't communicate with itself. I never said it could. I don't know why you're asking. [1] Certain two TCP/IP applications using the same stack can communicate with each other, but that has nothing to do with the stack communicating with itself, just properly forwarding packets. If you are referring to two applications using the same stack, how does that differ from two applications using the same VTAM? I don't know the NJE jargon. What is the analogue of a client from which jobs might be submitted, and which writes output to a printer, and of a server which places jobs in the spool or reads output from the spool of the system on which it runs? The complaint (however mild) was that it's relatively difficult to submit jobs via NJE to run on the local host, and relatively easy to submit them to run on a remote host. With FTP, there's no differential in difficulty. Why is it harder with NJE? Is it simply that the local host is customarily left out of the routing tables? Someone else suggested that with a /*ROUTE command it could be done. But: o Regardless how simple, this is modifying the JCL, probably making it ineligible to run on other systems until it's changed back o Does this work by routing the job to an (arbitrarily chosen) remote host which sends it back? Ugh! -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SL SA and range parameter
On what z/OS version? 1.13. As documented in MVS System Commands (v1.12): RANGE is not valid for error event traps. RANGE cannot be specified on an ACTION=IGNORE storage alteration PER trap. I believe this could be the reason for IEE739I. Since this was a PER trap, not an error event trap, I didn't worry. I have overlooked the second part, though. So what I wanted to do (only monitoring certain words in a 2 page area) is really not supported. Pity. Thanks for finding the reference, though. I had spend way more than an hour reading about the correct syntax, and the docs aren't exactly easy to read, anyway. I missed the little sentence. Barbara -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SL SA and range parameter
Barbara Nitz wrote: Since this was a PER trap, not an error event trap, I didn't worry. I have overlooked the second part, though. So what I wanted to do (only monitoring certain words in a 2 page area) is really not supported. Pity. Pity, yes. Thanks for finding the reference, though. I had spend way more than an hour reading about the correct syntax, and the docs aren't exactly easy to read, anyway. I missed the little sentence. You're most welcome, it was a big pleasure to help you. That little word 'RANGE' in IEE739I caught my unwelcome attention. ;-) But I agree, the docs could be better written. Perhaps a note to the authors to highlight this? Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Which fonts are being actually used?
I don't have access to VPS documentation, so I don't know if VPS offers a suitable exit. With PSF, I'd try with a Ressource Management exit (exit 7) which can ask to receive control when fonts are loaded. The exit would then write information about fonts being used to a data set which can be analyzed later. -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Doug Nadel's ISPFHTML - retired
On Tue, 25 Mar 2014 07:25:35 -0400, Richards, Robert B. robert.richa...@opm.gov wrote: Hank, Thanks for the heads up about Doug. I still use his tools on a daily basis. Tools such as ISRFIND, ISRDDN, and TASID to name a few. Thank you, Doug, for your contribution to ISPF's usefulness and my productivity! Bob Same here. I have had an F key mapped to VCURSOR for many years now, absolutely invaluable. Plus have appreciated his responses to my various posts on ISPF, REXX etc. Thanks -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Reflexivity (was: NJE Clarifications)
Paul Gilmartin said: Someone else suggested that with a /*ROUTE command it could be done. But: o Regardless how simple, this is modifying the JCL, probably making it ineligible to run on other systems until it's changed back o Does this work by routing the job to an (arbitrarily chosen) remote host which sends it back? Ugh! That was me, and I'm not understanding your problem. Your first bullet: /*ROUTE XEQ name/nodename vs. an IP address. If you want to run on different systems, you have to modify -something-. Unless you want to run on the system you submitted from. Then you specify /*ROUTE XEQ LOCAL, and it works from wherever you are. Your second bullet: Nothing like imagining something, and shuddering in horror at the imagined sins. Which don't exist, in this case. What am I missing in your stated requirements? Cheers,,,Steve Steven F. Conway, CISSP Hosting Services Division, Cloud Technology and Hosting Office, AO-DTS-CTHO-HSD z/OS Systems Support Phone: 703-295-1926 Mobile: 703-402-2650 steve_con...@ao.uscourts.gov -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DS6800 disk - was support is ending for Windows XP - Microsoft Windows
On Tue, 2014-03-25 at 19:51 -0300, Clark Morris wrote: Is there a follow-on software [to the DS6800 SMC] or a version supported on Linux? If not, I suspect that there should be customer requirement that the software needed for use of the DS6800s must run on supported operating systems. Since the DS6800 has been withdrawn from marketing for a handful of blue moons, I doubt that such a requirement would be taken very seriously. I'd settle for IBM offering a DS6800 replacement product. They always emphasize the affordable entry-level cost of their Z processors, but just try to find an affordable small-capacity DASD device to match. -- David Andrews A. Duda Sons, Inc. david.andr...@duda.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Allocating file in Rex exec
Micheal:
As I have mentioned and others , please provide us the actual source structure
of rexx. Its hard to help just seeing a line.
Plus your syntax is wrong …
Regards,
Scott Ford
www.identityforge.com
www.idmworks.com
From: Micheal Butz
Sent: Tuesday, March 25, 2014 9:50 PM
To: IBM Mainframe Discussion List
Hi
I am allocating a dataset in a Rex exec using the following syntax
Alloc fi(myddnam) da('my.pds.name(member)') shr
I get an error routine not found
Sent from my iPhone
--
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: Allocating file in Rex exec
This is because you used the dsname as a variable. Remove the qoutes around
the dsname and live the single ones.
It should read ad alloc f(X) DA('DSNAME') ... not '
Itschak
בתאריך 26 במרץ 2014 03:50, Micheal Butz michealb...@optonline.net כתב:
Hi
I am allocating a dataset in a Rex exec using the following syntax
Alloc fi(myddnam) da('my.pds.name(member)') shr
I get an error routine not found
Sent from my iPhone
--
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: Support is ending for Windows XP - Microsoft Windows
On Mar 26, 2014, at 2:32 AM, R.S. wrote: Now you are rude type. Oh, what was your point about WIn XP? What was the value added for the group? Relationship to mainframes? rhetorical Are you able to explain it? About as much as your entry does. Ed -- Radoslaw Skorupka Lodz, Poland --- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e- mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorized to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. mBank S.A. z siedzib w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: kont...@mbank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. Wedug stanu na dzie 01.01.2014 r. kapita zakadowy mBanku S.A. (w caoci wpacony) wynosi 168.696.052 zote. -- 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: DS6800 disk - was support is ending for Windows XP - Microsoft Windows
Rex, I am running mine on a virtual server running Server 2008 Standard SP2. The one time I opened a software call on this, IBM immediately told me I was running an unsupported configuration. They helped me with my problem, but griped the entire time. I would not look for IBM to update the Storage Manager to officially run on anything new, since DS6800 have been removed from marketing. Steve On Tue, 25 Mar 2014 20:48:28 +, Pommier, Rex rpomm...@sfgmembers.com wrote: No, but I have it on a PC front-ending my DS6800s. And from what I've been able to find, IBM doesn't officially support the DS Storage Manager for the DS6800s on anything more current than XP. So I have a question for the group. Is anybody out there running the DS Storage Manager for DS6800s on a PC with Win 7? If so, did you have any issues getting it up and running? Rex -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Tuesday, March 25, 2014 3:25 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Support is ending for Windows XP - Microsoft Windows W dniu 2014-03-25 20:32, Ed Finnell pisze: http://windows.microsoft.com/en-us/windows/end-support-help?ocid=xp_eos_clie nt I don't have Win XP on any of my LPARs. In fact I have never had any. -- Radoslaw Skorupka Lodz, Poland The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. -- 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
Ever see automatic 30-day trials for mainframe software?
It is common in the PC world for software to be offered for a 30-day trial that works automatically. You download the software, install it, and it somehow knows when it was installed and quits 30 days later unless purchased. Typically, it knows by hiding some magic file or registry entry somewhere that has the original install date. On the mainframe side, I don't think I've ever seen an automatic 30-day trial, largely because magic hidden files are of course greatly frowned upon in this space. Mainframe 30-day trials in my experience require vendor administration to generate some sort of 30-day key. Obviously, there would be advantages to a vendor if they could offer a freely-downloadable trial of mainframe software that expired automatically. No one is going to install mainframe software on a whim, but eliminating the administrative burden of issuing a 30-day key has a distinct advantage. (Please, let's for the sake of argument not digress into the are keys good or bad? debate. For certain mainframe software, keys are here to stay, like it or not, and that's a different topic.) Has anyone ever seen mainframe software that automatically expired 30 days after installation? If so, any rough idea how that worked? (Presumably, not a magic hidden file LOL.) Thanks, Charles -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Ever see automatic 30-day trials for mainframe software?
I just happen to be installing a SAS upgrade as I am writing. A (90 day) temp key is provided (with the distribution - no request needed) to support the installation (SAS used to install SAS). On/before the end of that period a regular perm key must be installed. snip Has anyone ever seen mainframe software that automatically expired 30 days after installation? If so, any rough idea how that worked? (Presumably, not a magic hidden file LOL.) /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Allocating file in Rex exec
I highly recommend editing/viewing a Rexx with Hilite On 1 (Automatic) or
14 (Rexx). In this mode, literals are one color (in my case white) and
variables a different color (in my case green). I had a very similar
problem yesterday making a pesky update to a Rexx. Coloring showed me the
error of my ways.
Once more, thank you Doug Nadel.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
jo.skip.robin...@sce.com
From: Itschak Mugzach imugz...@gmail.com
To: IBM-MAIN@LISTSERV.UA.EDU,
Date: 03/26/2014 07:21 AM
Subject:Re: Allocating file in Rex exec
Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU
This is because you used the dsname as a variable. Remove the qoutes
around
the dsname and live the single ones.
It should read ad alloc f(X) DA('DSNAME') ... not '
Itschak
בתאריך 26 במרץ 2014 03:50, Micheal Butz michealb...@optonline.net כתב:
Hi
I am allocating a dataset in a Rex exec using the following syntax
Alloc fi(myddnam) da('my.pds.name(member)') shr
I get an error routine not found
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Ever see automatic 30-day trials for mainframe software?
Charles Mills wrote: It is common in the PC world for software to be offered for a 30-day trial that works automatically. You download the software, install it, and it somehow knows when it was installed and quits 30 days later unless purchased. Typically, it knows by hiding some magic file or registry entry somewhere that has the original install date. They're also called 'nagware'. They're nagging constantly, interrupting your work, with 'buy me' prompt or something like that. Some of those software were really clever that if you adjust your clock, they will disable themselves properly... On the mainframe side, I don't think I've ever seen an automatic 30-day trial, largely because magic hidden files are of course greatly frowned upon in this space. Mainframe 30-day trials in my experience require vendor administration to generate some sort of 30-day key. True. You get also temp keys for DRP or switch over to new footprint. Whatever it is, you have to involve your vendor. Obviously, there would be advantages to a vendor if they could offer a freely-downloadable trial of mainframe software that expired automatically. No one is going to install mainframe software on a whim, but eliminating the administrative burden of issuing a 30-day key has a distinct advantage. Indeend! I really would like that, but over the years I never see such animals. It is either licensed (vendor supplied) or freebies at your own extreme risk (CBTTAPE for example). ... For certain mainframe software, keys are here to stay, like it or not, and that's a different topic. The more expensive the software, the more weird are the keys and the [slow, slower, slowest] administration of it. ;-D Has anyone ever seen mainframe software that automatically expired 30 days after installation? If so, any rough idea how that worked? (Presumably, not a magic hidden file LOL.) No. Never. But I wonder about IBM-MAIN members own software. How are THEY working with licensing and key management? Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Ever see automatic 30-day trials for mainframe software?
The CICS Betas released over the last few releases (I believe betas were/are available for 4.2, 5.1 5.2) have built in expiry dates. IBM states that the betas Contain a disabling device that will prevent it from being used after the test period ends. http://www-01.ibm.com/software/htp/cics/openbeta/ -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Charles Mills Sent: Wednesday, March 26, 2014 10:36 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Ever see automatic 30-day trials for mainframe software? It is common in the PC world for software to be offered for a 30-day trial that works automatically. You download the software, install it, and it somehow knows when it was installed and quits 30 days later unless purchased. Typically, it knows by hiding some magic file or registry entry somewhere that has the original install date. On the mainframe side, I don't think I've ever seen an automatic 30-day trial, largely because magic hidden files are of course greatly frowned upon in this space. Mainframe 30-day trials in my experience require vendor administration to generate some sort of 30-day key. Obviously, there would be advantages to a vendor if they could offer a freely-downloadable trial of mainframe software that expired automatically. No one is going to install mainframe software on a whim, but eliminating the administrative burden of issuing a 30-day key has a distinct advantage. (Please, let's for the sake of argument not digress into the are keys good or bad? debate. For certain mainframe software, keys are here to stay, like it or not, and that's a different topic.) Has anyone ever seen mainframe software that automatically expired 30 days after installation? If so, any rough idea how that worked? (Presumably, not a magic hidden file LOL.) Thanks, Charles -- 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: Metal C vs. HLASM - for C callable subroutine?
David, I agree - this would be GREAT. I've asked IBM about this and I think that at the time they said that it was a known requirement. Will be asking again next week. In the meantime, I would suggest that all interested submit your requirements. What we do (a lot) is to write XPLINK assembler leaf routines and call them from (non-metal) C/C++. It works better for 31-bit, since you can use the XPLINK stack for your 31-bit work area. For 64-bit or bi-amodal assembler, we end up using __malloc31() and passing the workarea as a pointer, which IMO is preferable to getting OS memory off the heap. But inlining in non-Metal wouldn't help with that. Kirk Wolf Dovetailed Technologies http://dovetail.com On Tue, Mar 25, 2014 at 10:54 PM, David Crayford dcrayf...@gmail.comwrote: On 26/03/2014 11:38 AM, Gord Tomlin wrote: On 2014-03-25 22:11, David Crayford wrote: I find that I rarely need Metal/C. What I do want to do is inline assembler into LE code. I have found Metal to be useful in a few situations where it is desirable to have a self-contained program with inline Assembler and no dependencies on the LE runtime. Admittedly these occasions are not that common; in my experience it's not very often that a situation presents itself where C with inline Assembler is preferable to pure Assembler. I can think of plenty of situations, the most common being synchronization primitives for multi-theaded code. They is no built-in for a membar in z/OS C/C++ which is simple to code in gcc. #define eieio() asm volatile(bcr 15,0 : : : memory) If I had that I can then port libraries like boosts lock free http://www.boost.org/doc/libs/1_55_0/doc/html/lockfree.html. There's no such thing as Metal/C++ ;). -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Support is ending for Windows XP - Microsoft Windows
On 14Mar26:1105-0500, Dan Skomsky wrote: A little OS/2 experience with IBM Marketing... Back in '94-'95 we spent over $500K to port a major Public Safety system from CICS MVS to CICS OS/2. The port was very successful. But, when we went into a major presentation to demonstrate our offering, the new 90-Day-Wonder IBM Public Safety Expert blew us out of the water. All throughout the demo he used an IBM laptop running Windows 98 and stated that his group was more familiar with Windows rather than OS/2. He also stated he had no problem recommending a Microsoft based solution versus and IBM based solution. We couldn't believe it! In the days after this disaster, we were getting feedback from the attendees with a common theme, If IBM has so little faith in their own offering, why should we go out on a limb and use it? -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Staller, Allan Sent: Wednesday, March 26, 2014 10:38 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Support is ending for Windows XP - Microsoft Windows Agreed! snip Too bad IBM dumped OS/2. Well, I think everyone's forgeting IBM never had exclusive ownership of everything OS/2--that explains a lot in my mind. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Support is ending for Windows XP - Microsoft Windows
I was at SHARE a long time ago when Pat Artis slide into a chair next to me and said I just went to the Windows vs OS/2 Shootout. It was a bloodbath. Expecting the worst I asked what happened. Pat said Microsoft brought eight people to the demo and IBM brought one. OS/2 blew the doors off Windows. I always preferred OS/2 but it just goes to show that the best technology doesn't always win. Bob Shannon Rocket Software -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Ever see automatic 30-day trials for mainframe software?
Right. Good input. Thanks. I have shipped software with a hard-coded expiration date. What I am looking for is a floating expiration date that would be 30 days after installation, whether installed today or a year from today. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mullen, Patrick Sent: Wednesday, March 26, 2014 9:07 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Ever see automatic 30-day trials for mainframe software? The CICS Betas released over the last few releases (I believe betas were/are available for 4.2, 5.1 5.2) have built in expiry dates. IBM states that the betas Contain a disabling device that will prevent it from being used after the test period ends. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Ever see automatic 30-day trials for mainframe software?
On 26 March 2014 12:20, Charles Mills charl...@mcn.org wrote: Right. Good input. Thanks. I have shipped software with a hard-coded expiration date. What I am looking for is a floating expiration date that would be 30 days after installation, whether installed today or a year from today. It depends to a great extent on the nature of the product. If it contains/provides its own database of some sort, then there's no need for a magic hidden file; it can just store the key info and install date in some obscure corner of the database. Likewise, if the program is APF authorized by its nature, there are plenty of legitimate places it can store the info - most obviously in the security system, and as dataset or file metadata. But it all depends on what you're trying to accomplish. I imagine it's a matter of convenience for you and prospective customers. But if you are seriously worried about unauthorized use (say, beyond the time of a trial), then there are all sorts of other considerations that have been discussed at some length here in the past. These days even the act of hiding key and data info somewhere may provide you (in the US, at least) with a DMCA stick to threaten your customers with should they attempt to figure out where and how you've hidden things. But I'm sure you wouldn't want to even think of that. Tony H. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: STOW member list format?
On Tue, 25 Mar 2014 19:02:04 -0500, Bill Godfrey wrote: You did see that it is in the Z/OS 2.1 PDF that I mentioned, right? 380th page, page 354. http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/download/DGT3D500.pdf I found a nice example, more suited to my need, in Using Data Sets: STOWLIST DS0FList of member names for STOW DCCL8'MEMBERA' Name of member DSCL3 TTR of first record (created by STOW) DCX'23' C byte, 1 user TTRN, 4 bytes of user data DSCL4 TTRN of NOTE list ... one list entry per member (16 bytes each) Whenever MHVRCFs assigns a tracking number, I'll recommend that they provide a cross-reference. Thanks, gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Support is ending for Windows XP - Microsoft Windows
Many developers who had used OS/2 offered to rewrite any non-IBM code that was in OS/2 so IBM could at least release it as open source. IBM declined. As we all know IBM has been very good at shooting itself in the foot over the years (multiple times). There is one vendor that still sells OS/2 under the name eComStation. Gary Gary L. Shiminsky Senior zVM/zVSE Systems Programmer Mainframe Technical Support Group Department of Information Technology State of New Hampshire 27 Hazen Drive Concord, NH 03301 603-271-1509 Fax 603-271-1516 Statement of Confidentiality: The contents of this message are confidential. Any unauthorized disclosure, reproduction, use or dissemination (either whole or in part) is prohibited. If you are not the intended recipient of this message, please notify the sender immediately and delete the message from your system. -Original Message- From: David L. Craig dlc@gmail.com Reply-To: IBM List IBM-MAIN@LISTSERV.UA.EDU Date: Wednesday, March 26, 2014 at 12:17 PM To: IBM List IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Support is ending for Windows XP - Microsoft Windows Well, I think everyone's forgeting IBM never had exclusive ownership of everything OS/2--that explains a lot in my mind. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ -- 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: DS6800 disk - was support is ending for Windows XP - Microsoft Windows
While the DS6800 has been withdrawn from marketing, it has not reached end of support. Consequently, I am pretty confident IBM will continue to respond to support issues for the entire system, including the SMC, as long as it is their installation. If you install a non-IBM disk drive, I don't expect them to do much. The same if you install the SMC software on a non-IBM platform. Since the principal function of the SMC software is to configure the virtual 3390 drives, once your system is up and running you hardly ever need to use it. I wonder how many sites still have the logon password available. If the CE needs to use the SMC and it doesn't work correctly, the site shouldn't care if the cause is IBM's software or the operating system or the SMC hardware. Even if the operating system was still supported, the probability that the OS company (be it Microsoft for Windows, IBM for OS/2, whoever for Linux, etc) will produce a fix in time to solve the site's original problem is indistinguishable from zero. So it falls to the CE and IBM to come up with an alternate tool for the CE to do his job. Since both the SMC software and the OS have been working successfully for some years and they are not subject to wear and tear, concerns about the supportability of the OS seem to be so much FUD. Since the major portion of XP updates in the past few years have been for security issues, any site that has the SMC connected to an external network might want to reevaluate that. How often, and why, does someone connect to the SMC remotely? What is the cost if that is no longer possible? Why is the security exposure that was fixed on the last update (and therefore in existence for over ten years) suddenly less of an issue than the next exposure that won't be fixed? Has anyone installed malware protection on an SMC? If so, how do you keep it updated? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
The IBM Strategy
URL recently showed up in (ibm employee) linkedin group http://www.ibm.com/annualreport/2013/strategy.html The IBM Strategy: Waer remaining a new future for our clients, our industry and our company. This is how. 01: We are making markets by transforming indusries and professions with data 02: We are remaking enterprise IT for the era of cloud 03: We are enabling systems of engagement for enterprises. And we are leading by example. -- 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: Support is ending for Windows XP - Microsoft Windows
On 14Mar26:1700+, Shiminsky, Gary wrote: Many developers who had used OS/2 offered to rewrite any non-IBM code that was in OS/2 so IBM could at least release it as open source. IBM declined. Without knowledge of the Ts and Cs in the pertinent contracts between Microsoft and IBM regarding usage of Microsoft IP, it is dubious to presume IBM was simply being stupid. I would be surprised if Redmond left itself without grounds to litigate regarding any innovation by IBM that replaces any licensed IP. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Reflexivity (was: NJE Clarifications)
-Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Conway Sent: Wednesday, March 26, 2014 6:06 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Reflexivity (was: NJE Clarifications) Paul Gilmartin said: Someone else suggested that with a /*ROUTE command it could be done. But: o Regardless how simple, this is modifying the JCL, probably making it ineligible to run on other systems until it's changed back o Does this work by routing the job to an (arbitrarily chosen) remote host which sends it back? Ugh! That was me, and I'm not understanding your problem. Your first bullet: /*ROUTE XEQ name/nodename vs. an IP address. If you want to run on different systems, you have to modify -something-. Unless you want to run on the system you submitted from. Then you specify /*ROUTE XEQ LOCAL, and it works from wherever you are. I think that some of this is a real difference between the way the two protocols work. Using FTP, I can submit a given JCL deck to any host I have access to and authority to run. I can do this without making changes to the JCL itself. Localhost is a valid target for my FTP PUT. I haven't actually used NJE much, but I don't think it supports changing the NJE target from outside the JCL deck. The /*ROUTE XEQ (inside the JCL deck) is the method for specifying the target node. On the other hand, /*ROUTE XEQ LOCAL seems equivalent to an FTP open localhost, and a put of a JCL deck to JES. :) Cheers,,,Steve Steven F. Conway, CISSP Hosting Services Division, Cloud Technology and Hosting Office, AO-DTS-CTHO-HSD z/OS Systems Support Phone: 703-295-1926 Mobile: 703-402-2650 steve_con...@ao.uscourts.gov -- 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: DS6800 disk - was support is ending for Windows XP - Microsoft Windows
quote any site that has the SMC connected to an external network might want to reevaluate that /quote Therein lies the rub. At my site, the dictate has come down from on high (and not completely without merit) that any PC on the network needs to be supported. The SMC needs to be on the network in order for the phone home to work. We don't have a modem on our SMC, it is configured to send problem data across the big, bad, internet to IBM. Rex -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of retired mainframer Sent: Wednesday, March 26, 2014 12:15 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DS6800 disk - was support is ending for Windows XP - Microsoft Windows While the DS6800 has been withdrawn from marketing, it has not reached end of support. Consequently, I am pretty confident IBM will continue to respond to support issues for the entire system, including the SMC, as long as it is their installation. If you install a non-IBM disk drive, I don't expect them to do much. The same if you install the SMC software on a non-IBM platform. Since the principal function of the SMC software is to configure the virtual 3390 drives, once your system is up and running you hardly ever need to use it. I wonder how many sites still have the logon password available. If the CE needs to use the SMC and it doesn't work correctly, the site shouldn't care if the cause is IBM's software or the operating system or the SMC hardware. Even if the operating system was still supported, the probability that the OS company (be it Microsoft for Windows, IBM for OS/2, whoever for Linux, etc) will produce a fix in time to solve the site's original problem is indistinguishable from zero. So it falls to the CE and IBM to come up with an alternate tool for the CE to do his job. Since both the SMC software and the OS have been working successfully for some years and they are not subject to wear and tear, concerns about the supportability of the OS seem to be so much FUD. Since the major portion of XP updates in the past few years have been for security issues, any site that has the SMC connected to an external network might want to reevaluate that. How often, and why, does someone connect to the SMC remotely? What is the cost if that is no longer possible? Why is the security exposure that was fixed on the last update (and therefore in existence for over ten years) suddenly less of an issue than the next exposure that won't be fixed? Has anyone installed malware protection on an SMC? If so, how do you keep it updated? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: The IBM Strategy
IBM has a strategy? Wow, that's a huge leap forward from what we've seen in recent years! (Yes, I'm being snide/unfair/whatever, no need to point that out) On Wed, Mar 26, 2014 at 1:29 PM, Anne Lynn Wheeler l...@garlic.comwrote: URL recently showed up in (ibm employee) linkedin group http://www.ibm.com/annualreport/2013/strategy.html The IBM Strategy: Waer remaining a new future for our clients, our industry and our company. This is how. 01: We are making markets by transforming indusries and professions with data 02: We are remaking enterprise IT for the era of cloud 03: We are enabling systems of engagement for enterprises. And we are leading by example. -- 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 -- zMan -- I've got a mainframe and I'm not afraid to use it -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Support is ending for Windows XP - Microsoft Windows
-Original Message- From: IBM Mainframe Discussion List On Behalf Of Skip Robinson RIP Betamax. Turns out that Ralph Waldo Emerson (had to look that up) was wrong about mousetraps and the power of innovation. Or, as I often quote Leonard Woren, if you build a better mouse trap, the world will build a better mouse. If you make something idiot-proof, God will send you a better idiot. (Attribution unknown) -jc- ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Reflexivity (was: NJE Clarifications)
A job can routed for execution to another NJE node by JES command. If there happens to a SYSAFF card, the job might not run until the SYSAFF name is changed or nullified, but JES commands allow a job or its output to be sent anywhere in the network by operator command. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: Gibney, Dave gib...@wsu.edu To: IBM-MAIN@LISTSERV.UA.EDU, Date: 03/26/2014 11:03 AM Subject:Re: Reflexivity (was: NJE Clarifications) Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Conway Sent: Wednesday, March 26, 2014 6:06 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Reflexivity (was: NJE Clarifications) Paul Gilmartin said: Someone else suggested that with a /*ROUTE command it could be done. But: o Regardless how simple, this is modifying the JCL, probably making it ineligible to run on other systems until it's changed back o Does this work by routing the job to an (arbitrarily chosen) remote host which sends it back? Ugh! That was me, and I'm not understanding your problem. Your first bullet: /*ROUTE XEQ name/nodename vs. an IP address. If you want to run on different systems, you have to modify -something-. Unless you want to run on the system you submitted from. Then you specify /*ROUTE XEQ LOCAL, and it works from wherever you are. I think that some of this is a real difference between the way the two protocols work. Using FTP, I can submit a given JCL deck to any host I have access to and authority to run. I can do this without making changes to the JCL itself. Localhost is a valid target for my FTP PUT. I haven't actually used NJE much, but I don't think it supports changing the NJE target from outside the JCL deck. The /*ROUTE XEQ (inside the JCL deck) is the method for specifying the target node. On the other hand, /*ROUTE XEQ LOCAL seems equivalent to an FTP open localhost, and a put of a JCL deck to JES. :) Cheers,,,Steve -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: STOW member list format?
On Wed, 26 Mar 2014 11:42:42 -0500, Paul Gilmartin wrote: On Tue, 25 Mar 2014 19:02:04 -0500, Bill Godfrey wrote: You did see that it is in the Z/OS 2.1 PDF that I mentioned, right? 380th page, page 354. http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/download/DGT3D500.pdf I found a nice example, more suited to my need, in Using Data Sets: STOWLIST DS0FList of member names for STOW DCCL8'MEMBERA' Name of member DSCL3 TTR of first record (created by STOW) DCX'23' C byte, 1 user TTRN, 4 bytes of user data For 1 user TTRN, 4 bytes of user data, it should be X'22' DSCL4 TTRN of NOTE list ... one list entry per member (16 bytes each) Whenever MHVRCFs assigns a tracking number, I'll recommend that they provide a cross-reference. Bill -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Reflexivity (was: NJE Clarifications)
That is true, but it is still a second action required after the JCL is submitted. Issuing the command requires use of a different interface (SDSF or (E)JES). I probably should have known better than to interject in a Shmuel/Gil discussion. :) -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Skip Robinson Sent: Wednesday, March 26, 2014 11:45 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Reflexivity (was: NJE Clarifications) A job can routed for execution to another NJE node by JES command. If there happens to a SYSAFF card, the job might not run until the SYSAFF name is changed or nullified, but JES commands allow a job or its output to be sent anywhere in the network by operator command. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: Gibney, Dave gib...@wsu.edu To: IBM-MAIN@LISTSERV.UA.EDU, Date: 03/26/2014 11:03 AM Subject:Re: Reflexivity (was: NJE Clarifications) Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU -Original Message- From: IBM Mainframe Discussion List [mailto:IBM- m...@listserv.ua.edu] On Behalf Of Steve Conway Sent: Wednesday, March 26, 2014 6:06 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Reflexivity (was: NJE Clarifications) Paul Gilmartin said: Someone else suggested that with a /*ROUTE command it could be done. But: o Regardless how simple, this is modifying the JCL, probably making it ineligible to run on other systems until it's changed back o Does this work by routing the job to an (arbitrarily chosen) remote host which sends it back? Ugh! That was me, and I'm not understanding your problem. Your first bullet: /*ROUTE XEQ name/nodename vs. an IP address. If you want to run on different systems, you have to modify -something-. Unless you want to run on the system you submitted from. Then you specify /*ROUTE XEQ LOCAL, and it works from wherever you are. I think that some of this is a real difference between the way the two protocols work. Using FTP, I can submit a given JCL deck to any host I have access to and authority to run. I can do this without making changes to the JCL itself. Localhost is a valid target for my FTP PUT. I haven't actually used NJE much, but I don't think it supports changing the NJE target from outside the JCL deck. The /*ROUTE XEQ (inside the JCL deck) is the method for specifying the target node. On the other hand, /*ROUTE XEQ LOCAL seems equivalent to an FTP open localhost, and a put of a JCL deck to JES. :) Cheers,,,Steve -- 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: Which fonts are being actually used?
PSF reports all resource usage for a job with the AFPSTATS report, including number of references, member and library name, but, of course, only for files that PSF processes. If VPS is processing AFP print files (produced by DCF or files using a PAGEDEF or FORMDEF) and driving AFP (IPDS) printers, then there may be a resource exit that you could monitor. If it does not use PAGEDEF/FORMDEF (defaulted in VPS or on the OUTPUT statement) then, other than DCF jobs (if DCF is used to create AFP instead of PostScript or line data or HTML), it won't use any of the fonts distributed with z/OS 2.1. For DCF, you could replace the .BF (begin font) command with a macro that records the font used, or just run SUPERC against your DCF source looking for .BF. In general, it is not a good idea to delete individual fonts. Because there are a number of libraries for 240, 300 and outline fonts you could remove the libraries you are sure you won't need. Also, you will not need the WorldType Fonts installed in Unix. Howard Turetzky Ricoh Production Print Solutions -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Metal C vs. HLASM - for C callable subroutine?
David Crayford wrote: On 26/03/2014 4:32 AM, Tony Harminc wrote: On 25 March 2014 16:16, Paul Gilmartin paulgboul...@aim.com wrote: Wouldn't it be nice if all the header files were trilingual? Assembler/PLS/Metal C? It'll take a while. Ugh, please. :-( There's nothing wrong with Metal C that a complete redesign wouldn't fix. I find that I rarely need Metal/C. What I do want to do is inline assembler into LE code. Why the z/OS C++ compiler doesn't support this is beyond me. It's the only C/C++ compiler that doesn't and it's a PITA. The Dignus compilers would let you do this... (in-line ASM in LE mode.) - 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: Ever see automatic 30-day trials for mainframe software?
Haven't seen anything. Possibilities would be a date in the program and if past that date the program stops. Site would need to keep updating the download to reflect a later date. Or detect the create date of the library the program is installed in, or save the install date into a member, possibly store as packed data or time stamp to hide the value. On Wed, Mar 26, 2014 at 11:20 AM, Charles Mills charl...@mcn.org wrote: Right. Good input. Thanks. I have shipped software with a hard-coded expiration date. What I am looking for is a floating expiration date that would be 30 days after installation, whether installed today or a year from today. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mullen, Patrick Sent: Wednesday, March 26, 2014 9:07 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Ever see automatic 30-day trials for mainframe software? The CICS Betas released over the last few releases (I believe betas were/are available for 4.2, 5.1 5.2) have built in expiry dates. IBM states that the betas Contain a disabling device that will prevent it from being used after the test period ends. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Reflexivity (was: NJE Clarifications)
Skip Robinson is of course quite right. A job can be sent to any NJE node for execution by operator command, and operator commands can of course be generated. There are, however, simpler solutions. JCL that differs parametrically from one instance to another of its use is easy, very easy, to generate using, say, the HLASM's macro language, after which it can be handed off to the the internal reader. (REXX or the PL/I macro preprocessor could be used instead.) This pother about whether JCL is or is not changed is not really very interesting. It is either in error or it does something in any of its states, and defaults for the usual case are easy to provide. 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: DS6800 disk - was support is ending for Windows XP - Microsoft Windows
W dniu 2014-03-26 19:04, Pommier, Rex pisze: quote any site that has the SMC connected to an external network might want to reevaluate that /quote Therein lies the rub. At my site, the dictate has come down from on high (and not completely without merit) that any PC on the network needs to be supported. The SMC needs to be on the network in order for the phone home to work. We don't have a modem on our SMC, it is configured to send problem data across the big, bad, internet to IBM. The dictate is not weird, but for such cases there is an acceptable solution: separate network. It's a kind of physical security. BTW: What kind of support does one have for 3494 or TS3500? There are some computers inside, you can (should) connect them to the network in order to have remote access. Did anyone get any security patch fo any of the computers? They do have some OS (OS/2 for 3494, AIX or Linux for TS3500 AFAIK). Usually there is patching policy (dictate) for the computers in the network, obviously the policy does not cover such embedded machines. -- Radoslaw Skorupka Lodz, Poland -- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorized to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. mBank S.A. z siedzib w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: kont...@mbank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. Wedug stanu na dzie 01.01.2014 r. kapita zakadowy mBanku S.A. (w caoci wpacony) wynosi 168.696.052 zote. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Ever see automatic 30-day trials for mainframe software?
W dniu 2014-03-26 16:36, Charles Mills pisze: [...] Has anyone ever seen mainframe software that automatically expired 30 days after installation? If so, any rough idea how that worked? (Presumably, not a magic hidden file LOL.) Yes. How does it work? It depends, I've seen various methods. One of them is to record some data in magic file. -- Radoslaw Skorupka Lodz, Poland --- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorized to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. mBank S.A. z siedzib w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: kont...@mbank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. Wedug stanu na dzie 01.01.2014 r. kapita zakadowy mBanku S.A. (w caoci wpacony) wynosi 168.696.052 zote. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: The IBM Strategy
IBM: We make mistakes so you don't have too! - -teD - Original Message From: zMan Sent: Wednesday, March 26, 2014 14:58 To: IBM-MAIN@LISTSERV.UA.EDU Reply To: IBM Mainframe Discussion List Subject: Re: The IBM Strategy IBM has a strategy? Wow, that's a huge leap forward from what we've seen in recent years! (Yes, I'm being snide/unfair/whatever, no need to point that out) On Wed, Mar 26, 2014 at 1:29 PM, Anne Lynn Wheeler l...@garlic.comwrote: URL recently showed up in (ibm employee) linkedin group http://www.ibm.com/annualreport/2013/strategy.html The IBM Strategy: Waer remaining a new future for our clients, our industry and our company. This is how. 01: We are making markets by transforming indusries and professions with data 02: We are remaking enterprise IT for the era of cloud 03: We are enabling systems of engagement for enterprises. And we are leading by example. -- 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 -- zMan -- I've got a mainframe and I'm not afraid to use it -- 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: The IBM Strategy
thats reminds me the tails about the M(onk)frammer who sold his f(errari)acility... He should have done that years ago. On Wed, Mar 26, 2014 at 10:22 PM, Ted MacNEIL eamacn...@yahoo.ca wrote: IBM: We make mistakes so you don't have too! - -teD - Original Message From: zMan Sent: Wednesday, March 26, 2014 14:58 To: IBM-MAIN@LISTSERV.UA.EDU Reply To: IBM Mainframe Discussion List Subject: Re: The IBM Strategy IBM has a strategy? Wow, that's a huge leap forward from what we've seen in recent years! (Yes, I'm being snide/unfair/whatever, no need to point that out) On Wed, Mar 26, 2014 at 1:29 PM, Anne Lynn Wheeler l...@garlic.com wrote: URL recently showed up in (ibm employee) linkedin group http://www.ibm.com/annualreport/2013/strategy.html The IBM Strategy: Waer remaining a new future for our clients, our industry and our company. This is how. 01: We are making markets by transforming indusries and professions with data 02: We are remaking enterprise IT for the era of cloud 03: We are enabling systems of engagement for enterprises. And we are leading by example. -- 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 -- zMan -- I've got a mainframe and I'm not afraid to use it -- 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JFCB LBI Blocksize
I guess I should have made myself more clear. I am running a job and in that job I want to get the block size for the dataset associated with one of the DDs in the step that is currently running. I 'stole' COBOL a program which PSA--TCB--TIOT. It then searches for my DD establishes addressability to the JFCB for my file. I then get the DSN, member name, LRECL, and block size from the JFCB for my file. However, the block size in the JFCB is only 2 bytes. I have discovered the actual block size is in the SIOTX as SIOTX_BLOCKSIZE. My question is how do I get to the SIOTX for my DD while running the program which has the DD allocated? Thanks! Chris Cantrell -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Ever see automatic 30-day trials for mainframe software?
I once did this with a VSE software product. However, when I created the z/OS version of that product I decided the advantage of the automatic trial period was just not worth the risk in an MVS environment. There are easy enough ways to determine when something has been installed for a period of time, but the trick is to be able to determine that when the product is completely reinstalled. The current date can be checked against something like the creation date in a library DSCB or a PDS directory entry stat. But, the real problem is that you need to leave some track that will persist beyond the complete removal of the product and a reinstall from scratch. That is a big problem in a secure environment, and if you do find a way it would be still be considered unethical by most people. I don't know what type of product you are considering this for but something else to consider is the competitors for the product. Some product areas see very fierce competition. I also ran into the situation where a competitor downloaded my product and ran it on their system with the automatic trial period. I quickly lost my enthusiasm for that technique. All in all, in my opinion it is just not worth it. Authorization keys are a necessary evil for most ISVs but the tricks you would have to play to automate it and still maintain control are not worth the potential problems. Chuck Arney Arney Computer Systems Web: http://zosdebug.com Facebook: http://www.facebook.com/arneycomputer -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Wednesday, March 26, 2014 3:15 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Ever see automatic 30-day trials for mainframe software? W dniu 2014-03-26 16:36, Charles Mills pisze: [...] Has anyone ever seen mainframe software that automatically expired 30 days after installation? If so, any rough idea how that worked? (Presumably, not a magic hidden file LOL.) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Ever see automatic 30-day trials for mainframe software?
On Mar 26, 2014, at 10:36 AM, Charles Mills wrote: Has anyone ever seen mainframe software that automatically expired 30 days after installation? If so, any rough idea how that worked? (Presumably, not a magic hidden file LOL.) Charles: I have. Its *USUALLY* hidden in the key . Its been a while so I cannot remember exact cases. At one time (IIRC) it took an IPL to update the key. I am pretty sure that has been eliminated. As to Good/Bad it really depended on the product. *SOME* products are an easy install, others take 30 days just to read the installation manual. Then there are what I call throw away products. They are just that, throw away (I won't go into names). Those are a waste of time IMO and e shouldn't be discussing them on here. Ed -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: The IBM Strategy
Meaningless nonsense buzzwords. From: Anne Lynn Wheeler l...@garlic.com To: IBM-MAIN@LISTSERV.UA.EDU Sent: Wednesday, March 26, 2014 11:29 AM Subject: The IBM Strategy URL recently showed up in (ibm employee) linkedin group http://www.ibm.com/annualreport/2013/strategy.html The IBM Strategy: Waer remaining a new future for our clients, our industry and our company. This is how. 01: We are making markets by transforming indusries and professions with data 02: We are remaking enterprise IT for the era of cloud 03: We are enabling systems of engagement for enterprises. And we are leading by example. -- 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Ever see automatic 30-day trials for mainframe software?
On 27/03/2014 2:36, Charles Mills wrote: On the mainframe side, I don't think I've ever seen an automatic 30-day trial, largely because magic hidden files are of course greatly frowned upon in this space. Mainframe 30-day trials in my experience require vendor administration to generate some sort of 30-day key. The idea of magic hidden files might be frowned upon, but I think that is more due to the description. If you store data for use by your program in an obscure location, using standard, documented interfaces I don't see it as a problem. I worry more about software requiring authorized libraries and software that installs hooks into system services than software that might store a piece of data somewhere for its own use. The difficlty is working out a location that would work on all customer systems. An idea might be something along the lines of storing a date and hash into the application load library on installation, then storing a hash of the hash somewhere in storage on first run so that if you reinstalled you also had to re-IPL (or find and delete the stored value). The aim is not to create something foolproof and unhackable, it is really to remind the customer that they are supposed to be paying for the software, and make it at least inconvenient to bypass. PC 30 day trials are similar - you can probably use registry monitors etc. to find where the data is stored and delete it, and some people might do that, but the aim is to remind the honest customer to purchase. I think the real reason most mainframe software requries you to contact the vendor for a trial is price. With high prices comes the assmption that a sales person will be involved (and vice versa - if a sales person is involved prices need to be set at a level that will support them!) The last thing sales people want is to have people interested in the software, but not know who they are. So the real reason for having to contact the vendor and request a key is to provide a lead for a sales person - not because of technical difficulties implementing a trial period. Andrew Rowley -- and...@blackhillsoftware.com +61 413 302 386 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Ever see automatic 30-day trials for mainframe software?
The Sterling Software division I worked for did this, on VM, not MVS. The CPUID file was very robust, had in it: - Soft expiration (start warning) - Expiration (warn loudly) - Hard expiration (stop working) The file could contain keys for multiple CPUs, so you didn't have to keep track of which one was for which CPU, and if it read one that was expired, the parser would keep reading. So while there was hygienic value in keeping the file clean, it didn't hurt if you didn't. It also supported timed emergency keys, that would run on any CPU. So the on-call person had a list of those, updated every week (with a several-week timeout, so a missed update wasn't a crisis, either). And of course a short-term key could be easily (and automatically) generated for a given CPU serial number. The CPUID consisted of human-readable hex groupings with blanks between them, ignored extra/missing blanks, linends, blank lines, and comments, and was thus easy to read over the phone, FAX, cutpaste, etc. All very civilized; aside from the fact that customers would let things get to crisis state and call at 3AM Sunday, it worked very well. (As opposed to another place I worked, where the CPUID for a Linux machine was a human-readable blob of hex with no spaces-impossible to read reliably-and the stupid thing that processed it insisted on no spaces and on Linux-style linends, so if you got one emailed to you on Windows and FTPed it, it wouldn't work until you dos2unix-ed it, which was just dumb. And it had no redundancy, no tolerance for anything. Really, really irritating.) ObAnecdote: A friend once wandered into his data center (remember having one of those nearby?) and looked at the operator's console, saw product WILL EXPIRE IN 3 DAYS! CONTACT STERLING SOFTWARE! He said something gentle along the lines of What the *!#$? Why are you ignoring that? The operator glanced at it and said, Oh, product always says that. Um, no - only for the last 27 days! I believe that operator was soon looking for a job. Or at least should have been. ...phsiii -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DS6800 disk - was support is ending for Windows XP - Microsoft Windows
I configure 4 IBM ESS F20 from a Win NT SP6 isolated PC. On Wed, Mar 26, 2014 at 3:03 PM, R.S. r.skoru...@bremultibank.com.pl wrote: W dniu 2014-03-26 19:04, Pommier, Rex pisze: quote any site that has the SMC connected to an external network might want to reevaluate that /quote Therein lies the rub. At my site, the dictate has come down from on high (and not completely without merit) that any PC on the network needs to be supported. The SMC needs to be on the network in order for the phone home to work. We don't have a modem on our SMC, it is configured to send problem data across the big, bad, internet to IBM. The dictate is not weird, but for such cases there is an acceptable solution: separate network. It's a kind of physical security. BTW: What kind of support does one have for 3494 or TS3500? There are some computers inside, you can (should) connect them to the network in order to have remote access. Did anyone get any security patch fo any of the computers? They do have some OS (OS/2 for 3494, AIX or Linux for TS3500 AFAIK). Usually there is patching policy (dictate) for the computers in the network, obviously the policy does not cover such embedded machines. -- Radoslaw Skorupka Lodz, Poland -- Tre tej wiadomo ci mo e zawiera informacje prawnie chronione Banku przeznaczone wy cznie do u ytku s u bowego adresata. Odbiorc mo e by jedynie jej adresat z wy czeniem dost pu osób trzecich. Je eli nie jeste adresatem niniejszej wiadomo ci lub pracownikiem upowa nionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dzia anie o podobnym charakterze jest prawnie zabronione i mo e by karalne. Je eli otrzyma e t wiadomo omy kowo, prosimy niezw ocznie zawiadomi nadawc wysy aj c odpowied oraz trwale usun t wiadomo w czaj c w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorized to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. mBank S.A. z siedzib w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: kont...@mbank.pl S d Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru S dowego, nr rejestru przedsi biorców KRS 025237, NIP: 526-021-50-88. Wed ug stanu na dzie 01.01.2014 r. kapita zak adowy mBanku S.A. (w ca o ci wp acony) wynosi 168.696.052 z ote. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: The IBM Strategy
Frank Swarbrick wrote: | Meaningless nonsense buzzwords. and it is easy to sympathize with his reaction; but he is wrong, dead wrong. IBM has, for example, made a large substantive and financial commitment to the cloud. Rhetorical conventions differ from one context to another, and in the context of big companys' annual reports, IBM's rhetoric is modest. It would be inappropriate to a learned-journal paper or even a language-reference manual, but an annual report is neither. 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: Reflexivity (was: NJE Clarifications)
In 4657009561737029.wa.paulgboulderaim@listserv.ua.edu, on 03/26/2014 at 07:00 AM, Paul Gilmartin paulgboul...@aim.com said: OK. An FTP server can't communicate with itself. I never said it could. I don't know why you're asking. Because that's the TCP/IP analog to NJE talking to itself. I don't know the NJE jargon. What is the analogue of a client from which jobs might be submitted, There is none. NJE is a peer-to-peer protocol for jobs and other entities that something has already submitted. The mechanism for submitting a job is outside the scope of the protocol, just as the editor used to create a file is outside the scope of FTP. For MVS you use an internal reader to submit a job. either explicitly or under the covers. For other systems you use something else. Similarly, if a job creates a sysout data set then the ultimate disposition of that data set is outside the scope of NJE, just as there is nothing in FTP to affect what you do with a file after you FTP it. The complaint (however mild) was that it's relatively difficult to submit jobs via NJE to run on the local host, In fact, it's impossible. It is, however, trivial to submit jobs to JES[2|3] in an NJE network to run on the local host, and doing so does *NOT* require the local node to talk to itself. With FTP, there's no differential in difficulty. With FTP, a local client can talk to a local server. Again, neither can talk to itself. Why is it harder with NJE? That depends on what it is. The analog of what you are asking NJE to do is for an FTP client to talk to itself or for an FTP server to talk to itself, neither of which is possible. Is it simply that the local host is customarily left out of the routing tables? No, it's that NJE was not designed to talk to itself and nobody has ever shown that there would be any utility in allowing it. Someone else suggested that with a /*ROUTE command it could be done. No, they suggested that a /*ROUTE could do what you really wanted, as opposed to what you asked for. o Regardless how simple, this is modifying the JCL, probably making it ineligible to run on other systems until it's changed back How would you expect the software to determine that the intended routing is not what you have in the JCL? How would allowing the local node to talk to itself facilitate that determination? BTW, I would probably use the shorter /*XEQ JECL statement. o Does this work by routing the job to an (arbitrarily chosen) remote host which sends it back? No, it works by noticing that the node name given matches the node name of the local node. -- 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: Metal C vs. HLASM - for C callable subroutine?
In 3653742774909972.wa.paulgboulderaim@listserv.ua.edu, on 03/25/2014 at 06:03 PM, Paul Gilmartin paulgboul...@aim.com said: Actually, I can. That's an implementation technique. Suppose a Requirement for trilingual macros were to be submitted to IBM. They'd reject it. It's my understanding that when considering Requirements, IBM discourages the users' specifying implementation techniques, desiring only objectives instead. And yet you're asking for a specific implementation technique instead of the actual objective, which is to have control block mappings for multiple languages. It might be nice that a single file serve all of the languages, but that should not be part of the requirement. BTW, why trilingual? Why not multilingual, to include at least foo, bar and baz? -- 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: Allocating file in Rex exec
In 219796.7982...@smtp110.mail.ne1.yahoo.com, on 03/26/2014
at 02:09 PM, Scott Ford scott_j_f...@yahoo.com said:
Alloc fi(myddnam) da('my.pds.name(member)') shr
I get an error routine not found
That a sjorthand equivalent to
Alloc fi(myddnam) da(' || my.pds.name(member) || ') shr
The expression in the middle is a function call. You almost certainly
wanted one long constant, in which case you need to put everything
inside of the quotes. When you get that sort of error message against
what you thought was a constant, carefully check whether your opening
and closing quotes are correctly paired.
--
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: Ever see automatic 30-day trials for mainframe software?
In 3253568952062076.wa.elardus.engelbrechtsita.co...@listserv.ua.edu, on 03/26/2014 at 10:55 AM, Elardus Engelbrecht elardus.engelbre...@sita.co.za said: They're also called 'nagware'. They're nagging constantly, Those are the ones that I decide not to buy. interrupting your work, The smart vendors whine when you initially start the application and then leave you alone until the next time you start it; oddly enough, those are usually the ones that I decide are worth buying. I've also had products that I couldn't evaluate adequately within the permitted period; the vendor invariably gave me an extension and in every case that I recall ultimately got my money. Some of those software were really clever that if you adjust your clock, they will disable themselves properly... If I have to go through that much hassle, the evaluation is over - thanks but no thyanks. True. You get also temp keys for DRP or switch over to new footprint. Whatever it is, you have to involve your vendor. ObPogo Alas, sometimes the problem is not the vendor. It is either licensed (vendor supplied) or freebies at your own extreme risk (CBTTAPE for example). Paying for software is no guaranty of adequate support, and some of the best software support that I have gotten has been for free software. Thank you, Bruce and all the others. -- 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: Reflexivity (was: NJE Clarifications)
In 0de6a9840123e547b061ac5b6765c026dda...@exmb-05.ad.wsu.edu, on 03/26/2014 at 06:03 PM, Gibney, Dave gib...@wsu.edu said: I think that some of this is a real difference between the way the two protocols work. Not that I can see. I think that some of this is a real difference between the way the two protocols work. Using FTP, I can submit a given JCL deck to any host I have access to and authority to run. No you can't. You can submit a given JCL file to the primary JES on any host running an FTP server that you have access to. You can't control what node and member it runs on without modifying the JCL. I haven't actually used NJE much, but I don't think it supports changing the NJE target from outside the JCL deck. The /*ROUTE XEQ (inside the JCL deck) is the method for specifying the target node. The methods are not part of the NJE protocl, and /*ROUTE is not the only method. On the other hand, /*ROUTE XEQ LOCAL seems equivalent to an FTP open localhost, No. -- 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: Ever see automatic 30-day trials for mainframe software?
On Mar 26, 2014, at 6:44 PM, Andrew Rowley wrote: On 27/03/2014 2:36, Charles Mills wrote: On the mainframe side, I don't think I've ever seen an automatic 30-day trial, largely because magic hidden files are of course greatly frowned upon in this space. Mainframe 30-day trials in my experience require vendor administration to generate some sort of 30-day key. The idea of magic hidden files might be frowned upon, but I think that is more due to the description. If you store data for use by your program in an obscure location, using standard, documented interfaces I don't see it as a problem. I worry more about software requiring authorized libraries and software that installs hooks into system services than software that might store a piece of data somewhere for its own use. Andrew: This is not quite the same but something remotely similar. A LONG time ago (GT 40) years a vendor who thought he as clever needed to store a jobname in low memory. This was fine except MVS needed 2 PSA's (or more) so the the problem arose that you had to assemble the nuc with a DC of 640 ((max 80 job names). At the beginning it was OK. e started having issues when the #'s of UCB's reached over 1200 (or some number my memory is fuzzy here). Then to add to the issue the product did not always clear the entry in the table and it would fill up if we didn't IPL for a few days. One of the sysprogs had to write a program to see if the job was still running and if not clear the entry. We had major management screaming at us as they couldn't order any more DASD and operations screaming at us because of the JOBNAME issue. We just old them to talk to the vendor as we didn't write the code. I think the vendor finally fixed the jobname issue as the problem seem to disappear after maintenance but the UCB was a PIA for quite some time as we seemed to be the only customer ho complained. The vendor as little if any help. CA bought them out 2 years or so later. Ed -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Metal C vs. HLASM - for C callable subroutine?
On 27/03/2014 12:20 AM, Kirk Wolf wrote: David, I agree - this would be GREAT. I've asked IBM about this and I think that at the time they said that it was a known requirement. Will be asking again next week. In the meantime, I would suggest that all interested submit your requirements. I put that requirement in a couple of years ago with a list of use cases why it would be useful. To be fair the compiler guys in Toronto have been good wrt accepting my requirements in the past (PLO bif) and I appreciate they have a long list of features to implement. However, __asm() is an absolute must have for me. One of my use cases was a packed decimal class in C++. I notice in z/OS 2.1 they shipped all the PD instructions as BIFs so they threw a bone! Just not the one I wanted. What we do (a lot) is to write XPLINK assembler leaf routines and call them from (non-metal) C/C++. It works better for 31-bit, since you can use the XPLINK stack for your 31-bit work area. For 64-bit or bi-amodal assembler, we end up using __malloc31() and passing the workarea as a pointer, which IMO is preferable to getting OS memory off the heap. But inlining in non-Metal wouldn't help with that. We use the same technique. Grrr, __malloc31(), __malloc24() only supported in AMODE(64)! How brain damaged is that? Kirk Wolf Dovetailed Technologies http://dovetail.com On Tue, Mar 25, 2014 at 10:54 PM, David Crayforddcrayf...@gmail.comwrote: On 26/03/2014 11:38 AM, Gord Tomlin wrote: On 2014-03-25 22:11, David Crayford wrote: I find that I rarely need Metal/C. What I do want to do is inline assembler into LE code. I have found Metal to be useful in a few situations where it is desirable to have a self-contained program with inline Assembler and no dependencies on the LE runtime. Admittedly these occasions are not that common; in my experience it's not very often that a situation presents itself where C with inline Assembler is preferable to pure Assembler. I can think of plenty of situations, the most common being synchronization primitives for multi-theaded code. They is no built-in for a membar in z/OS C/C++ which is simple to code in gcc. #define eieio() asm volatile(bcr 15,0 : : : memory) If I had that I can then port libraries like boosts lock free http://www.boost.org/doc/libs/1_55_0/doc/html/lockfree.html. There's no such thing as Metal/C++ ;). -- For IBM-MAIN subscribe / signoff / archive access instructions, send email tolists...@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: Ever see automatic 30-day trials for mainframe software?
On 27/03/2014 14:40, Ed Gould wrote: This is not quite the same but something remotely similar. A LONG time ago (GT 40) years a vendor who thought he as clever needed to store a jobname in low memory. That's why I specified using standard, documented interfaces. It might be as simple as name/token services. I'm not sure what options you have to store something that lasts longer than the address space if you are not APF authorized, but in that case you shouldn't be able to do damage either. There are many products out there that hook into the systems in ways that are not documented or supported by IBM to perform thier core functionality. This is equally as dangerous (or more) than something simply storing a value somewhere. Most sysprogs would have some experience with one or another vendor product causing a problem with its hooks. That core function is probably more reason to be cautious with an evaluation than the method of tracking the evaluation period. Andrew Rowley -- and...@blackhillsoftware.com +61 413 302 386 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Ever see automatic 30-day trials for mainframe software?
On 3/26/2014 9:20 AM, Charles Mills wrote: Right. Good input. Thanks. I have shipped software with a hard-coded expiration date. What I am looking for is a floating expiration date that would be 30 days after installation, whether installed today or a year from today. Our trial software expires n days after download. The key is stored in a load module. It would not be difficult to use the SHSCRIPT function of SMP/E to create a module in a z/OS UNIX directory with expiry date relative to install date. Food for thought for the future. :) However, I really don't like the idea of an expiry date relative to first execution. Implementation could get messy. -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
