AW: Re: AW: Re: How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

> >The exit 6 that I modified from the version done by Glenn Harper at >[snip] Exit 6 is JES2 Exit 6, I assume, and this is run in a JES2 context, so it has access to JES2 "data", such as the JESYSMSG ACB. I doubt SMS has access to that information when writing IGD* message upon data set

Re: AW: Re: How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

[Default] On 27 Oct 2016 03:32:19 -0700, in bit.listserv.ibm-main p...@gmx.ch (Peter Hunkeler) wrote: >>It is route code 11. specify that on your WTO macro . > > >No, it s not. As I wrote, WTO with route code 11 goes to JESMSGLG and JESYSMSG >(and also to consoles which receive route code 11).

AW: Re: How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

> Isn't your finding what I wrote to you few emails ago...? I was asking how to write a message to JESYSMSG, only. You answered, a WTO with route code 11 will do that. At least this is how I understood. If this is what you are referring to, then no. WTO with route code 11 writes to

Re: AW: Re: How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

Peter Hunkeler wrote: >After reading about IEFACTRT in "Installation Exits" I conclude that IEFYScan >only be used by this exit. You need what is passed in R12 to IEFACTRT to be >able to address the parameter list for IEFYS. And again this text talks about >"...writing to the JOBLOG..." which

Re: How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

Isn't your finding what I wrote to you few emails ago...? ITschak ITschak Mugzach Z/OS, ISV Products and Application Security & Risk Assessments Professional On Thu, Oct 27, 2016 at 2:49 PM, Peter Hunkeler wrote: > > > > > >>It is route code 11. specify that on your WTO macro . >

AW: Re: How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

>From IEFACTRT we write to JESYSMSG with the IEFYS routine. After reading about IEFACTRT in "Installation Exits" I conclude that IEFYScan only be used by this exit. You need what is passed in R12 to IEFACTRT to be able to address the parameter list for IEFYS. And again this text talks about

Re: How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

>From IEFACTRT we write to JESYSMSG with the IEFYS routine. Are you sure the messages go to JESYSMSG (file 3) and not JESMSGLG (file 1)? I only seem to have ever seen messages from IEFACTRT, such as step statistics, appear in JESMSGLG. But me not having seen any in JESYSMSG does not mean

AW: Re: How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

>>It is route code 11. specify that on your WTO macro . >No, it s not. As I wrote, WTO with route code 11 goes to JESMSGLG and JESYSMSG >(and also to consoles which receive route code 11). At last I found the following in the *authorized* assembler service reference: WTO ... A WTO message

AW: Re: How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

>It is route code 11. specify that on your WTO macro . No, it s not. As I wrote, WTO with route code 11 goes to JESMSGLG and JESYSMSG (and also to consoles which receive route code 11). I'm wondering how to write to JESYSMGS *only*. -- Peter Hunkeler

Re: How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Jesse 1 Robinson > Sent: 26 October, 2016 23:47 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: How to write messages to JESYSMSG only? (was: Randomly > disappearing IGD101I messages) > > I can help a

Re: How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

ges to JESYSMSG only? (was: Randomly disappearing IGD101I messages) I can help a bit with the first question but not the other two. We have an ancient and venerable JES2 EXIT 6 that writes messages to JESYSMSG only. It uses the IFGRPL macro (AMODGEN). I did not write this part of the code, but I could s

Re: How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

Of Peter Hunkeler Sent: Friday, October 21, 2016 1:22 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages) Triggered by the discussion about randomly disappearing IGD101I message, I did some RTFM and some testing

AW: Re: Randomly disappearing IGD101I messages.

>Lizette, >You said you suppressed IGD1010I. Are you sure you got it in syslog without >suppressing it? > >Kees. I just posted the initial message for the new thread. Therein, I say that I have found a case of IGD103I and IGD104I in syslog (without the IEF196I prefix). So I'm pretty sure

How to write messages to JESYSMSG only? (was: Randomly disappearing IGD101I messages)

Triggered by the discussion about randomly disappearing IGD101I message, I did some RTFM and some testing to find out how to write a message only to JESYSMSG. I got contradicting information instead of an answer. So here it goes... It was may understanding from my experience that allocation

Re: Randomly disappearing IGD101I messages.

>A message is produced or not based on MPF list, Automation Tools, or a user >exit. The Vendors (IBM and BMC) should be able to help you determine why this >is going on. I do not know about automation's posibilities, but MPF does *not* suppress messages from the syslog/operlog. The SUP=YES

Re: Randomly disappearing IGD101I messages.

Subject: Re: Randomly disappearing IGD101I messages. >They are among the messages that (seem to) never appear in SYSLOG/OPERLOG, >only in the job's Allocation messages file. IGD101I is not trappable via SLIP >or MPFLST. They seem to be (like the IGD messages produces by the ACS routine

Re: Randomly disappearing IGD101I messages.

>They are among the messages that (seem to) never appear in SYSLOG/OPERLOG, >only in the job's Allocation messages file. IGD101I is not trappable via SLIP >or MPFLST. They seem to be (like the IGD messages produces by the ACS routines >WRITE statements) directly written to the job sysout.

Re: Randomly disappearing IGD101I messages.

this level. === From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Peter Hunkeler <p...@gmx.ch> Sent: Thursday, October 20, 2016 4:16 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: AW: Re: Randomly disappearing IGD101I messages. >Dynalloc's S99MSGL0 i

Re: Randomly disappearing IGD101I messages.

Peter: I haven’t worked with DMS lately. Having said that I vaguely remember DMS doing its own thing with DASD (i.e. creating a F4 DSCB and deb etc etc etc). Ed > On Oct 20, 2016, at 3:12 PM, Peter Hunkeler wrote: > > > > >> That might be a good point: different flows through

Re: Randomly disappearing IGD101I messages.

age- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter Hunkeler Sent: Thursday, October 20, 2016 3:13 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: AW: Re: Randomly disappearing IGD101I messages. All new allocations are seen by SMS's ACS routines. If they dec

Re: Randomly disappearing IGD101I messages.

Of Vernooij, Kees (ITOPT1) - KLM Sent: Thursday, October 20, 2016 2:51 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Randomly disappearing IGD101I messages. Greg, If you request to bypass SMS, no IGD101I can be expected. Can you create an example where things are left to SMS when possible? Kees

AW: Re: Randomly disappearing IGD101I messages.

>Dynalloc's S99MSGL0 is the equivalent of JCL's MSGLEVEL=0, ie. the allocation >of datasets to ddnames. Not equivalent, I would say. MSGLEVEL is for the whole job, S99MSGL0 is for a single allocation. -- Peter Hunkeler

AW: Re: Randomly disappearing IGD101I messages.

>That might be a good point: different flows through the program that set >different S99MSGLO flags. and it has nothing to do with "bypassing SMS". All new allocations are seen by SMS's ACS routines. If they decide to assign a Storage Class to the data set, then the data set is "SMS

Re: Randomly disappearing IGD101I messages.

Dynalloc's S99MSGL0 is the equivalent of JCL's MSGLEVEL=0, ie. the allocation of datasets to ddnames. Messages describing the details of actually creating new datasets on DASD are related to DADSM. Sent from my iPhone > On Oct 20, 2016, at 15:18, Peter Hunkeler wrote: > >

Re: Randomly disappearing IGD101I messages.

@LISTSERV.UA.EDU Subject: Re: Randomly disappearing IGD101I messages. >"So, it is DMS or FDR which decide whether to place those IGD* messages or >not." > -- Peter Hunkeler >To be precise: >It is DMS or FDR which decide to allocate the dataset via SMS or not, thereby

Re: Randomly disappearing IGD101I messages.

, 2016 5:19 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Randomly disappearing IGD101I messages. Here is a job which produced a new SMS-managed data set without generating an IGD101I message: //DPC088X JOB 111,NOTIFY=DPC088,CLASS=A,MSGLEVEL=(1,1) //STEP01 EXEC PGM=ADRDSSU,REGION=0M

Re: Randomly disappearing IGD101I messages.

>"So, it is DMS or FDR which decide whether to place those IGD* messages or >not." > -- Peter Hunkeler >To be precise: >It is DMS or FDR which decide to allocate the dataset via SMS or not, thereby >causing the IGD message to appear or not. PMFJI, I do not know but I seriously wonder if it

Re: Randomly disappearing IGD101I messages.

- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Vernooij, Kees (ITOPT1) - KLM Sent: Thursday, October 20, 2016 8:53 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Randomly disappearing IGD101I messages. "So, it is DMS or FDR which decide whether to place

Re: Randomly disappearing IGD101I messages.

ssion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Elardus Engelbrecht Sent: 20 October, 2016 15:49 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Randomly disappearing IGD101I messages. Vernooij, Kees (ITOPT1) - KLM wrote: >We found the answer. Excellent! >IGD101I is used by Control-M for t

Re: Randomly disappearing IGD101I messages.

Vernooij, Kees (ITOPT1) - KLM wrote: >We found the answer. Excellent! >IGD101I is used by Control-M for the 'disp=catalog' rule of dataset triggering. >IGD104I is used by Control-M for the 'disp=keep' rule of dataset triggering. >In the case of the DMS step IGD104I is always produced, so we

Re: Randomly disappearing IGD101I messages.

reliable indicator for dataset creation and we will report this to BMC. Kees. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Vernooij, Kees (ITOPT1) - KLM Sent: 18 October, 2016 11:04 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Randomly di

Re: Randomly disappearing IGD101I messages.

Koehler Sent: Wednesday, October 19, 2016 9:26 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Randomly disappearing IGD101I messages. In my case we have automation suppressing the messages. However, I will see them occasionally when it is preceded by an IEF196I message IEF196I IGD101I Our

Re: Randomly disappearing IGD101I messages.

sage- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Elardus Engelbrecht > Sent: 19 October, 2016 12:44 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Randomly disappearing IGD101I messages. > > Vernooij, Kees (ITOPT1) - KLM wrote: >

Re: Randomly disappearing IGD101I messages.

] On Behalf Of Elardus Engelbrecht Sent: 19 October, 2016 12:44 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Randomly disappearing IGD101I messages. Vernooij, Kees (ITOPT1) - KLM wrote: >Well, the situation is becoming more and more curious: - I checked 400 runs of the job in the last year and IGD1

Re: Randomly disappearing IGD101I messages.

Vernooij, Kees (ITOPT1) - KLM wrote: >Well, the situation is becoming more and more curious: - I checked 400 runs of the job in the last year and IGD101I appears in 2/3 of the jobs and does not appear in 1/3 of the jobs, without an indication of why Ok, try this temporary workaround: In

Re: Randomly disappearing IGD101I messages.

] On Behalf Of Vernooij, Kees (ITOPT1) - KLM Sent: 19 October, 2016 8:18 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Randomly disappearing IGD101I messages. Bob, I could not find any difference between the steps with and without IGD101I. The JCL is the same, the output dataset cannot exist because

Re: Randomly disappearing IGD101I messages.

: Randomly disappearing IGD101I messages. When CA Disk moves SMS data sets, it renames the original to a temporary name and creates the new one with the existing name. If the new data set is correctly created, cataloged, written, and closed, then CA Disk deletes the original (now renamed) data set

Re: Randomly disappearing IGD101I messages.

: Randomly disappearing IGD101I messages. I would suggest asking CA about the DMS step not generating the IGD101I message. (DMS has a "hook" in SMS, doesn't it?) Regards, Greg Shirey Ben E. Keith Company -Original Message- From: IBM Mainframe Discussion List [mailt

Re: Randomly disappearing IGD101I messages.

ehler Sent: Tuesday, October 18, 2016 8:46 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Randomly disappearing IGD101I messages. One I see BMC has asked for doc. I would definitely do that. Two, I concur with Tom Conley, Most scheduling software will provide an SMF Exit in order to see whe

Re: Randomly disappearing IGD101I messages.

Vernooij, Kees (ITOPT1) - KLM wrote: >Two: IGD101I seems to be among those messages that are only/directly sent to >the job's allocation message file and never make it to the Syslog/Operlog and >are never seen by SLIP, MPFLST and other automation tools that scan the >subsystem interface for

Re: Randomly disappearing IGD101I messages.

Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler Sent: 18 October, 2016 15:46 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Randomly disappearing IGD101I messages. One I see BMC has asked for doc. I would definitely do that. Two, I concur with Tom Conley, Most scheduling

Re: Randomly disappearing IGD101I messages.

UA.EDU] On > Behalf Of Vernooij, Kees (ITOPT1) - KLM > Sent: Tuesday, October 18, 2016 6:36 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Randomly disappearing IGD101I messages. > > We verified that the problem exists for at least a couple of months. > Kees. > > -

Re: Randomly disappearing IGD101I messages.

> Sent: 18 October, 2016 15:32 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Randomly disappearing IGD101I messages. > > Vernooij, Kees (ITOPT1) - KLM wrote: > > >Via a DMS COPY step. Always. Can't find any suppression, nor do I specify > route of desc codes for IBM's

Re: Randomly disappearing IGD101I messages.

ctober, 2016 15:32 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Randomly disappearing IGD101I messages. > > Vernooij, Kees (ITOPT1) - KLM wrote: > > >Via a DMS COPY step. Always. Can't find any suppression, nor do I specify > route of desc codes for IBM's IGD messages. >

Re: Randomly disappearing IGD101I messages.

disappearing IGD101I messages. Vernooij, Kees (ITOPT1) - KLM wrote: >Via a DMS COPY step. Always. Can't find any suppression, nor do I specify >route of desc codes for IBM's IGD messages. >They are among the messages that (seem to) never appear in SYSLOG/OPERLOG, >only in the job's Allocat

Re: Randomly disappearing IGD101I messages.

Vernooij, Kees (ITOPT1) - KLM wrote: >Via a DMS COPY step. Always. Can't find any suppression, nor do I specify >route of desc codes for IBM's IGD messages. >They are among the messages that (seem to) never appear in SYSLOG/OPERLOG, >only in the job's Allocation messages file. IGD101I is not

Re: Randomly disappearing IGD101I messages.

:09 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Randomly disappearing IGD101I messages. Vernooij, Kees (ITOPT1) - KLM wrote: >I would circumvent the problems (if I can get BMC to redesign their way of >working), but still the question remains, why the message sometimes disappear. Question

Re: Randomly disappearing IGD101I messages.

@LISTSERV.UA.EDU Subject: Re: Randomly disappearing IGD101I messages. Hi Kees, Are there any allocation messages issued? The MSGLEVEL parameter controls whether allocation messages are issued to the JESYSMSG sysout. Make sure it is (1,1) in all executions. Otherwise, please open a ticket with BMC

Re: Randomly disappearing IGD101I messages.

15:56 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Randomly disappearing IGD101I messages. I would circumvent the problems (if I can get BMC to redesign their way of working), but still the question remains, why the message sometimes disappear. Kees. -Original Message- From: IBM Mainframe

Re: Randomly disappearing IGD101I messages.

Vernooij, Kees (ITOPT1) - KLM wrote: >I would circumvent the problems (if I can get BMC to redesign their way of >working), but still the question remains, why the message sometimes disappear. Question - how are they allocated? Via JCL DD statements or via dynalloc? Is SMS *always* used in

Re: Randomly disappearing IGD101I messages.

October, 2016 14:53 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Randomly disappearing IGD101I messages. On 10/18/2016 5:04 AM, Vernooij, Kees - KLM , ITOPT1 wrote: > Hello, > > Control-M uses message IGD101I for dataset triggering: when a data set has > been created, as indicated by IGD101I

Re: Randomly disappearing IGD101I messages.

On 10/18/2016 5:04 AM, Vernooij, Kees - KLM , ITOPT1 wrote: Hello, Control-M uses message IGD101I for dataset triggering: when a data set has been created, as indicated by IGD101I, a job must be triggered. We see every now and then that the triggering is not working, because IGD101I is not

Re: Randomly disappearing IGD101I messages.

@LISTSERV.UA.EDU Subject: Re: Randomly disappearing IGD101I messages. kees, are you sure that the expected dataset that shoud be reported by IGD101I is allocated new? ITschak Mugzach Z/OS, ISV Products and Application Security & Risk Assessments Professional On Tue, Oct 18, 2016 at 2:39 PM, Vernooij,

Re: Randomly disappearing IGD101I messages.

@LISTSERV.UA.EDU] On Behalf Of Greg Shirey Sent: 18 October, 2016 14:25 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Randomly disappearing IGD101I messages. Kees, How are you verifying the data set was created? Regards, Greg Shirey Ben E. Keith Company -Original Message- From: IBM Mainframe

Re: Randomly disappearing IGD101I messages.

13:31 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Randomly disappearing IGD101I messages. > > Are all allocations are SMS managed? May be SMS is not involved in some of > the allocations, or the dataset was not allocated as new in some cases. > > ITschak > > ITsc

Re: Randomly disappearing IGD101I messages.

@LISTSERV.UA.EDU Subject: Re: Randomly disappearing IGD101I messages. No, everything is equal in all jobs (from what I could check), except the appearance of the message. -- For IBM-MAIN subscribe / signoff / archive access

Re: Randomly disappearing IGD101I messages.

Subject: Re: Randomly disappearing IGD101I messages. Are all allocations are SMS managed? May be SMS is not involved in some of the allocations, or the dataset was not allocated as new in some cases. ITschak ITschak Mugzach Z/OS, ISV Products and Application Security & Risk Assessments Professi

Re: Randomly disappearing IGD101I messages.

ype of messages? > > Kees. > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Elardus Engelbrecht > Sent: 18 October, 2016 12:32 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Randomly disappearing IGD101I messages. >

Re: Randomly disappearing IGD101I messages.

[mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Elardus Engelbrecht Sent: 18 October, 2016 12:32 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Randomly disappearing IGD101I messages. Vernooij, Kees (ITOPT1) - KLM wrote: >Everything is equal, no errors, only IGD101I is sometimes missing and we h

Re: Randomly disappearing IGD101I messages.

Vernooij, Kees (ITOPT1) - KLM wrote: >Everything is equal, no errors, only IGD101I is sometimes missing and we have >no idea why. Ok, where is that message displayed? Joblog or Syslog or where? What is the Route and Descriptor code where you expect the message to be shown? Perhaps you should

Re: Randomly disappearing IGD101I messages.

: Re: Randomly disappearing IGD101I messages. Vernooij, Kees (ITOPT1) - KLM wrote: >Control-M uses message IGD101I for dataset triggering: when a data set has >been created, as indicated by IGD101I, a job must be triggered. Isn't that Control-O which scans the SYSLOG? Or am I missing som

Re: Randomly disappearing IGD101I messages.

Vernooij, Kees (ITOPT1) - KLM wrote: >Control-M uses message IGD101I for dataset triggering: when a data set has >been created, as indicated by IGD101I, a job must be triggered. Isn't that Control-O which scans the SYSLOG? Or am I missing something in your setup? >We see every now and then

Randomly disappearing IGD101I messages.

Hello, Control-M uses message IGD101I for dataset triggering: when a data set has been created, as indicated by IGD101I, a job must be triggered. We see every now and then that the triggering is not working, because IGD101I is not produced, although the dataset has been created. We don't have