Re: "New" Java-less Operating System Messages blips like crazy

2017-06-13 Thread David Crayford
On 11/06/2017 7:15 AM, Ed Jaffe wrote: On 6/6/2017 8:54 PM, David Crayford wrote: On 7/06/2017 1:43 AM, Ed Jaffe wrote: We test (E)JES Web with current releases of Chrome, Firefox, Opera, Safari, and IE. We also test with IE8 because it's a different animal and requires special code to make

Re: IBM customer anchor

2017-06-13 Thread scott Ford
Steve, This is exactly as Charles stated we want to do. Scott On Tue, Jun 13, 2017 at 10:51 PM Steve Thompson wrote: > On 06/13/2017 09:06 PM, John McKown wrote: > > On Tue, Jun 13, 2017 at 5:44 PM, Charles Mills wrote: > > > >> As a user of the word, you

Re: IBM customer anchor

2017-06-13 Thread Steve Thompson
On 06/13/2017 09:06 PM, John McKown wrote: On Tue, Jun 13, 2017 at 5:44 PM, Charles Mills wrote: As a user of the word, you really, really want to think about upward compatibility. Don't store the address of your product's anchor table there. Assume you will someday have

Re: EREP Symptom and/or Software Records

2017-06-13 Thread Lizette Koehler
So Logrec has two types of sysprogs using it the ones that want to know everything that is going on - read it hourly (i use to do that) the ones that only look at it when it is associated with a problem. (i do that now.) If your shop has a lot of issues with software and/or hardware, then

Re: Notify Type in Apar

2017-06-13 Thread Dan Little
I believe it means the Hiper flag is being removed from the APAR for some reason. Perhaps there is a different root cause than originally thought or something like that. Thanks. Dan On Jun 13, 2017, 12:35 PM -0400, Gilson Cesar de Oliveira , wrote: > > > > > Dear list: >

Re: IBM customer anchor

2017-06-13 Thread John McKown
On Tue, Jun 13, 2017 at 5:44 PM, Charles Mills wrote: > As a user of the word, you really, really want to think about upward > compatibility. Don't store the address of your product's anchor table > there. Assume you will someday have multiple products. You would want to >

Re: EREP Symptom and/or Software Records

2017-06-13 Thread Edward Gould
> On Jun 13, 2017, at 4:24 PM, Turner Cheryl L wrote: > > Greetings. > Our former sysprog, who paid attention to the more finer system details, has > left the building for greener pastures. So now we seem to have to step up > our game. However, I'm not sure what to

Re: Wacko S722 abend

2017-06-13 Thread Edward Gould
> On Jun 13, 2017, at 2:36 PM, Porowski, Kenneth wrote: > > One reason people will code 0 linecount/cardcount in the jobcard is that it > can affect the jes input queue priority. On systems where queuing is > frequent this is one way to get your job bumped to the top or

Re: IBM customer anchor

2017-06-13 Thread Charles Mills
As a user of the word, you really, really want to think about upward compatibility. Don't store the address of your product's anchor table there. Assume you will someday have multiple products. You would want to store the address of a vector of anchor table addresses. Think about upward

Re: EREP Symptom and/or Software Records

2017-06-13 Thread Jesse 1 Robinson
Those IBM supplied SLIP traps are generally there to suppress irrelevant SVC dumps: SL SET,C=13E,ID=X13E,A=NODUMP,END Imagine what would happen if you got a dump for each S13E in addition to the LOGREC record? The truth is that some abends relating to 'improper' termination cleanup are just

EREP Symptom and/or Software Records

2017-06-13 Thread Turner Cheryl L
Greetings. Our former sysprog, who paid attention to the more finer system details, has left the building for greener pastures. So now we seem to have to step up our game. However, I'm not sure what to do or how. We are running several EREP reports to see what software or symptom records are

SMFLIMxx sample?

2017-06-13 Thread Pew, Curtis G
I’m going through our SMF exits and reviewing them. I was able to eliminate most of what IEFUSI was doing; all that was left was setting the REGION limits. Then reading the manual more carefully I discovered there’s a new (apparently starting in z/OS 2.2) PARMLIB member, SMFLIMxx, that can do

Re: IBM customer anchor

2017-06-13 Thread Steve Thompson
On 06/13/2017 08:35 AM, scott Ford wrote: All: I have a question about something called 'customer anchor table entry' . My colleague said IBM can provide this entry to a ISV like use so we can place an address there for routines. I think it's like a vector address . Has anyone heard of this ?

AW: Re: Wacko S722 abend

2017-06-13 Thread Peter Hunkeler
>This from the job card:>>JOB (TE000MEJIC,DK6D,,0),... Exactly the reason I asked to see the JCL. I was just too lazy to lookup the format of the accounting parameter, and thought I would recognize once I see it. Glad you found it. I always found it somewhat strange design that JES is trying

Re: Wacko S722 abend

2017-06-13 Thread Porowski, Kenneth
One reason people will code 0 linecount/cardcount in the jobcard is that it can affect the jes input queue priority. On systems where queuing is frequent this is one way to get your job bumped to the top or at least higher on the food chain. This email message and any accompanying materials

Re: Wacko S722 abend

2017-06-13 Thread Jesse 1 Robinson
Problem solved thanks to a colleague who put the right keywords on a Google search and found a past IBM-MAIN thread that provided the answer. This from the job card: JOB (TE000MEJIC,DK6D,,0),... In all my years I never learned about the 'other positional sub-parameters' of the accounting

AW: Re: Wacko S722 abend

2017-06-13 Thread Peter Hunkeler
Can you post the JCL? -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Java on z/OS?

2017-06-13 Thread Frank Swarbrick
Really? I swear I tried this under z/OS 1.13 and it did not work. Maybe I just assumed it, because all of the examples of using BPXBATCH don't write directly to SYSOUT. Frank From: IBM Mainframe Discussion List on behalf of Mark

Re: Wacko S722 abend

2017-06-13 Thread Allan Staller
Any OUTLIM coded in JCL? -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Tuesday, June 13, 2017 12:49 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Wacko S722 abend On Tue, Jun 13, 2017 at 12:41 PM, Jesse 1 Robinson

Re: Wacko S722 abend

2017-06-13 Thread John McKown
On Tue, Jun 13, 2017 at 12:41 PM, Jesse 1 Robinson wrote: > I don't want to turn this into a debugging session. We plan to open an SR > with IBM. Just to verify what I've said, here are some lines from the job > log. The first step is vanilla CA11. That's where the job

Re: Wacko S722 abend

2017-06-13 Thread Jesse 1 Robinson
I don't want to turn this into a debugging session. We plan to open an SR with IBM. Just to verify what I've said, here are some lines from the job log. The first step is vanilla CA11. That's where the job dies. We completely removed the CA11 step; same result. I was just looking for any 'me

Re: Wacko S722 abend

2017-06-13 Thread Tony Harminc
On 13 June 2017 at 12:46, Jesse 1 Robinson wrote: > ESTLNCT NUM=2,INT=2,OPT=1 > > We changed NUM from the old value, but added OPT=1 to cancel the job with > no dump. On this system only, a particular job started getting S722 for no > apparent reason. It

Re: Wacko S722 abend

2017-06-13 Thread Elardus Engelbrecht
Jesse 1 Robinson wrote: >I'm posting this here because I was asked too. It's beyond crazy. As I >indicated earlier, we are trying to reduce spool full conditions by limiting >job output via ESTLNCT. Yesterday we set the limit on one system like this: >ESTLNCT NUM=2,INT=2,OPT=1 >We

Wacko S722 abend

2017-06-13 Thread Jesse 1 Robinson
I'm posting this here because I was asked too. It's beyond crazy. As I indicated earlier, we are trying to reduce spool full conditions by limiting job output via ESTLNCT. Yesterday we set the limit on one system like this: ESTLNCT NUM=2,INT=2,OPT=1 We changed NUM from the old value,

Re: Sorting a REXX STEM variable

2017-06-13 Thread Nims,Alva John (Al)
BPXWUNIX is available to z/OS 1.13 too, so this should work under z/OS 1.13. I am using BPXWUNIX to invoke USS dig command get info from the DNS server. Al Nims Systems Admin/Programmer 3 UFIT University of Florida (352) 273-1298 -Original Message- From: IBM Mainframe Discussion List

Notify Type in Apar

2017-06-13 Thread Gilson Cesar de Oliveira
> >Dear list: Does anyone know the meaning of Notify Type= Hyper DEL in apar?? I have received a notification today but I could not find the meaning of thid Notify Type. Thanks for any help. Regards, Gilson -- For IBM-MAIN

Re: Estae and the Linkage Stack

2017-06-13 Thread David Cole
At 6/13/2017 09:07 AM, Joseph Reichman wrote: So PC inst will also un-define an ESTAE No... Only the PR will "un-define" an ESTAE. PC is more similar in functionality to a BAKR than to a PR. Both PCs and BAKRs create stack entries. Only the PR removes them. When a PR removes a stack entry,

Re: IBM customer anchor

2017-06-13 Thread Charles Mills
Yep! That's what we did. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tony Thigpen Sent: Tuesday, June 13, 2017 5:45 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IBM customer anchor Recently came across this too. In

Re: Sorting a REXX STEM variable

2017-06-13 Thread Albert Ferguson
Under zOS REXX does have a STEM Sort (via BPXWUNIX). If you have an OMVS Segment on your USERID (and as of zOS 2.1+ you should), try this: /* Do a Binary Sort (use -tn for Text) Using 2nd Word in each StemIn. Record as primary sort key Using 1st Word in each StemIn. Record as

Re: Estae and the Linkage Stack

2017-06-13 Thread Joseph Reichman
So PC inst will also un-define an ESTAE > On Jun 13, 2017, at 9:05 AM, Greg Dyck wrote: > >> On 6/13/2017 2:55 AM, David Cole wrote: >> PRs do automagically cancel all ESTAEs created since the matching BAKR. >> There is a bit (in the BAKR's stack entry I think. I forget

Re: Estae and the Linkage Stack

2017-06-13 Thread Greg Dyck
On 6/13/2017 2:55 AM, David Cole wrote: PRs do automagically cancel all ESTAEs created since the matching BAKR. There is a bit (in the BAKR's stack entry I think. I forget which and where.) that, when set on, causes an interrupt to occur when the PR is issued. This is how z/OS gains control so

Re: Estae and the Linkage Stack

2017-06-13 Thread Blaicher, Christopher Y.
Yes they will stay defined. If you define an ESTAE at the beginning of a program, outside of a linkage stack entry, you can create and delete all the linkage stack entries you want and it will still be there. You could create a linkage stack entry on entry to your program rather than chaining

Re: Estae and the Linkage Stack

2017-06-13 Thread Joseph Reichman
Will the ESTAE remain active if declared outside of the BAKR/PR pair David from you description it should > On Jun 13, 2017, at 3:55 AM, David Cole wrote: > > BAKRs do not create or cancel ESTAEs. > > PRs do automagically cancel all ESTAEs created since the matching

Re: IBM customer anchor

2017-06-13 Thread Tony Thigpen
Recently came across this too. In CBT841 files: "CONTACT PETER RELSON, rel...@us.ibm.com FOR YOUR OWN OFFSET IN THE CUSTOMER ANCHOR TABLE. ONCE YOU HAVE RECEIVED YOUR ASSIGNED VALUE MODIFY.." Also, in the same CBT: "A possible address off the Customer Anchor Table, X'CC' off the ECVT, could

IBM customer anchor

2017-06-13 Thread scott Ford
All: I have a question about something called 'customer anchor table entry' . My colleague said IBM can provide this entry to a ISV like use so we can place an address there for routines. I think it's like a vector address . Has anyone heard of this ? -- Regards, *IDMWORKS * Scott Ford

Re: Estae and the Linkage Stack

2017-06-13 Thread David Cole
BAKRs do not create or cancel ESTAEs. PRs do automagically cancel all ESTAEs created since the matching BAKR. There is a bit (in the BAKR's stack entry I think. I forget which and where.) that, when set on, causes an interrupt to occur when the PR is issued. This is how z/OS gains control so

Re: Customer is Using CPACF (Crypto) purchased Crypto Express

2017-06-13 Thread Arye Shemer
Thank you all for your contribution and time. It sure gave me a lot to think of. thanks, Arye. On Mon, Jun 12, 2017 at 6:44 PM, Phil Smith wrote: > There are several things intertwined here. > > > * CPACF is the "crypto on the chip" - z Systems instructions that do >