Re: Future of COBOL based on RDz policies was Re: RDz or RDzEnterprise developers
In 636e38e0-85a4-4259-a3e4-02f3e61dd...@comcast.net, on 07/12/2013 at 04:04 PM, Ed Gould edgould1...@comcast.net said: An example (software wise) was the TSO UTILITIES OS/MVT AND OS/VS2 TSO DATA UTILITIES: COPY, FORMAT, LIST MERGE, PROG. NO. 5734-UTl. IBM issued a final round of PTF's which did not in fact correct all of the APAR's listed as corrected. You had a competitor (which I did not know of at the time) ASI Superset Utilities; better functionality, and better support than 5734-UT1 had ever had. -- Shmuel (Seymour J.) Metz, SysProg and JOAT Atid/2http://patriot.net/~shmuel We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMF record - IPADDR
In CAPikFhE9p1txmJGdkzzNPzZ+CreKsrkKd5yKwYci=ty1zqe...@mail.gmail.com, on 07/13/2013 at 09:22 AM, mf db dbajava...@gmail.com said: Is it possible to fetch Users Logon detail based on IPADDR from SMF ? Are you logging on directly to TSO or going through a session manager. Not every session mnanager supports the control vector (CV) used to communicate the IP address to TSO. -- Shmuel (Seymour J.) Metz, SysProg and JOAT Atid/2http://patriot.net/~shmuel We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMF record - IPADDR
The SMF Type 106, 118 and 119 record layouts are in: z/OS V1R13.0 Comm Svr: IP Programmer's Guide and Reference SC31-8787-14 E.0 Appendix E. Type 119 SMF records http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/f1a1d3b1/E.0 Mike Stayton z/OS Communications Server -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMF record - IPADDR
Appendix E of the z/OS Communications Server IP Programmer's Guide and Reference Version 1 Release 13 SC31-8787-14 http://publib.boulder.ibm.com/infocenter/zos/v1r13/index.jsp?topic=%2Fcom.ibm.zos.r13.halx001%2Fbehav.htm documents the many subtypes of the SMF ID=119 records, from which MXG Software creates these datasets: /* */ /* THE LIST OF DATASETS AND DD SUFFIXES FOR TYPE 119 SMF record */ /* */ /* DD MXG MXG*/ /* DATASET DATASET DATASETRECORD */ /* SUFFIX NAME LABEL SUBTYPE */ /* */ /* T11901 TYP11901 TCP CONNECTION INITIATION 1*/ /* T11902 TYP11902 TCP CONNECTION TERMINATON 2*/ /* T11903 TYP11903 FTP CLIENT TRANSFER COMPLETION3*/ /* T11904 TYP11904 TCP PROFILE INFORMATION FOR STACK 4*/ /* T11905 TYP11905 TCP/IP STATISTICS 5*/ /* T11906 TYP11906 INTERFACE STATISTICS 6*/ /* T119A7 TYP119A7 SERVER PORT STATISTICS7*/ /* T119B7 TYP119B7 SERVER PORT STATISTICS UDP7*/ /* T11908 TYP11908 TCP/IP STACK START/STOP 8*/ /*RESERVED 9*/ /* T11910 TYP11910 UDP SOCKET CLOSE 10 */ /*RESERVED 11-19 */ /* T11920 TYP11920 TN3270 SERVER SNA SESSION INIT20 */ /* T11921 TYP11921 TN3270 SERVER SNA SESSION TERM21 */ /* T11922 TYP11922 TSO TELNET CLIENT CONNECTION IN 22 */ /* T11923 TYP11923 TSO TELNET CLIENT CONNECTION TR 23 */ /*RESERVED 24-31 */ /* T11932 TYP11932 DVIPA STATUS CHANGE*/ /* T11933 TYP11933 DVIPA REMOVED */ /* T11934 TYP11934 DVIPA TARGET ADDED */ /* T11935 TYP11935 DVIPA TARGET REMOVED */ /* T11936 TYP11936 DVIPA TARGET SERVER STARTED*/ /* T11937 TYP11937 DVIPA TARGET SERVER ENDED */ /*RESERVED 38-40 */ /* T11941 TYP11941 SMC-R LINK GROUP STATISTICS*/ /* T1194L TYP1194L SMC-R LINK SPECIFIC STATISTICS */ /* T11942 TYP11942 SMC-R LINK STATE START */ /* T11943 TYP11943 SMC-R LINK STATE END */ /* T11944 TYP11944 RDMA RNIC INTERFACE STATISTICS */ /*RESERVED 45-47 */ /* T11948 TYP11948 CSSMTP CONFIGURATION DATA */ /* T11949 TYP11949 CSSMTP TARGET SERVER CONNECTION*/ /* T11950 TYP11950 CSSMTP MAIL*/ /* T11951 TYP11951 CSSMTP SPOOL */ /* T11952 TYP11952 CSSMTP STATISTICS */ /*RESERVED 53-69 */ /* T11970 TYP11970 FTP SERVER TRANSFER COMPLETION70 */ /* T11971 TYP11971 FTP DAEMON CONFIGURATION 71 */ /* T11972 TYP11972 FTP SERVER LOGIN FAILURE 72 */ /* T11973 TYP11973 IPSEC IKE TUNNEL ACTIVATE 73 */ /* T11974 TYP11974 IPSEC IKE TUNNEL DEACTIVATE 74 */ /* T11975 TYP11975 IPSEC DYNAMIC TUNNEL ACTIVATE 75 */ /* T11976 TYP11976 IPSEC DYNAMIC TUNNEL DEACTIVATE 76 */ /* T11977 TYP11977 IPSEC DYNAMIC TUNNEL ADDED77 */ /* T11978 TYP11978 IPSEC DYNAMIC TUNNEL REMOVED 78 */ /* T11979 TYP11979 IPSEC MANUAL TUNNEL ACTIVATE 79 */ /* T11980 TYP11980 IPSEC MANUAL TUNNEL DEACTIVATE80 */ /*RESERVED 81-95 */ /* T11996 TYP11996 OPENSSH SERVER TRANSFER COMPLETE 96 */ /* T11997 TYP11997 OPENSSH CLIENT TRANSFER COMPLETE 97 */ /* T11998 TYP11998 OPENSSH LOGIN FAILURE 98 */ /*RESERVED 99-191 */ /* T119X2 TY119192 CO:Z SFTP SERVER LOG 192 */ /* T119M2 TY119M92 CO:Z SFTP SERVER LOG MESSAGES192 */ /* T119X3 TY119193 CO:Z SFTP CLIENT LOG 193 */ /* T119M3 TY119M93 CO:Z SFTP CLIENT LOG MESSAGES193 */ /*RESERVED 194-255 */ The archaic SMF 118 record is also documented in the
Re: PDS86 EAV compatibility
Thanks There is a version 8.6.14.5 in File # 182 available from the CBT UPDATES section - reachable from the Updates download that doesn't have to be requested. regards, Anthony Fletcher - NZ MIITP Team Lead NZ SMM (AirNZ, Westpac NZ , TelstraClear NZ and NWM AU) IBM Strategic Outsourcing Delivery Server Systems Operations Server Management Mainframe Mainframe Software Program Manager NZ z/OS Technical Lead A/NZ Ph: Direct +64 4 576 8142, tieline 61 929 8142, ITN *869298142, mobile +64 21 464 864, Fax +64 4 576 5808. Internet: flet...@nz1.ibm.com, Sametime: flet...@nz1.ibm.com The biggest threat to effective communication is the belief that it has occurred Winners make commitments, Losers make promises From: Don Poitras poit...@pobox.com To: IBM-MAIN@listserv.ua.edu, Date: 13/07/2013 11:02 Subject:Re: PDS86 EAV compatibility Sent by:IBM Mainframe Discussion List IBM-MAIN@listserv.ua.edu You need 8.6.14.4. I don't know if you have to request it or if the CBT is current. See: http://tech.groups.yahoo.com/group/cbt-tape/message/448 In article of66ce2cb1.a8256d93-oncc257ba6.0077aa08-cc257ba6.007ae...@nz1.ibm.com you wrote: I was testing using PDS 8.6 14.2 which I believe is the latest version. The Tracking is still occurring, so there must be some code that hasn't been updated. Can't tell whether the number of cases has reduced. We don't have any EAV volumes on the system I was using so this must be against 'traditional' volumes. regards, Anthony Fletcher - NZ MIITP From: Jousma, David david.jou...@53.com To: IBM-MAIN@listserv.ua.edu, Date: 13/07/2013 00:05 Subject:Re: PDS86 EAV compatibility Sent by:IBM Mainframe Discussion List IBM-MAIN@listserv.ua.edu Nevermind, I downloaded the latest package, and see the updates. I wish that CBt would display the revision level of the PDS86. I always just assumed that since it was still 8.6 that the code wasn?t being changed. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: Friday, July 12, 2013 6:48 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: PDS86 EAV compatibility John, When did they do that? Is there a newer version than 86? -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John P Kalinich Sent: Friday, July 12, 2013 6:24 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: PDS86 EAV compatibility Anthony, SAS provided the modifications to PDS86 for access to PDSE's in cylinder managed space on EAV. Download from CBT Updates page. Regards, John K -IBM Mainframe Discussion List IBM-MAIN@listserv.ua.edu wrote: - To: IBM-MAIN@listserv.ua.edu From: Anthony Fletcher Sent by: IBM Mainframe Discussion List Date: 07/11/2013 07:29PM Subject: PDS86 EAV compatibility Is anyone, by any chance, working on PDS86 to make it compatible with the EAV DASD support code? The z/OS Tracking facility is listing PDS86 as not having the necessary set up. For example - this is just after emptying the list. RESPONSE=MLCS CNZ1001I 10.26.09 TRACKING DISPLAY 212 STATUS=ON NUM=6MAX=1000 MEM=00 EXCL=125 REJECT=0 TRACKING INFORMATION -VALUE-- JOBNAME PROGNAME+OFF-- ASID NUM SMS-E:1 DADSM OBTAIN C10001 DB2ADM SSCLOCT172 71 2 SMS-E:1 DADSM OBTAIN C10001 LDAXF67 PDS86 3D42 55 1 SMS-E:1 DADSM OBTAIN C10001 LDAXF67 SSCLOCT172 55 5 SMS-E:1 DCB OPEN EAS 113-4401 CTDTROLD IOADBS 53E 4F 2 SMS-E:1 DCB OPEN EAS 113-4401 LDAXF67 PDS86 124 55 1 SMS-W:2 IEHLIST LISTVTOC 02 AXR08IRXSTAM 1F3A 41 1 -- TO REPORT THESE INSTANCES, SEND THIS MESSAGE VIA E-MAIL TO conso...@us.ibm.com. FOR ADDITIONAL INFORMATION OR TO OBTAIN A CURRENT EXCLUSION LIST, SEE APAR II13752. -- Don Poitras - SAS Development - SAS Institute Inc. - SAS Campus Drive sas...@sas.com (919) 531-5637Cary, NC 27513 -- 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: Dynamic LPA Services
John Gilmore-There is no need for further assertions that things that manifestly do work may not or for something less than clarity about, for example, the fact that AMODE(64) code is faster than AMODE(31) code. Are you saying that AMODE(64) is faster than AMODE(31) ? If so, why would that be ? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: The amazing disappearing mainframe.
Only in India. Ashes cricket is a sell out for every single game. I won't comment on the damage that India has done to cricket in general, viz T20. The mob rules On Sun, Jul 14, 2013 at 2:16 AM, Govind Chettiar rasha...@gmail.com wrote: Not really one of the greatest rivalries anymore...With the diminishing interest in Test cricket and the surfeit of ODIs and, worse, T20s, I think Test cricket might be going the way of the IBM Mainframe. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Wayne V. Bickerdike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: The amazing disappearing mainframe.
I tried to choose my language carefully; but I was apparently misunderstood anyway, at least in part. I see no evidence that the mainframe is going the way of the dodo. What is happening, outside China and several other new markets, is that 1) the number of small- and middling-sizeed mainframe shops is dropping steadily and 2) that many of the remaining large and very large shops are continuing to grow in size. 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: SMF record - IPADDR
Which bring up the question... Where should the layout of SMF records reside, SMF manual, each product manual or ? Anyone have an opinion which way? Ed ps: Arguments on both sides are reasonable although personally I think the SMF manual as it central to all products. On Jul 14, 2013, at 7:47 AM, Mike Stayton wrote: The SMF Type 106, 118 and 119 record layouts are in: z/OS V1R13.0 Comm Svr: IP Programmer's Guide and Reference SC31-8787-14 E.0 Appendix E. Type 119 SMF records http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/f1a1d3b1/ E.0 Mike Stayton z/OS Communications Server -- 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: SMF record - IPADDR
On 7/15/2013 12:00 AM, Ed Gould wrote: Which bring up the question... Where should the layout of SMF records reside, SMF manual, each product manual or ? Anyone have an opinion which way? With most manuals now being made available in electronic form, it would be nice to have a comprehensive SMF manual with all record and field descriptions, as well as another copy, possibly with more detailed field information, in the appropriate component manual. The same question, and answer, is relevant to control blocks. It's a PITA to have a multi-volume set of control block descriptions, only to find that some are listed only in the product manuals. Gerhard Postpischil Bradford, Vermont -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMF record - IPADDR
I'd vote for both. All IBM product SMF records type 0-200 should be documented in the SMF manual. Roger S. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ed Gould Sent: Sunday, July 14, 2013 11:00 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SMF record - IPADDR Which bring up the question... Where should the layout of SMF records reside, SMF manual, each product manual or ? Anyone have an opinion which way? Ed ps: Arguments on both sides are reasonable although personally I think the SMF manual as it central to all products. On Jul 14, 2013, at 7:47 AM, Mike Stayton wrote: The SMF Type 106, 118 and 119 record layouts are in: z/OS V1R13.0 Comm Svr: IP Programmer's Guide and Reference SC31-8787-14 E.0 Appendix E. Type 119 SMF records http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/f1a1d3b1/ E.0 Mike Stayton z/OS Communications Server -- 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
