Re: changing the STC identifier

The code was originally created back in 1987 and using IEFRDER allowed a lot of flexibility (at the time). The code now supports alternate DD's for sequential script command input, and even dynamically generating the DD (which is what most of the 400 current users use), but enough people still

Re: changing the STC identifier

No, all that needs to be changed is that field. It takes immediate effect. I'm actually pretty impressed with the results (so far). There is still a great deal of beta testing to be conducted, but it seems to work fine. Brian

Re: CONSOLE command failing - what else to check?

We do not use RACF as our ESM, but year ago, I recall having to give OPER authority under the TSO ACCOUNT command in order for users to issue the TSO CONSOLE command. Perhaps one of your users has this and one does NOT. -Original Message- From: IBM Mainframe

Re: Application Performance Tuning Products

Hi Mark, There is also an APM product for CICS called Inspect-CPU ("ICPU") which has the ability to identify apps are causing high CPU and performance issues down to the line of code and/or offset. Has a small footprint so that it can run in production to identify candidates for tuning or for

Re: Useful recent changes to CBT File 300 (TSO commands)

Please correct me if I'm wrong, but after looking at file182 and file296, I think the release command opens the data set in order to release the free space. I'd prefer to use PARTREL instead. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On

Re: CONSOLE command failing - what else to check?

Todd Burrell wrote: >I have 2 users and one can successfully execute the CONSOLE command while >running it in a started task and in batch, but the other user cannot. From >what I can tell they are both connected to the same RACF groups and both >should have all of the necessary access

Re: CONSOLE command failing - what else to check?

SAF trace? -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Burrell, Todd Sent: Wednesday, August 16, 2017 11:06 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: CONSOLE command failing - what else to check? Yes - both are connected to

Re: CONSOLE command failing - what else to check?

Neither have an OPERPARM segment. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mark Jacobs - Listserv Sent: Wednesday, August 16, 2017 12:03 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: CONSOLE command failing - what else to

Re: CONSOLE command failing - what else to check?

Yes - both are connected to groups that give access to TSOAUTH/CONSOLE and to the appropriate OPERCMDS profiles. Todd Burrell | Sr. Mainframe Systems Administrator CISSP, PMP, ITIL Expert, CCNA, MCSE CSX Technologies| 550 Water St. (634H), Jacksonville, FL 32202 Office: (904) 633-5651 Cell:

Re: CONSOLE command failing - what else to check?

Does the falling user have an OPERPARM segment in their RACF profile? Todd Burrell August 16, 2017 at 11:52 AM I have 2 users and one can successfully execute the CONSOLE command while running it in a started task and in batch, but the other user cannot. From

Re: CONSOLE command failing - what else to check?

On Wed, Aug 16, 2017 at 10:52 AM, Todd Burrell wrote: > I have 2 users and one can successfully execute the CONSOLE command while > running it in a started task and in batch, but the other user cannot. From > what I can tell they are both connected to the same RACF groups

CONSOLE command failing - what else to check?

I have 2 users and one can successfully execute the CONSOLE command while running it in a started task and in batch, but the other user cannot. From what I can tell they are both connected to the same RACF groups and both should have all of the necessary access required to run the CONSOLE

Re: changing the STC identifier

Way back in the 70s, our SVS and MVT systems had 2! started tasks, Master and HASP. Occasionally, an external writer. STCs only later were expanded to other purposes, and obviously there's quite a few these days. J R's question is a good one. //IEFRDER allows for some convenience overrides on

Re: changing the STC identifier

IEFRDER/unitaddr was originally for unit record tasks (readers & writers) which would never be shared. (Also worked for tape drives.) It enables start/stop/modify commands to be issued against the unit address. What's odd is why you're using it in this day and age for shareable devices. If

Re: changing the STC identifier

Brian Westerman wrote: >The field at +8 into the CSCB is field I needed to change. As it turns out, I >only need to change it when it's left to default to the unit address of the >IEFRDER DD. In my code, I already know the unit address that the IEFRDER file >is on (or if it is Inline), so if

Path switch for FCTC

Hi For one of our activity we need to vary off and vary on a CHPID. All the FCTC have two CHPID defined. So if one CHPID is varied off then the active FCTC will dynamically start using the other available defined CHPID ? Regards Peter

Re: changing the STC identifier

You're quite right, it's not supported but it's actually quite safe (in this case). It's our code that makes up both the STC and the script that it uses. I have a series of checks that we do during startup and I also made sure there won;t be any timing issues between tasks. Originally I had

Re: changing the STC identifier

The field at +8 into the CSCB is field I needed to change. As it turns out, I only need to change it when it's left to default to the unit address of the IEFRDER DD. In my code, I already know the unit address that the IEFRDER file is on (or if it is Inline), so if I compare them and they are