Clarification of ECBLIST

Hi The documentation says for ECBLIST All ecb's must be in the home address Space. Does that mean addressable from the Hone address space As I have 1 ecb's in the home address space And 1 in CSA Thanks Sent from my iPhone

Re: EXTERNAL: Re: IBM secure z/OS software delivery: Don't get locked out!

Just wanted to confirm for you all that Skips' note below is totally accurate. Addition of the below 2 lines is ALL that is needed to convert your existing jobs from the unsecure ftp delivery to the secure HTTPS delivery (and in my case also solved a firewall issue I'd been having with my

Re: Testing SFM policy

Followed Jim's instructions to add a WSAT entry for QUIESCE wait state. IPLed it in, then did another QUIESCE command. Got SAD and AutoIPL. SAD title: AUTOIPL WAIT STATE CODE 0CCC Thanks to everyone. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler

Re: MCS console sharing in a sysplex

Thank you John and Curtis for the explanation . Infact , I should have said UCW instead of UCB to make it more clear . But now i understand that they could be physically different devices . On Wed, Jun 8, 2016 at 2:09 AM, Pew, Curtis G wrote: > On Jun 7,

Re: Testing SFM policy

> Testing was semi-successful. On one hand, QUIESCE stopped the > system. Missing heartbeat was detected by SFM and system was > partitioned out. However, I was also trying to test SAD and AutoIPL. > Nothing happened in that arena, so--as I do when all else fails--I > RTFM. Found this: > >

Re: Testing SFM policy

> You can write a simple assembler program to load a WAIT PSW that is > disabled for interrupts or you can modify the RESTART NEW PSW in the > PSW with the wait bit on and disabled for interrupts. > > If you use the RESTART NEW PSW, then a PSW RESTART should result in > your system going into a

Re: MCS console sharing in a sysplex

On Jun 7, 2016, at 3:08 PM, baby eklavya wrote: > > To my understanding , when sharing MCS consoles in a sysplex , one thing > which matters is the console name which has to be unique for each LPAR even > though the UCB can be the same . Then again , console uses EXCP to

Re: MCS console sharing in a sysplex

On Tue, Jun 7, 2016 at 3:08 PM, baby eklavya wrote: > Hi Listers , > > To my understanding , when sharing MCS consoles in a sysplex , one thing > which matters is the console name which has to be unique for each LPAR even > though the UCB can be the same . Then again ,

Re: Testing SFM policy

For completeness I'm posting the 'Wait state action table (WSAT)', which determines the DIAGxx action(s) to take for various wait states. I'm surprised at how short this table is. Entries are of the form fwww, where f represents flags represents the reason code www represents the wait

MCS console sharing in a sysplex

Hi Listers , To my understanding , when sharing MCS consoles in a sysplex , one thing which matters is the console name which has to be unique for each LPAR even though the UCB can be the same . Then again , console uses EXCP to write the screen of data each time . Since the UCB is shared , how

Re: Testing SFM policy

You can write a simple assembler program to load a WAIT PSW that is disabled for interrupts or you can modify the RESTART NEW PSW in the PSW with the wait bit on and disabled for interrupts. If you use the RESTART NEW PSW, then a PSW RESTART should result in your system going into a wait state.

Re: Testing SFM policy

When I saw your original post, the first thing I thought of was a program that sets the PSW so it can't be interrupted, then loops for a time (while checking the clock) before exiting. ATTACH a few of these tasks and maybe you could take over all CPU's and better simulate the bad-dog. Just a

Re: Testing SFM policy

Testing was semi-successful. On one hand, QUIESCE stopped the system. Missing heartbeat was detected by SFM and system was partitioned out. However, I was also trying to test SAD and AutoIPL. Nothing happened in that arena, so--as I do when all else fails--I RTFM. Found this: "For restartable

Re: TCPIP Help

Scott- We had issues with IND$FILE through our TN3270 client when we were using a Session manager. Just a thought. Cheryl -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Scott Ford Sent: Monday, June 06, 2016 6:41 PM To:

Re: SRB SUSPEND exit curiosity

On 6/7/2016 8:41 AM, michelbutz wrote: Can someone tell me what the advantage of this Is then using IEAVPSE2 is it performance I think they both set up a SSRB SUSPEND/RESUME w/TOKEN *only* works for SRBs. Pause/Release works for both tasks and SRBs. Performance wise, SUSPEND/RESUME w/Token

Decryption failure - Invalid Key Exception on Java for zOS

Hi All, We have recently created a RACF digital certificate and it is used to encrypt a file on the Postilion server. Later the file is transferred to the Mainframes and when we try to decrypt the file, we are getting below error: Caught GeneralSecurityException: null

Re: SRB SUSPEND exit curiosity

Can someone tell me what the advantage of this Is then using IEAVPSE2 is it performance I think they both set up a SSRB Sent from my iPhone > On Jun 7, 2016, at 11:27 AM, Greg Dyck wrote: > > On 6/6/2016 6:54 AM, Steve Smith wrote: > > I'm wondering what an SRB SUSPEND

Re: SRB SUSPEND exit curiosity

On 6/6/2016 6:54 AM, Steve Smith wrote: > I'm wondering what an SRB SUSPEND exit is really good for. The Services Guide and Reference state that it is required, and that it is supposed to save the SUSPEND token, and decide whether to allow the SUSPEND. I can't see why the SRB mainline

Re: Determine the PDS a job was submitted from?

Among the tasks that I am now responsible for maintaining, there is a suite of programs written in Assembler that manufacture jobs, by building the text and writing them directly to the internal reader. There is never any PDS member or source involve.

Re: Determine the PDS a job was submitted from?

Charles, We generate JCL from SAS programs on Windows and write them direct to JES with FTP. filename jesftp0ftp '.submit' USER="" host="" PASS="" rcmd='site file=jes' passive; The sample is from within a SAS macro, so

Re: Testing SFM policy

I will proceed with QUIESCE once our automation SME is ready to test. Key goal is to capture the partitioning message on another member of the sysplex and blast out some alerts. In a recent failure at oh-dark-thirty on a Saturday morning, Ops did not notice the wait state failure (SQA

Re: Survery PDSE MAXGENS_LIMIT

Tony, I wasn't trying to stress test it. I'm looking for an improvement in recovering from finger checks. REC ON doesn't help once the member is saved :-( and backups aren't up to the minute. I like this. Ron -Original Message- From: IBM Mainframe Discussion List

Re: Determine the PDS a job was submitted from?

Yes, that's the standard way of doing it in Zeke - you define the schedule time and/or the conditions that must be satisfied and also the member name and library that is the source of the job. However, Zeke also allows for dynamically created schedule queue records (SQRs), whereby Zeke

Re: Determine the PDS a job was submitted from?

Caveat: daily digestion implies response delays... As was discussed extensively on IBM-Main before (Jan, Feb?), for all other methods besides 'automation' submission, you're outta luck. 'specially in a sysplex environment where conversion and xeq'tion could occur in different locations. For

Re: Determine the PDS a job was submitted from?

Don't know. Kees. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: 07 June, 2016 16:36 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Determine the PDS a job was submitted from? On 2016-06-07, at 08:18, Vernooij, CP

Re: Determine the PDS a job was submitted from?

On 2016-06-07, at 08:18, Vernooij, CP (ITOPT1) - KLM wrote: > With IOF you can select a job that has run, edit the input JCL and submit it > again. This job is exactly the job from your production JCL library, but > doesn't come from there. > Does it preserve RECFM and LRECL of SYSINs? --

Re: Determine the PDS a job was submitted from?

With IOF you can select a job that has run, edit the input JCL and submit it again. This job is exactly the job from your production JCL library, but doesn't come from there. Kees. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of

Re: Determine the PDS a job was submitted from?

On Tue, 7 Jun 2016 08:26:41 -0500, Tom Marchant wrote: >On Mon, 6 Jun 2016 16:08:30 -0500, Paul Gilmartin wrote: > >>a programmer might >>have typed JCL from scratch in an editor then SUBMIT on the command >>line. > >I sometimes do that from within SDSF using line command SJ. >And I frequently

Re: Determine the PDS a job was submitted from?

On Tue, 7 Jun 2016 09:21:40 -0400, Charles Mills wrote: >> Or from a Windows file, if you're so afflicted. > >Really? Without first copying it to a mainframe file or dataset? > Sure.: ftp zos user password quote site filetype=JES put JCL somename quit (Haven't actually

Re: Determine the PDS a job was submitted from?

On Tue, Jun 7, 2016 at 8:46 AM, Charles Mills wrote: > Ah! You're right. But the job goes off into never-never land. I have only > used GET which submits a local JCL (on the FTP server mainframe) file or > dataset and retrieves the SYSOUT back to the submitting FTP client. >

Re: [EXTERNAL] Re: Survery PDSE MAXGENS_LIMIT

One interesting anomaly with PDSE generations is if you delete a member using tso delete then the generations are not deleted. If you use LMMDEL to delete a member (you can't delete an individual generation) then the member and all generations are deleted. BUT the anomaly is that if you then

Re: Determine the PDS a job was submitted from?

Ah! You're right. But the job goes off into never-never land. I have only used GET which submits a local JCL (on the FTP server mainframe) file or dataset and retrieves the SYSOUT back to the submitting FTP client. BTW, I *think* you mean quote SITE filetype=jes Charles -Original

Re: Survery PDSE MAXGENS_LIMIT

On Mon, 6 Jun 2016 20:08:32 -0500, TonyB-IBM-MAIN wrote: >Does the generation counter get incremented when a member is output of a batch >job? AFAIK, when a member is written, the normal (default) behavior is to create it as a new generation if that is the way the PDSE was created. An old

Re: Determine the PDS a job was submitted from?

On Tue, Jun 7, 2016 at 8:21 AM, Charles Mills wrote: > > Or from a Windows file, if you're so afflicted. > > Really? Without first copying it to a mainframe file or dataset? > ​Sure. Use ftp ftp zos quote filetype=jes​ put myjob.jcl > > Charles > > -- The unfacts, did we

Re: Determine the PDS a job was submitted from?

> Or from a Windows file, if you're so afflicted. Really? Without first copying it to a mainframe file or dataset? Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Monday, June 06, 2016 8:12 PM To:

Re: Determine the PDS a job was submitted from?

On Mon, 6 Jun 2016 16:08:30 -0500, Paul Gilmartin wrote: >a programmer might >have typed JCL from scratch in an editor then SUBMIT on the command >line. I sometimes do that from within SDSF using line command SJ. And I frequently resubmit a job the same way. -- Tom Marchant

Re: Testing SFM policy

Mark and Skip: I can assure you that QUIESCE will stop the XCF heartbeat. I have used it often in training to demonstrate the loss of heartbeat and triggering the sysplex to respond to the loss of a member. With an active SFM policy, it will trigger your desired action. The advantage to

Re: Determine the PDS a job was submitted from?

Yes... I recall some discussion awhile back with the consensus being a “likely no”. I wanted to make sure I was not missing something. Thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to

Re: new IBM Knowledge Center

It has some good points. I,also, prefer to download the pdf's as needed. There are times that I have to move around inside the same document and having the pdf downloaded just makes the job easier for me. On Tuesday, June 7, 2016 7:38 AM, Jon Butler wrote: Jack, 

Re: new IBM Knowledge Center

Jack, Oy it is because I like it for the very reason you state: it's easier to search. It appears to actually consider the terms you enter in the search field. Did someone at IBM look at Google Scholar search? However, like you, if I don't really know what I need it may be a bit dicey.

Re: Testing SFM policy

No system escapes from the System Reset button on the HMC. This is how we tested our CF failure procedures. Kees. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Rob Schramm Sent: 07 June, 2016 2:42 To: IBM-MAIN@LISTSERV.UA.EDU

Re: Determine the PDS a job was submitted from?

We discussed this a few months ago. General answer: no. Kees. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter Ten Eyck Sent: 06 June, 2016 21:09 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Determine the PDS a job was submitted from?

Re: z/OS 2.2 JES2 ABEND S878-10 during startup

5MB is huge for 24-Bit CSA. You can work out from SMF 79-2 almost all you need to know to manage this, including which storage keys are big and how much CSA is free. Cheers, Martin Sent from my iPad > On 7 Jun 2016, at 06:30, Bruce Hewson wrote: > > Hi Lizette, > >