Re: TIBCO ES start up error - Duplicate ID
Knowing nothing at all about what TIBCO may be, I would guess a syntax error in TIBCO.CNTL(SXSSSP$1). A duplicated parameter perhaps. I would also expect more info from one or more of the SYSOUT's TIBLPARM for example. Then I'd look SXS2019E up in the products message manual (if you have an install manual, I would hope you have a msg manual). I would expect rc=8 rsn=261 to be fairly specific. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of jagadishan perumal Sent: Wednesday, November 30, 2011 8:57 PM To: IBM-MAIN@bama.ua.edu Subject: TIBCO ES start up error - Duplicate ID Hi, Recently I tried installing TIBCO ES, after all the consecutive steps the final step was to start the TIBCO ES server. The TIBCO start up ended with the below error : Start Up proc : //SXSESSS JOB (SYSUID),'SUBSTATION ES START', // CLASS=A, // TIME=1440, // REGION=0M, // NOTIFY=SYSUID, // MSGCLASS=X, // MSGLEVEL=(1,1) //* /*JOBPARM BYTES=99,CARDS=99,LINES=,PAGES=9 //* // //* //* EXECUTE THE TIBCO SUBSTATION ES //* --- //* //* Instructions: //* Issue CAPS OFF when modifying this file. //* Refer to the Tibco Substation Installation manual for the //* System Startup paramaters (SSP) defintions and usage //* //* //* === //* //* TIBCO Substation(tm) ES for z/OS //* //* Copyright (c) 1994-2010 Tibco Software Inc. //* Tibco technology is protected under these US patent numbers: //* 5187787; 5257369; 5557798. //* All rights reserved. //* //* // //* //* GLOBALS: //* // SET USERHLQ=TIBCO // SET CICSHLQ=CICSTS31.CICS //* //* //TIBSSMT EXEC PGM=TIBSSMT2,REGION=0M, // PARM='-SSPMEM SXSSSP$1' //* //* Libraries in this concatenation must be Authorized //STEPLIB DD DISP=SHR,DSN=USERHLQ..AUTH // DD DISP=SHR,DSN=CICSHLQ..SDFHEXCI //* //SYSLIB DD DISP=SHR,DSN=CEE.SCEERUN //* //** TIBCO Substation ES - Control files //* //TIBPARM DD DISP=SHR,DSN=USERHLQ..CNTL //TIBCFG DD DISP=SHR,DSN=USERHLQ..CFGIVP //* //** Parameter Audit output (v1.1) //* //TIBLPARM DD SYSOUT=* //* //* //** TIBCO Substation ES - Log and Trace Files //* //TIBLOGPR DD SYSOUT=* //TIBTRCPR DD SYSOUT=* //* //** TIBCO Substation ES - Log and Trace Debug Files //* //TIBLOGDB DD SYSOUT=* //TIBTRCDB DD SYSOUT=* //* //** Used for Disk Logging and Tracing (v1.1) //** Initially not setup to be used //* //*TIBLOGF1 DD DISP=SHR,DSN=USERHLQ..LOG.DISKF1 //*TIBLOGF2 DD DISP=SHR,DSN=USERHLQ..LOG.DISKF2 //*TIBTRCF1 DD DISP=SHR,DSN=USERHLQ..TRC.DISKF1 //*TIBTRCF2 DD DISP=SHR,DSN=USERHLQ..TRC.DISKF2 //* //** SSL Certificate Files //* //*SSLCCERT DD DISP=SHR,DSN=USERHLQ..CNTL(SSLCCERT) //*SSLCKEY DD DISP=SHR,DSN=USERHLQ..CNTL(SSLCKEY) //* //* //** System miscellaneous definitions //* //SYSMDUMP DD SYSOUT=* //SYSPRINT DD SYSOUT=* //SYSOUT DD SYSOUT=* //STDOUT DD SYSOUT=* //STDERR DD SYSOUT=* //CEEOUT DD SYSOUT=* //CEEDUMP DD SYSOUT=* //TIBLEMSG DD SYSOUT=* //TIBUOESB DD SYSOUT=* //TIBUOMSG DD SYSOUT=* //TIBUOSXC DD SYSOUT=* //* Use ONLY when needed. This would affect performance //*CEEOPTS DD * //*RPTSTG(ON) Error message : Now logging for date 2011/12/01 09:03:07.7317 SXG1600I Log Agent Starting - Logging to TIBLOGPR 09:03:07.7447 SXG1800I Parameter Log Agent Starting - Logging to TIBLPARM 09:03:07.7717 SXG1700I Trace Agent Starting - Tracing to TIBTRCPR 09:03:07.7738 SXS1000I Starting ~ TIBCO Substation (ES) for z/OS 09:03:07.7748 SXS1009I Substation (ES) - Version 2.6.0.0 *09:03:07.8889 SXS2019E Found Duplicate IId: ESB01 RC:8 RSN:261* - duplication found 09:03:07.8889 SXG2803W Terminating ~ Substation ES for IVP's 09:03:08.8899 SXG1801I Parameter Log closed 09:03:08.8947 SXG1701I Trace Agent terminating 09:03:08.8998 SXG1601I Log Agent terminating file closed Please share your expertise tips if you had similar experience during TIBCO start up. I tried Googling but Not able to trace the cause for this error message. Jags -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: TIBCO ES start up error - Duplicate ID
Hi, Recently I tried installing TIBCO ES, after all the consecutive steps the final step was to start the TIBCO ES server. The TIBCO start up ended with the below error : Jags, First I would probably post to the CICS group for CICS issues. Second, I would go to the vendor for support. It sounds like a customization issue. Remember: Newsgroups are no replacement for vendor support. Lizette -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Fixing a sysplex definition problem for the first system in a sysplex - was: Re: CFRM Policy Number
I hope the above didn't completely confuse everybody! Quite the contrary, your comments about NOCATALOG were excellent! Bob -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Barbara Nitz Sent: Thursday, December 01, 2011 12:54 AM To: IBM-MAIN@bama.ua.edu Subject: Fixing a sysplex definition problem for the first system in a sysplex - was: Re: CFRM Policy Number The danger is that if *anything* goes wrong before your first system comes up, you cannot log on to fix even the most trivial problem. One way to be able to fix a sysplex problem that occurs for the first system is the following and requires planning in advance: 1. Use the default of NOCATALOG when defining the CDS. Yes, that is *still* the default. Make sure the CDS is NOT SMS-managed. (This enables you to define a new one from another sysplex or system that is up and running. All you need is access to the DASD volume the CDS will reside on.) 2. Have the sysplex. or any other qualifier that uniquely identifies *this* sysplex in the CDS name. If you don't (or have the CDS names identical on all sysplexes), the ENQ from XCFAS (that is just there to prevent you from shooting yourself in the foot when deleting CDSs) will interfere with the definition of a CDS on a different volume but with the same name. Despite NOCATALOG being the default, apparently it was never tested to define a CDS on a new volume with that ENQ present, so there is no way around it, not even via the STGADMIN RACF definition. XCF just cannot distinguish between the same name on a different volser because the ENQ cannot. Ask me how I know. Once the name is different, XCF has no problem defining the dataset, which in my opinion is adding more complexity than necessary. 3. Make sure that you specify the volser each CDS resides on in couplexx. Also, since you use NOCATLOG, the volser must get specified on every setxcf command. 4. Make sure that SYS1.SYSPLEX.CNTL (or whatever your name is as long as it is not sms-managed) is on a DASD accessible to the system that the DASD for the CDSs is accessible to. We put ours on the volume containing the primary sysplex CDS. I believe that's it. I have implemented this here, and it came in handy when we had to combine two previously independent sysplexes into one and all the two subplexes ever shared were the CDSs. It was also very handy when we had the latest round of problems with a GRS wait state because of an XCF definition, and the GRS wait state didn't even tell us the reason. BTW 'SYS1.SYSPLEX.CNTL' was our choice of a PDS to hold all couple data set and policy definitions. I highly recommend creating a single repository for all sysplex definition job streams even in a small shop. I completely agree with this advise, *especially* for the LOGR CDS, since updating that policy is done on a logstream-by-logstream basis with i.e. CICS defining new log streams as they please (if you let them). If you ever loose the LOGR CDS, you will need a repository of everything that was defined to speed up restart. And more advise: Keep the joblogs of all your latest definition jobs in sys1.sysplex.joblog, also residing on the same volume as sys1.sysplex.cntl. That helps tremendously when you actually have to check why the upcoming first system of a sysplex insists on wait stating because it cannot find ISGLOCK. We had it happen that we *thought* (checked by six eyes) we had done the right definition, but we had not. In addition, once you change the definitions from another sysplex, the joblogs won't be accessible from the sysplex they were done for. It requires discipline, though, to always save the joblogs. I hope the above didn't completely confuse everybody! Barbara Nitz -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Product code 360HTX035?
Gentlefolk, Subject says all, really. Anyone recognise product code 360HTX035? Looks to be from the dark ages, beyond that I've no idea. I've run into a few load modules recently (at different sites, but both sites are in France if that might be relevant) with this one. It seems to have something to do with comms controllers but I'd be grateful for any confirmation. A sample load module name is IFLLD1P2. All replies gratefully received! Pete. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
SYSIEFSD.Q4 resource
Hello experts, One question regarding to SYSIEFSD.Q4 resource: What is it used? Where can I find information about it? If a job tried to allocate a tape drive, will iOS tries to communicate with tape drive first before it can get share access of SYSIEFSD.Q4? Or allocation only related with software control block manipualtion? Sorry for asking this. Just trying to know if get SYSIEFSD.Q4 resource involve hardware communication or not? Thanks Victor -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Product code 360HTX035?
Found this: ftp://ftp.software.ibm.com/networking/nswww/did/f1nb3301.pdf -Original Message- From: Pete Dillon [mailto:codecraft...@cix.co.uk] Sent: Thursday, December 01, 2011 7:15 AM To: IBM-MAIN@bama.ua.edu Subject: Product code 360HTX035? Gentlefolk, Subject says all, really. Anyone recognise product code 360HTX035? Looks to be from the dark ages, beyond that I've no idea. I've run into a few load modules recently (at different sites, but both sites are in France if that might be relevant) with this one. It seems to have something to do with comms controllers but I'd be grateful for any confirmation. A sample load module name is IFLLD1P2. All replies gratefully received! Pete. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SYSIEFSD.Q4 resource
Hello experts, One question regarding to SYSIEFSD.Q4 resource: What is it used? Where can I find information about it? If a job tried to allocate a tape drive, will iOS tries to communicate with tape drive first before it can get share access of SYSIEFSD.Q4? Or allocation only related with software control block manipualtion? Have you tried to search this on the internet? Have you looked in the PLANNING FOR GRS type manuals on IBMs website? A quick search turned up the following short answer snip Mon, 02 Oct 2006 10:54:27 -0700 This has been a problem of varying severity ever since OS/360 Release 10 back in 1967 or so. I think Q4 is/was the UCB resource - but SYSIEFSD Q4 and Q5 were locked during OS/360 allocation - the most egregious form being an AVR tape mount, which blocked all other initiator processing. (also from an IBM Apar OA12454 Nov 7 2006) The VARY OFFLINE command is changed to wait for 5 seconds for the SYSIEFSD.Q4 resource to be obtained. If it is not obtained within 5 seconds, the request for the resource is cancelled to allow stalled Allocations to proceed. New message MSGCNZ0010A is issued to indicate that the command is delayed. VARY will then request SYSIEFSD.Q4 again and repeat the wait/cancel/reobtain processing until the resource is finally obtained. The IEEVARYD offline service is also changed in the same way as the VARY OFFLINE command. However, for IEEVARYD callers that cannot tolerate a delayed return from the service, a new flag, VDEV_DO_NOT_WAIT_FOR_ENQ, can be set so that the IEEVARYD service returns to the caller if the SYSIEFSD.Q4 resource cannot be obtained within 5 seconds. In this case, register 15 will contain a new return code, RC0C, on return from the IEEVARYD service. The caller of the service can choose to retry the IEEVARYD request if appropriate. end snip Lizette -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Last use date of a PDS member
What constitutes using a PDS member? When should a PDS member's access be audit-trailed? [1] The reason for some accesses seems to be more important uses than others. E.g., if a PDS member contains JCL and it is read for the purpose of starting an address space, constructing a job to be submitting into a JES, expanding a cataloged procedure, etc., then this would appeal to some users as justification for writing an SMF record, or at least putting the member name in a field in an SMF record. Likewise, using a macro or copy book at compile time seems a compelling use of the PDS member involved. At least the Assembler documents the use of such PDS members in the cross-references produced at the end of the SYSOUT for each Assembly. If such SYSOUTs were saved, then they could be scanned for particular macro names, and thus writing SMF records in this case would be redundant (although a saved SYSOUT takes a lot more storage space than a saved SMF record). Executable programs and pieces of programs are stored in PDS members, and their use typically involves an e! xecuting program, which might make this usage important enough to be documented. And object modules used in linking and building new executable modules should be given the same importance as the use of macros and copy books by compilers. But what about copying a PDS? Are its members being used? What about compressing a PDS in place, or compressing while copying elsewhere? The members are not really being used for any productive purpose, but probably in a housekeeping operation to reclaim unusable disk storage. Each member is not really being changed when it is copied, as the copy is logically identical to the original, but the metadata describing the entire member and the metadata surrounding each piece of the member are changed when its pieces are written to new disk locations. And metadata within the member's directory entry, as in the case of a load module, may change if the load module is copied to a new disk location. If a PDS member is deleted, has that member been used? When a member is deleted, often a large number of other members in the same PDS must have their metadata (directory entries) changed. Are these other members being then used when the directory is being updated to reflec! t the removal of one entry from its middle and all entries after that point must be shifted towards the front of the directory? Or is only the directory itself being used when the directory is compressed, expanded, or copied? What about an ISPF 3.14 scan of a vast library for all occurrences of a character string? Is this a use of each member? Maybe a member's access in which a string is found is important enough to document but not that of the members not containing that string. Yet all the members were accessed and thus used, FSVO use. Then there are SMP libraries. Oy vey. Each of these many different uses of a PDS member would require different logic placed in different system components to effect an audit trail, which would explain why there is no simple solution for logging any use of a PDS member. Bill Fairchild Rocket Software, Inc. [1] I believe this is the first time I have ever verbed a noun all on my own authority. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: TIBCO ES start up error - Duplicate ID
In English, the term Duplicate ID usually means that you have specified the same ID in at least two places, where a different ID is expected or required in each place. -jc- -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of jagadishan perumal Sent: Wednesday, November 30, 2011 10:57 PM To: IBM-MAIN@bama.ua.edu Subject: TIBCO ES start up error - Duplicate ID Hi, Recently I tried installing TIBCO ES, after all the consecutive steps the final step was to start the TIBCO ES server. The TIBCO start up ended with the below error : Start Up proc : //SXSESSS JOB (SYSUID),'SUBSTATION ES START', // CLASS=A, // TIME=1440, // REGION=0M, // NOTIFY=SYSUID, // MSGCLASS=X, // MSGLEVEL=(1,1) //* /*JOBPARM BYTES=99,CARDS=99,LINES=,PAGES=9 //* // //* //* EXECUTE THE TIBCO SUBSTATION ES //* --- //* //* Instructions: //* Issue CAPS OFF when modifying this file. //* Refer to the Tibco Substation Installation manual for the //* System Startup paramaters (SSP) defintions and usage //* //* //* === //* //* TIBCO Substation(tm) ES for z/OS //* //* Copyright (c) 1994-2010 Tibco Software Inc. //* Tibco technology is protected under these US patent numbers: //* 5187787; 5257369; 5557798. //* All rights reserved. //* //* // //* //* GLOBALS: //* // SET USERHLQ=TIBCO // SET CICSHLQ=CICSTS31.CICS //* //* //TIBSSMT EXEC PGM=TIBSSMT2,REGION=0M, // PARM='-SSPMEM SXSSSP$1' //* //* Libraries in this concatenation must be Authorized //STEPLIB DD DISP=SHR,DSN=USERHLQ..AUTH // DD DISP=SHR,DSN=CICSHLQ..SDFHEXCI //* //SYSLIB DD DISP=SHR,DSN=CEE.SCEERUN //* //** TIBCO Substation ES - Control files //* //TIBPARM DD DISP=SHR,DSN=USERHLQ..CNTL //TIBCFG DD DISP=SHR,DSN=USERHLQ..CFGIVP //* //** Parameter Audit output (v1.1) //* //TIBLPARM DD SYSOUT=* //* //* //** TIBCO Substation ES - Log and Trace Files //* //TIBLOGPR DD SYSOUT=* //TIBTRCPR DD SYSOUT=* //* //** TIBCO Substation ES - Log and Trace Debug Files //* //TIBLOGDB DD SYSOUT=* //TIBTRCDB DD SYSOUT=* //* //** Used for Disk Logging and Tracing (v1.1) //** Initially not setup to be used //* //*TIBLOGF1 DD DISP=SHR,DSN=USERHLQ..LOG.DISKF1 //*TIBLOGF2 DD DISP=SHR,DSN=USERHLQ..LOG.DISKF2 //*TIBTRCF1 DD DISP=SHR,DSN=USERHLQ..TRC.DISKF1 //*TIBTRCF2 DD DISP=SHR,DSN=USERHLQ..TRC.DISKF2 //* //** SSL Certificate Files //* //*SSLCCERT DD DISP=SHR,DSN=USERHLQ..CNTL(SSLCCERT) //*SSLCKEY DD DISP=SHR,DSN=USERHLQ..CNTL(SSLCKEY) //* //* //** System miscellaneous definitions //* //SYSMDUMP DD SYSOUT=* //SYSPRINT DD SYSOUT=* //SYSOUT DD SYSOUT=* //STDOUT DD SYSOUT=* //STDERR DD SYSOUT=* //CEEOUT DD SYSOUT=* //CEEDUMP DD SYSOUT=* //TIBLEMSG DD SYSOUT=* //TIBUOESB DD SYSOUT=* //TIBUOMSG DD SYSOUT=* //TIBUOSXC DD SYSOUT=* //* Use ONLY when needed. This would affect performance //*CEEOPTS DD * //*RPTSTG(ON) Error message : Now logging for date 2011/12/01 09:03:07.7317 SXG1600I Log Agent Starting - Logging to TIBLOGPR 09:03:07.7447 SXG1800I Parameter Log Agent Starting - Logging to TIBLPARM 09:03:07.7717 SXG1700I Trace Agent Starting - Tracing to TIBTRCPR 09:03:07.7738 SXS1000I Starting ~ TIBCO Substation (ES) for z/OS 09:03:07.7748 SXS1009I Substation (ES) - Version 2.6.0.0 *09:03:07.8889 SXS2019E Found Duplicate IId: ESB01 RC:8 RSN:261* - duplication found 09:03:07.8889 SXG2803W Terminating ~ Substation ES for IVP's 09:03:08.8899 SXG1801I Parameter Log closed 09:03:08.8947 SXG1701I Trace Agent terminating 09:03:08.8998 SXG1601I Log Agent terminating file closed Please share your expertise tips if you had similar experience during TIBCO start up. I tried Googling but Not able to trace the cause for this error message. Jags -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SYSIEFSD.Q4 resource
The lock on Q4 was bad for a tape mount, but in those old days, we had lots of mountable 3330 volumes, and those mounts, which always took minutes, since the tape librarian had to dismount the existing volume after it spun down, then go find the disk (and visit with Sally on the way) and then mount the new volume. And during this locked time, not only were no jobs initiated, no TSO user could issue a SAVE or EDIT a new dataset. We ran into this 360 issue when we first began to use TSO in late 72 or early 73, and fortunately, made the connection to the disk mount, and eliminated the lock by requiring all users of mountable 3330 packs to insert an IEFBR14 step to premount the volume with DISP=SHR which eliminated the lock. And this was one of the items in my first SHARE presentation in 1974. Barry Merrill -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Lizette Koehler Sent: Thursday, December 01, 2011 7:05 AM To: IBM-MAIN@bama.ua.edu Subject: Re: SYSIEFSD.Q4 resource Hello experts, One question regarding to SYSIEFSD.Q4 resource: What is it used? Where can I find information about it? If a job tried to allocate a tape drive, will iOS tries to communicate with tape drive first before it can get share access of SYSIEFSD.Q4? Or allocation only related with software control block manipualtion? Have you tried to search this on the internet? Have you looked in the PLANNING FOR GRS type manuals on IBMs website? A quick search turned up the following short answer snip Mon, 02 Oct 2006 10:54:27 -0700 This has been a problem of varying severity ever since OS/360 Release 10 back in 1967 or so. I think Q4 is/was the UCB resource - but SYSIEFSD Q4 and Q5 were locked during OS/360 allocation - the most egregious form being an AVR tape mount, which blocked all other initiator processing. (also from an IBM Apar OA12454 Nov 7 2006) The VARY OFFLINE command is changed to wait for 5 seconds for the SYSIEFSD.Q4 resource to be obtained. If it is not obtained within 5 seconds, the request for the resource is cancelled to allow stalled Allocations to proceed. New message MSGCNZ0010A is issued to indicate that the command is delayed. VARY will then request SYSIEFSD.Q4 again and repeat the wait/cancel/reobtain processing until the resource is finally obtained. The IEEVARYD offline service is also changed in the same way as the VARY OFFLINE command. However, for IEEVARYD callers that cannot tolerate a delayed return from the service, a new flag, VDEV_DO_NOT_WAIT_FOR_ENQ, can be set so that the IEEVARYD service returns to the caller if the SYSIEFSD.Q4 resource cannot be obtained within 5 seconds. In this case, register 15 will contain a new return code, RC0C, on return from the IEEVARYD service. The caller of the service can choose to retry the IEEVARYD request if appropriate. end snip Lizette -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Last use date of a PDS member
Scanning SYSOUT was actually an IBM plan prior to SMF. From my length article The History of SMF' on the 20th Anniversary of SMF (http://www.mxg.com/newsletters) in Newsletter FIFTEEN (1989): IBM'S MOTIVATION FOR DESIGNING SMF: 1. User need to account time and resource usage. 2. IBM's need to know about how the system was being used, especially about which IBM Programs were used how much/often. A SYSOUT Project had already been started inside IBM. Originally the idea was to solicit customers to submit their SYSOUT on tape, which would then be analyzed after the fact (for compiler messages, link editor, etc.) to count program usage! Barry Merrill -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Bill Fairchild Sent: Thursday, December 01, 2011 7:16 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Last use date of a PDS member What constitutes using a PDS member? When should a PDS member's access be audit-trailed? [1] The reason for some accesses seems to be more important uses than others. E.g., if a PDS member contains JCL and it is read for the purpose of starting an address space, constructing a job to be submitting into a JES, expanding a cataloged procedure, etc., then this would appeal to some users as justification for writing an SMF record, or at least putting the member name in a field in an SMF record. Likewise, using a macro or copy book at compile time seems a compelling use of the PDS member involved. At least the Assembler documents the use of such PDS members in the cross-references produced at the end of the SYSOUT for each Assembly. If such SYSOUTs were saved, then they could be scanned for particular macro names, and thus writing SMF records in this case would be redundant (although a saved SYSOUT takes a lot more storage space than a saved SMF record). Executable programs and pieces of programs are stored in PDS members, and their use typically involves an e! xecuting program, which might make this usage important enough to be documented. And object modules used in linking and building new executable modules should be given the same importance as the use of macros and copy books by compilers. But what about copying a PDS? Are its members being used? What about compressing a PDS in place, or compressing while copying elsewhere? The members are not really being used for any productive purpose, but probably in a housekeeping operation to reclaim unusable disk storage. Each member is not really being changed when it is copied, as the copy is logically identical to the original, but the metadata describing the entire member and the metadata surrounding each piece of the member are changed when its pieces are written to new disk locations. And metadata within the member's directory entry, as in the case of a load module, may change if the load module is copied to a new disk location. If a PDS member is deleted, has that member been used? When a member is deleted, often a large number of other members in the same PDS must have their metadata (directory entries) changed. Are these other members being then used when the directory is being updated to reflec! t the removal of one entry from its middle and all entries after that point must be shifted towards the front of the directory? Or is only the directory itself being used when the directory is compressed, expanded, or copied? What about an ISPF 3.14 scan of a vast library for all occurrences of a character string? Is this a use of each member? Maybe a member's access in which a string is found is important enough to document but not that of the members not containing that string. Yet all the members were accessed and thus used, FSVO use. Then there are SMP libraries. Oy vey. Each of these many different uses of a PDS member would require different logic placed in different system components to effect an audit trail, which would explain why there is no simple solution for logging any use of a PDS member. Bill Fairchild Rocket Software, Inc. [1] I believe this is the first time I have ever verbed a noun all on my own authority. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Product code 360HTX035?
Hello Pete, maybe this helps you: ftp://ftp.boulder.ibm.com/networking/nswww/did/f1nb4100.pdf regards Juergen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Last use date of a PDS member
Sheryl's document: http://www.watsonwalker.com/SMFreference.pdf. is a good place to begin to explore this topic. It contains much information that is not readily available elsewhere. John Gilmore, Ashland, MA 01721 - USA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: CFRM Policy Number
On Wed, 30 Nov 2011 22:12:33 +0530, saurabh khandelwal sourabhkhandelwal...@gmail.com wrote: Hello Art, Thanks for reply. But I didn't understand the meaning of reformat and rotate new CFRM couple datasets into service. Can you please explain me . Misnomer on my part - I mean format new CFRM couple datasets. Based on responses thus far, seems you have a handle on this part. By 'rotate them into service' I mean using SETXCF COUPLE,TYPE=CFRM,... to activate the new CDS. Regards, Art Gutowski -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Last use date of a PDS member
Thanks, and I appreciate all the responses. What I take away from them is that A) there are 3rd party products that can track member usage, or B) each shop can craft its own solution, which may consist of SMF records or some other home-grown function. But without either A or B already in place it's hit or miss. Thanks again, Greg Shirey Ben E. Keith Company -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of John Gilmore Sent: Thursday, December 01, 2011 10:07 AM Sheryl's document: http://www.watsonwalker.com/SMFreference.pdf. is a good place to begin to explore this topic. It contains much information that is not readily available elsewhere. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SYSIEFSD.Q4 resource
Barry, AND to add to this was the infamous 3850 that killed Q4. Ed -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Last use date of a PDS member
Greg, The third party vendors are not as good as they want you you to think, in my opinion. They are OK just not all that good. There no is perfect solution in other words. I would for example not use it in a court of law. Ed -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
IKTLOGR ERROR 026
IKJ608I TSOLOGON TERMINATED. IKTLOGR ERROR 026,USER xx,PROC x Anyone know what might cause these to show up all of the sudden? We are at z/OS 1.12 and have been for months. - Robert B. Richards(Bob) US Office of Personnel Management 1900 E Street NW Room: BH04L Washington, D.C. 20415 Phone: (202) 606-1195 Email: robert.richa...@opm.govmailto:robert.richa...@opm.gov - -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IKTLOGR ERROR 026
On Thu, 1 Dec 2011 12:33:27 -0500, Richards, Robert B. robert.richa...@opm.gov wrote: IKJ608I TSOLOGON TERMINATED. IKTLOGR ERROR 026,USER xx,PROC x Anyone know what might cause these to show up all of the sudden? We are at z/OS 1.12 and have been for months. It's explained in the Messages book if you lookup that message. See http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2M9C0/SPTM012768 quote When the program is IKTLOGR and the return code is 26, it means reconnect failed because a previous reconnect attempt was already in progress. /quote -- Walt Farrell IBM STSM, z/OS Security Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IKTLOGR ERROR 026
According to the manual, System Messages, Vol. 9:
IKJ608I TSOLOGON TERMINATED. {srname|mac} ERROR return-code. USER
{userid|UNKNOWN} PROC {ppp|UNKNOW}
| |Explanation:
(some text omitted)
||When the program is IKTLOGR and the return code is 26, it means reconnect
failed because a previous reconnect attempt was already in progress.|
Does that help shed any light on the situation?
Regards,
Ulrich Krueger
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf
Of Richards, Robert B.
Sent: Thursday, December 01, 2011 9:33 AM
To: IBM-MAIN@bama.ua.edu
Subject: IKTLOGR ERROR 026
IKJ608I TSOLOGON TERMINATED. IKTLOGR ERROR 026,USER xx,PROC x
Anyone know what might cause these to show up all of the sudden?
We are at z/OS 1.12 and have been for months.
-
Robert B. Richards(Bob)
US Office of Personnel Management
1900 E Street NW Room: BH04L
Washington, D.C. 20415
Phone: (202) 606-1195
Email: robert.richa...@opm.govmailto:robert.richa...@opm.gov
-
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IKTLOGR ERROR 026
Walt, Thank you, but I was not asking what it was... I was asking what would cause it to show up all of the sudden (about a dozen times recently for different users on different systems in one sysplex). I am suspecting a bug, but thought I'd canvass the list for their experience with this (or lack thereof). Bob -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Walt Farrell Sent: Thursday, December 01, 2011 12:49 PM To: IBM-MAIN@bama.ua.edu Subject: Re: IKTLOGR ERROR 026 On Thu, 1 Dec 2011 12:33:27 -0500, Richards, Robert B. robert.richa...@opm.gov wrote: IKJ608I TSOLOGON TERMINATED. IKTLOGR ERROR 026,USER xx,PROC x Anyone know what might cause these to show up all of the sudden? We are at z/OS 1.12 and have been for months. It's explained in the Messages book if you lookup that message. See http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2M9C0/SPTM012768 quote When the program is IKTLOGR and the return code is 26, it means reconnect failed because a previous reconnect attempt was already in progress. /quote -- Walt Farrell IBM STSM, z/OS Security Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Last use date of a PDS member
Thanks, and I appreciate all the responses. What I take away from them is that A) there are 3rd party products that can track member usage, or B) each shop can craft its own solution, which may consist of SMF records or some other home-grown function. But without either A or B already in place it's hit or miss. Not in all cases. As I stated PROCs invoked can be determined from SMF step records. - Ted MacNEIL eamacn...@yahoo.ca Twitter: @TedMacNEIL -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Product code 360HTX035?
Google this: 360H-TX-035 From: Sambataro, Anthony (NIH/NBS) [E] anthony.sambat...@nih.gov To: IBM-MAIN@bama.ua.edu Date: 12/01/2011 07:03 AM Subject:Re: Product code 360HTX035? Sent by:IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Found this: ftp://ftp.software.ibm.com/networking/nswww/did/f1nb3301.pdf -Original Message- From: Pete Dillon [mailto:codecraft...@cix.co.uk] Sent: Thursday, December 01, 2011 7:15 AM To: IBM-MAIN@bama.ua.edu Subject: Product code 360HTX035? Gentlefolk, Subject says all, really. Anyone recognise product code 360HTX035? Looks to be from the dark ages, beyond that I've no idea. I've run into a few load modules recently (at different sites, but both sites are in France if that might be relevant) with this one. It seems to have something to do with comms controllers but I'd be grateful for any confirmation. A sample load module name is IFLLD1P2. All replies gratefully received! Pete. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
IBM Hardware support website
I'm a little baffled by IBM's hardware support website. Although it's not strictly a mainframe issue, I thought people here might know something about it. When I go to ibm.com/support to report a hardware problem, I end up on the Electronic Service Call (ESC+) site. Problems reported there get assigned a 7-character alphanumeric problem number, e.g.RBDFDD7. But some other problems get assigned PMR numbers in the same format used for software PMRs, 5 numeric digits followed by a 3-digit branch office number, e.g. 4979,082. This occurs with PMRs generated when systems call home. Also, problems reported via ESC+ that originally have the 7-character number sometimes get reassigned to a number with the 5-digit,3-digit format. Is there any way I can view or update PMRs online if they have the 5-digit,3-digit format? These don't seem to exist in ESC+, and I haven't been able to find any other site for hardware support. Having just spent 30 minutes on hold to check a PMR status via phone, I'd really prefer to work online if possible. -- Matt Simpson -- University of Kentucky m...@uky.edu -- (859) 257-2243 630 S Broadway, Lexington, KY 40506 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Product code 360HTX035?
Pete Thanks to John Kalinich we know that it is the following: Emulation Program (OS) (Program No. 360H-TX-035) Version 3 Modification 0 You can download a manual, GC30-3002-7, from here: http://bitsavers.org/pdf/ibm/370x/ Now I reread your original post I see I didn't read it anything like carefully enough or the module name would have rung a bell! The dark ages in this case are the first round of IBM communications controllers, which, when using the program which emulated the practically antediluvian 2701, 2702, 2703 transmission control units, could accurately - as opposed to when running NCP - be called front end processors (FEPs). I can come up with a connection with France only in that later manifestations of IBM communications controllers, 3725, 3720 and 3745, emanated from a charming, generally sunny location on a ridge by the Var valley called La Gaude. If you don't have a 3704 or a 3705 any more - most people don't unless they run a museum - you don't need any of the program modules taking up any space in your partitioned data sets. Chris Mason On Thu, 1 Dec 2011 12:15:00 +, Pete Dillon codecraft...@cix.co.uk wrote: Gentlefolk, Subject says all, really. Anyone recognise product code 360HTX035? Looks to be from the dark ages, beyond that I've no idea. I've run into a few load modules recently (at different sites, but both sites are in France if that might be relevant) with this one. It seems to have something to do with comms controllers but I'd be grateful for any confirmation. A sample load module name is IFLLD1P2. All replies gratefully received! Pete. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IBM Hardware support website
Customer's cannot view the contents of hardware PMR's which is a particular pet peeve of mine. Best Regards, Sam Knutson, GEICO System z Team Leader mailto:sknut...@geico.com (office) 301.986.3574 (cell) 301.996.1318 Think big, act bold, start simple, grow fast... -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Matt Simpson Sent: Thursday, December 01, 2011 2:41 PM To: IBM-MAIN@bama.ua.edu Subject: IBM Hardware support website I'm a little baffled by IBM's hardware support website. Although it's not strictly a mainframe issue, I thought people here might know something about it. When I go to ibm.com/support to report a hardware problem, I end up on the Electronic Service Call (ESC+) site. Problems reported there get assigned a 7-character alphanumeric problem number, e.g.RBDFDD7. But some other problems get assigned PMR numbers in the same format used for software PMRs, 5 numeric digits followed by a 3-digit branch office number, e.g. 4979,082. This occurs with PMRs generated when systems call home. Also, problems reported via ESC+ that originally have the 7-character number sometimes get reassigned to a number with the 5-digit,3-digit format. Is there any way I can view or update PMRs online if they have the 5-digit,3-digit format? These don't seem to exist in ESC+, and I haven't been able to find any other site for hardware support. Having just spent 30 minutes on hold to check a PMR status via phone, I'd really prefer to work online if possible. -- Matt Simpson -- University of Kentucky m...@uky.edu -- (859) 257-2243 630 S Broadway, Lexington, KY 40506 This email/fax message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of this email/fax is prohibited. If you are not the intended recipient, please destroy all paper and electronic copies of the original message. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Last use date of a PDS member
I did mention SMF records. I'm not sure what you mean - are you disagreeing that it's hit or miss? I'm suggesting that you can search through SMF history and maybe you'll find when the proc was last invoked, but maybe you won't. It just depends on how much history you keep. Doesn't it? Greg -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Ted MacNEIL Sent: Thursday, December 01, 2011 12:25 PM Thanks, and I appreciate all the responses. What I take away from them is that A) there are 3rd party products that can track member usage, or B) each shop can craft its own solution, which may consist of SMF records or some other home-grown function. But without either A or B already in place it's hit or miss. Not in all cases. As I stated PROCs invoked can be determined from SMF step records. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Product code 360HTX035?
Actually, some is trying to port his P370 to hercules (via the hercules groups) due the second P370 failing. Would these fall under the old MVS rules so he can install them on his system? On Thu, Dec 1, 2011 at 2:12 PM, Chris Mason chrisma...@belgacom.net wrote: Pete Thanks to John Kalinich we know that it is the following: Emulation Program (OS) (Program No. 360H-TX-035) Version 3 Modification 0 You can download a manual, GC30-3002-7, from here: http://bitsavers.org/pdf/ibm/370x/ Now I reread your original post I see I didn't read it anything like carefully enough or the module name would have rung a bell! The dark ages in this case are the first round of IBM communications controllers, which, when using the program which emulated the practically antediluvian 2701, 2702, 2703 transmission control units, could accurately - as opposed to when running NCP - be called front end processors (FEPs). I can come up with a connection with France only in that later manifestations of IBM communications controllers, 3725, 3720 and 3745, emanated from a charming, generally sunny location on a ridge by the Var valley called La Gaude. If you don't have a 3704 or a 3705 any more - most people don't unless they run a museum - you don't need any of the program modules taking up any space in your partitioned data sets. Chris Mason On Thu, 1 Dec 2011 12:15:00 +, Pete Dillon codecraft...@cix.co.uk wrote: Gentlefolk, Subject says all, really. Anyone recognise product code 360HTX035? Looks to be from the dark ages, beyond that I've no idea. I've run into a few load modules recently (at different sites, but both sites are in France if that might be relevant) with this one. It seems to have something to do with comms controllers but I'd be grateful for any confirmation. A sample load module name is IFLLD1P2. All replies gratefully received! Pete. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- 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...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IKTLOGR ERROR 026
Bob We may need a description of the configuration of your users in order better to appreciate what might cause this phenomenon. It could be something like the following, which unless and until I hear otherwise, I am going to assume: TSO-API-VTAM-SNA-VTAM-API-SERVER-TCP-EMULATOR Where SERVER is the SNA-oriented Communications Server TELNET server program (TN3270E) and EMULATOR is some sort of 3270 emulator taking on the role of the TELNET client probably with TN3270E capability, for example PCOMM. Have there been, in a recent change slot, changes to parameters relating to the SERVER? Have there been, in a recent PC software download - or whatever you might call it, changes to parameters relating to the EMULATOR? Have the users of your EMULATOR been given instructions on how to improve the operation of their workstation affecting setting up, or more likely, closing down their TN3270(E) connections? What does you local specialist in charge of the SERVER say about this phenomenon? There may be some associated messages only he or she could get his or her head around. You may like to check on this function, new in V1R11 - which you may have skipped and so encountered first in V1R12, which is one of those very, very naughty cases where the developers have put out - and *implemented* - an enhancement without asking, as it were. http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2e2a0/60.5 Pending full analysis of what is going wrong, you might like to see if LOGONHERE(OFF) prevents the problem reoccurring. This is all based on the word reconnect being associated with return code 26. Chris Mason On Thu, 1 Dec 2011 12:33:27 -0500, Richards, Robert B. robert.richa...@opm.gov wrote: IKJ608I TSOLOGON TERMINATED. IKTLOGR ERROR 026,USER xx,PROC x Anyone know what might cause these to show up all of the sudden? We are at z/OS 1.12 and have been for months. - Robert B. Richards(Bob) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IKTLOGR ERROR 026
On Thu, 1 Dec 2011 13:05:07 -0500, Richards, Robert B. robert.richa...@opm.gov wrote: Walt, Thank you, but I was not asking what it was... I was asking what would cause it to show up all of the sudden (about a dozen times recently for different users on different systems in one sysplex). I am suspecting a bug, but thought I'd canvass the list for their experience with this (or lack thereof). I would suspect you're having a number of users who are starting to do a LOGON RECONNECT and for some reason are initiating another one before the first one finishes. It's hard to say whether that would represent a change in user behavior, an issue with connectivity such that the first reconnect isn't completing for them and they start another one, an issue with the user's PCs, or what. -- Walt -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Last use date of a PDS member
For PROCs it's NOT hit or miss. If a PROC is invoked it's reported it the step record. That was, by my understanding, at least part of the original request. For regular DSNs it is hit or miss -- depending on whether the member is specified or not. The rest is problematic. - Ted MacNEIL eamacn...@yahoo.ca Twitter: @TedMacNEIL -Original Message- From: Greg Shirey wgshi...@benekeith.com Sender: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Date: Thu, 1 Dec 2011 14:41:08 To: IBM-MAIN@bama.ua.edu Reply-To: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Subject: Re: Last use date of a PDS member I did mention SMF records. I'm not sure what you mean - are you disagreeing that it's hit or miss? I'm suggesting that you can search through SMF history and maybe you'll find when the proc was last invoked, but maybe you won't. It just depends on how much history you keep. Doesn't it? Greg -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Ted MacNEIL Sent: Thursday, December 01, 2011 12:25 PM Thanks, and I appreciate all the responses. What I take away from them is that A) there are 3rd party products that can track member usage, or B) each shop can craft its own solution, which may consist of SMF records or some other home-grown function. But without either A or B already in place it's hit or miss. Not in all cases. As I stated PROCs invoked can be determined from SMF step records. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Last use date of a PDS member
Yes. I used to run a special audit for a company I used to work for 25 years ago. It was truncated to 44 characters, and l, at the time, didn't care about the member -- it was the DSN. So, it can be hit or miss. - Ted MacNEIL eamacn...@yahoo.ca Twitter: @TedMacNEIL -Original Message- From: McKown, John john.mck...@healthmarkets.com Sender: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Date: Thu, 1 Dec 2011 15:22:57 To: IBM-MAIN@bama.ua.edu Reply-To: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Subject: Re: Last use date of a PDS member -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Ted MacNEIL Sent: Thursday, December 01, 2011 3:14 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Last use date of a PDS member For PROCs it's NOT hit or miss. If a PROC is invoked it's reported it the step record. That was, by my understanding, at least part of the original request. For regular DSNs it is hit or miss -- depending on whether the member is specified or not. The rest is problematic. - Ted MacNEIL I wasn't aware of that! Does it include the DSN as well as the member name? -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Last use date of a PDS member
-Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Ted MacNEIL Sent: Thursday, December 01, 2011 3:14 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Last use date of a PDS member For PROCs it's NOT hit or miss. If a PROC is invoked it's reported it the step record. That was, by my understanding, at least part of the original request. For regular DSNs it is hit or miss -- depending on whether the member is specified or not. The rest is problematic. - Ted MacNEIL I wasn't aware of that! Does it include the DSN as well as the member name? -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Last use date of a PDS member
You're only saying that SMF records it. What I'm saying is that it's hit or miss whether you can determine the last date a proc was used because it will depend on whether you still have the SMF records from that date. I only keep records for two years, so if the last time a proc was invoked was 3 years ago, I'll never know. Greg Shirey Ben E. Keith Company -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Ted MacNEIL Sent: Thursday, December 01, 2011 3:14 PM For PROCs it's NOT hit or miss. If a PROC is invoked it's reported it the step record. That was, by my understanding, at least part of the original request. For regular DSNs it is hit or miss -- depending on whether the member is specified or not. The rest is problematic. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Last use date of a PDS member
If you want to do the auditing, you can collect and update the trail. Besides, if the PROC isn't in your 3 years of SMF data, doesn't that sort of state the PROC is a little out of date (unused). - Ted MacNEIL eamacn...@yahoo.ca Twitter: @TedMacNEIL -Original Message- From: Greg Shirey wgshi...@benekeith.com Sender: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Date: Thu, 1 Dec 2011 16:22:01 To: IBM-MAIN@bama.ua.edu Reply-To: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Subject: Re: Last use date of a PDS member You're only saying that SMF records it. What I'm saying is that it's hit or miss whether you can determine the last date a proc was used because it will depend on whether you still have the SMF records from that date. I only keep records for two years, so if the last time a proc was invoked was 3 years ago, I'll never know. Greg Shirey Ben E. Keith Company -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Ted MacNEIL Sent: Thursday, December 01, 2011 3:14 PM For PROCs it's NOT hit or miss. If a PROC is invoked it's reported it the step record. That was, by my understanding, at least part of the original request. For regular DSNs it is hit or miss -- depending on whether the member is specified or not. The rest is problematic. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Last use date of a PDS member
But, if your PROC isn't in 3 years worth of data is it current? - Ted MacNEIL eamacn...@yahoo.ca Twitter: @TedMacNEIL -Original Message- From: Greg Shirey wgshi...@benekeith.com Sender: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Date: Thu, 1 Dec 2011 17:03:53 To: IBM-MAIN@bama.ua.edu Reply-To: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Subject: Re: Last use date of a PDS member Here's what I said: each shop can craft its own solution, which may consist of SMF records or some other home-grown function. What I apparently should have said was: each shop can do the auditing, if they bother to collect and update the trail. And on that note, it's 5:00, so I'm headed home. Thanks Greg Shirey Ben E. Keith Company -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Ted MacNEIL Sent: Thursday, December 01, 2011 4:41 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Last use date of a PDS member If you want to do the auditing, you can collect and update the trail. Besides, if the PROC isn't in your 3 years of SMF data, doesn't that sort of state the PROC is a little out of date (unused). -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Last use date of a PDS member
Here's what I said: each shop can craft its own solution, which may consist of SMF records or some other home-grown function. What I apparently should have said was: each shop can do the auditing, if they bother to collect and update the trail. And on that note, it's 5:00, so I'm headed home. Thanks Greg Shirey Ben E. Keith Company -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Ted MacNEIL Sent: Thursday, December 01, 2011 4:41 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Last use date of a PDS member If you want to do the auditing, you can collect and update the trail. Besides, if the PROC isn't in your 3 years of SMF data, doesn't that sort of state the PROC is a little out of date (unused). -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Last use date of a PDS member
Ted, We also have jobs run about every 2 or 3 years ad hoc inquiries by auditors and the lie. Ed -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: TIBCO ES start up error - Duplicate ID
In 023801ccb003$8587ed10$9097c730$@mindspring.com, on 12/01/2011 at 03:30 AM, Lizette Koehler stars...@mindspring.com said: Remember: Newsgroups are no replacement for vendor support. This isn't a news group. -- 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...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SYSIEFSD.Q4 resource
In 8731877265338657.wa.victorworkcnyahoo.com...@bama.ua.edu, on 12/01/2011 at 06:42 AM, Victor Zhang victor_wor...@yahoo.com.cn said: What is it used? Allocation. Where can I find information about it? The job management logic manuals that IBM no longer provides to customers. If a job tried to allocate a tape drive, will iOS tries to communicate with tape drive first before it can get share access of SYSIEFSD.Q4? IOS has nothing to do with the SYSIEFSD resources. -- 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...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Last use date of a PDS member
In CAPD5F5q_5_J2VcSxHnvWpoSPcHD5BzOidLBrE-4udtHd=9b...@mail.gmail.com, on 12/01/2011 at 11:07 AM, John Gilmore johnwgilmore0...@gmail.com said: Sheryl's document: Her newsletter is also a good source of information for anybody doing performance and usage evaluation. -- 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...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Mobius RDS
Is anyone familiar with Mobius RDS? We would like to perform mass recalls of our report archives and was wondering if anyone has experience doing this. Thanks -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Product code 360HTX035?
In CAJTOO5-n03A2dfHtijxLMocrX2o0WY=sdz5c_yeb9fpp-1f...@mail.gmail.com, on 12/01/2011 at 02:45 PM, Mike Schwab mike.a.sch...@gmail.com said: Would these fall under the old MVS rules so he can install them on his system? No, because it's not a S/360[1] program. He'd need a 3705 simulator[2]. [1] Or successor. [2] Well, a real 3705 would work ;-) -- 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...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Last use of a PDS member?
Apart from an occasional senior-moment lapse I know that Cheryl does not spell her given name with an initial 'S'. The thing I should wish to emphasize about her website and the documents available there is that they do not have a narrow marketing focus: They are valuable even to those of us who are not her customers; and that is rare enough to be, in the old literal sense, remarkable. John Gilmore, Ashland, MA 01721 - USA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SYSIEFSD.Q4 resource
Hello experts, So based on your replies, can I get a conclusion like this: The process of getting SYSIEFSD.Q4 has nothing to do with hardware, it is purely an OS control block manipulation? Regards Victor -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Mobius RDS
I go to 3.4, bring up the list. print the list of datasets, exit ISPF and save the print file, going to the next print file, then edit the print file, do change alls to get the command in place, then execute the commands. Wild card by an authorized user can work too. On Thu, Dec 1, 2011 at 6:52 PM, gsg gsg_...@yahoo.com wrote: Is anyone familiar with Mobius RDS? We would like to perform mass recalls of our report archives and was wondering if anyone has experience doing this. Thanks -- 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...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
