Re: how to keep messages in the sys1.broadcast for ever

> On Jun 28, 2017, at 10:27 PM, Lizette Koehler wrote: > > There are commands you can use to update the SYS1.BRODCAST for SAVEd message. > > If you can download the broadcast tool from cbttape.org, it can be helpful. > > To list all messages in the notices section of

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

> On Jun 28, 2017, at 6:11 PM, Paul Gilmartin > <000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > > On Wed, 28 Jun 2017 16:24:16 -0500, Edward Gould wrote: >> >> We had a fool proof naming standard at one installation. It has been working >> for 25+ years and not even one word is/was

Re: how to keep messages in the sys1.broadcast for ever

Now, a different process is to create a TSO Logon REXX/CLIST that does what you want. Then you do not need to worry about SYS1.BRODCAST. You can add that in your TSO LOGON proc so when the user Logs on, they get the message you want for them to see.. Lizette > -Original Message- >

Re: how to keep messages in the sys1.broadcast for ever

There are commands you can use to update the SYS1.BRODCAST for SAVEd message. If you can download the broadcast tool from cbttape.org, it can be helpful. To list all messages in the notices section of the SYS1.BRODCAST data set, enter: SE LIST Then you can delete the message by msgno Then you

Re: how to keep messages in the sys1.broadcast for ever

Hi When we logon TSO, we want to tell everyone which system we logon by Broadcast message. it is ok now Because the system name was changed , we didn't know how to change it in the broadcast. == The broadcast dataset is not a repository for long term retention. It is considered

Re: how to keep messages in the sys1.broadcast for ever

The broadcast dataset is not a repository for long term retention. It is considered temporary. When a user logs on, any messages for that user are retrieved. If this does not occur, the SYS1.BRODCAST dataset will fill up and a failure to log the message to the SYS1.BRODCAST dataset will be

how to keep messages in the sys1.broadcast for ever

hi all Could you tell us how to keep messages in the sys1.broadcast for ever ? Thanks a lot! Jason Cai -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the

Re: Logstreams

Just so. We start up our systems on SYS1.LOGREC and convert to logstream once logger services are available (SETLOGRC command issued via automation). I converted both SMF and SYSLOG to logstreams with no dramas. This site had syslogs stored by system-id, so I modified SAMPLIB(IEAMDBLG) to

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

On 2017-06-28, at 18:11, Frank Swarbrick wrote: > Job cards are dead easy to code: > > //MYJOB JOB > > What can be simpler? I personally add a notify: > > //MYJOB JOB NOTIFY= > > Now if SUB could use, say, the PDS/PDSE member name as the job name and add a > NOTIFY= then that could be great

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

I do. I (me I mean) totally do. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Charles Mills Sent: keskiviikko 28. kesäkuuta 2017 23.42 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Sources of message: IKJ56700A ENTER JOBNAME

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

Spot on Peter. But we have to admit, one of the challenges that makes working with z/OS that makes it fun is to figure out how things are setup. It's basically legal hacking, and I quite don't like it. I mean, when I pretend I am Sherlock Holmes, I like it, but I don't get that privilege

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

Well for historical (hysterical) reasons, mine need to look more like this: //GIBNEY JOB (0495),'GIBNEY',MSGLEVEL=(1,1), // MSGCLASS=T,CLASS=S,NOTIFY=GIBNEY /*JOBPARM LINES=999 /*BIN ITB2163 /*ID GIBNEY

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

Job cards are dead easy to code: //MYJOB JOB What can be simpler? I personally add a notify: //MYJOB JOB NOTIFY= Now if SUB could use, say, the PDS/PDSE member name as the job name and add a NOTIFY= then that could be great as well! Related question: We don't specify NOTIFY on production

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

On Wed, 28 Jun 2017 16:24:16 -0500, Edward Gould wrote: > >We had a fool proof naming standard at one installation. It has been working >for 25+ years and not even one word is/was ever said against the standard. I >wrote it and it rock solid. > What names did it govern? Why? How resourceful

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

On 28 June 2017 at 16:10, Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu> wrote: >>Some of us do not get to make the rules ourselves, or even have any input on >>what the rules are. >> > http://mistupid.com/people/page058.htm Which is isomorphic to Ken Thompson's Reflections on

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

> On Jun 28, 2017, at 3:44 PM, Wayne Bickerdike wrote: > > I think in my days at IBM we had job name standards that were enforced as > UID + 1 char. > > This may explain why many times I never bother coding a job card for > trivial jobs and once the job has run, I perform an

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

> On Jun 28, 2017, at 3:10 PM, Paul Gilmartin > <000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > > On Wed, 28 Jun 2017 15:36:25 -0400, Farley, Peter x23353 wrote: > >> All well and good when the shop standard does not mandate TSO userid as job >> name for *all* non-privileged users,

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

On 28 June 2017 at 14:57, Jesse 1 Robinson wrote: > I love this business because I learn something every day. After wiping egg > off my face. ;-) No egg; we all live in slightly different mainframe worlds. I'm forever amazed to discover that some neat new trick in ISPF

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

I think in my days at IBM we had job name standards that were enforced as UID + 1 char. This may explain why many times I never bother coding a job card for trivial jobs and once the job has run, I perform an SJ command, cut ALL and paste ALL back into the JCL library to have a syntactically

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

Does he know about the First Unitarian Church of Kennebunk, Me? There's a story that the Ladies Auxiliary was unable to purchase monogramed aprons. (Actually existed, now renamed the Unitarian Universalist Church.) Is it Friday yet? Charles -Original Message- From: IBM Mainframe

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

I've worked in half a dozen shops but never encountered any onerous jobname restrictions. I suppose if you absolutely had to depend on the OUTPUT command and did not want to customize IKJEFF53, the restriction could be justified in those terms. But spool display tools like the old QUEUE

Re: Logstreams

We don't run regularly with logrec logstream, but I believe that you still need to maintain SYS1.LOGREC in order to capture IPL time records that are cut before logger gets running. If that's still true... . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler

Re: Windows 10 Pro automatic update

> On Jun 28, 2017, at 10:17 AM, Paul Gilmartin > <000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > > On Wed, 28 Jun 2017 09:11:30 -0500, Wendell Lovewell wrote: > >> Any version of Windows can have the update service disabled. >> > OTOH, beware: > >

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

On Wed, 28 Jun 2017 15:36:25 -0400, Farley, Peter x23353 wrote: >All well and good when the shop standard does not mandate TSO userid as job >name for *all* non-privileged users, no exceptions allowed. > >Some of us do not get to make the rules ourselves, or even have any input on >what the

Re: Logstreams

On Jun 28, 2017, at 2:07 PM, Bill Wilkie wrote: > > Is anyone running from logstreams instead just running logrec? Using > logstreams for other reports? How used? Problems? I switched SMF, LOGREC, and OPERLOG to logstreams a few years ago. It all went smoothly and

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

All well and good when the shop standard does not mandate TSO userid as job name for *all* non-privileged users, no exceptions allowed. Some of us do not get to make the rules ourselves, or even have any input on what the rules are. Peter -Original Message- From: IBM Mainframe

Re: Logstreams

Since I think 2001 the first company that wanted SYSPLEX savings started using LOGR LOGREC logstream, at the time it was the easiest was to exploit SYSPLEX savings. I'm using it now and offloading logstream data daily to a logrec history file, and running any EREP reports I need to just as it

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

On 2017-06-28, at 12:57, Jesse 1 Robinson wrote: > > So, where is this model job card? Never heard of it. > I believe there's one in somewhere in ISPF settings. And the SMP/E panels allow defining one. But I'm hardly an expert, because ... > ... And no, I never submit jobs with my userid in

Logstreams

Is anyone running from logstreams instead just running logrec? Using logstreams for other reports? How used? Problems? Thanks Bill -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

I love this business because I learn something every day. After wiping egg off my face. ;-) So, where is this model job card? Never heard of it. And no, I never submit jobs with my userid in the job name. Stopped doing that while a trainee decades ago. I use something meaningful for each job

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

That's kind of the way it was when I worked for Boeing, not sure they still maintain that TSO exit that builds the jobcard based on RACF profiles and custom templates. we were never allowed to supply a jobcard so that was the norm, and if the exit was removed we would see IKJ56700A 6 digit

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

On 28 June 2017 at 11:41, Jesse 1 Robinson wrote: > The message, wherever it's generated, always results from a missing JOB card. Not at all. I get this message virtually every time I submit a job. My model JOB statement has my TSO userid as the jobname, and I get the

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

The message, wherever it's generated, always results from a missing JOB card. 'Missing' means altogether absent or malformed, which is another way to say absent. The answer to the problem is in the JCL being submitted. If there is no purported JOB card, that's it. If there appears to be a JOB

Re: Ironstream over FTP

Okay, while we are discussing alternatives here: the product I am responsible for, zDefender, is also an alternative way of taking SMF and other data from your mainframe to an "analysis platform" such as Splunk, or alsdo any other "SIEM" such as HPE ArcSight, IBM QRadar, LogRhythm, etc. Again,

Re: Windows 10 Pro automatic update

On Wed, 28 Jun 2017 09:11:30 -0500, Wendell Lovewell wrote: >Any version of Windows can have the update service disabled. > OTOH, beware: https://www.usatoday.com/story/tech/news/2017/06/27/petya-ransomware-attack-windows-wannacry-protect/103241420/ Or, just avoid Windows. >1) From a DOS

Re: Windows 10 Pro automatic update

Any version of Windows can have the update service disabled. 1) From a DOS window, enter "services.msc". 2) Find the line that has "Windows Update" on it. Right-click and select "Properties". 3) Change the "Startup Type" to "Disabled". This will prevent it from starting next boot. 4) Click

Re: Ironstream over FTP

Similar to what Chris mentions below, the IBM Common Data Provider for z Systems provides a streamlined method for gathering z/OS operational data (SMF, SYSLOG, JOBLOGs, etc.) for forwarding to other products, particularly log analysis/analytics products such as ELK, Splunk or IOAz. Here is a

Re: Ironstream over FTP

Ironstream captures and forwards to a data repository in real time SYSLOG, SMF, LOG4J, JES Spooled output, RMF, SYSTEMSTATE, and user generated input using an API. As part of that capture and forward process raw data is formatted into a Splunk acceptable form and translated from EBCDIC to

Re: Ironstream over FTP

Ok does it mean we just need to feed the SMF/RMF into ironstream and then it intelligently divides into SYSOUT,SYSLOGD,USS,RMF,SMF,SPOOL etc and securely transfers to splunk ? Whereas plain FTP requires pre-reqs from our end to prepare them into each requested category ? On Jun 28, 2017 5:55 PM,

Re: Ironstream over FTP

From what I saw (there are videos on youtube), it can capture SMF records as they are created, and then transfer them to a splunk indexer. The important part is 'as they are created', so that you see the information in splunk in real time. Gadi -Original Message- From: IBM Mainframe

Re: IBM customer anchor

>Yes, I agree, we use IDENTI... I would say that that is wholly unacceptable unless you own the prefix IDE. If IBM creates a token that happens to collide then we may expect and require you to change. Is that likely? No. Is it conceivable? Yes. Some prefixes within the IBM range that had been

Re: Ironstream over FTP

Read the log ? On Jun 28, 2017 4:38 PM, "R.S." wrote: W dniu 2017-06-28 o 12:53, גדי בן אבי pisze: From what I read, Irontream is a lot more than just transferring files. > Not so lot, but it is just different animal. Ironstream purpose is to transmit logs to

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

IEFUTL only takes effect once a job is running. More likely to be the TSO submit exit IKJEFF10. Andrew -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message:

Re: Ironstream over FTP

W dniu 2017-06-28 o 12:53, גדי בן אבי pisze: From what I read, Irontream is a lot more than just transferring files. Not so lot, but it is just different animal. Ironstream purpose is to transmit logs to remote server. So it has to READ the log in real time (IMHO this is the most important

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

Thank you, Elardus. I accidentally copied a job card from a working member that was missing the word JOB after the job name. That was the problem. And you cleared up my other questions as well. Thanks again! Kind regards, Lindy -Original Message- From: IBM Mainframe Discussion List

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

Thanks, Suresh. Turned out that my "foreign" job card was missing the word JOB. :) doh. Anyway, I had a funny feeling it could be syntax related, which is why I asked this as a generic question. In some shops the job name must be the 7 character TSO user id plus one character, and if the

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

suresh chacko wrote: >Edit the job in 3.4 and the PROFILE. If PACK is ON, set it OFF with PACK OFF >command and resubmit the job and see it resolves the issue. PACK Status to do with jobname length? I must be missing something... Lindy Mayfield, Ok, I submitted a job from an edit session

Re: Ironstream over FTP

From what I read, Irontream is a lot more than just transferring files. Gadi -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jake Anderson Sent: Wednesday, June 28, 2017 1:38 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Ironstream over

Ironstream over FTP

Hi We have not bought ironstream but would like to know ironstream is different from FTP. Since using some Google search I just that it is easy to use without much of difficulty and securely sends the data. Generally I would like to know then difference. Regards Jake

Re: Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

Dear Lindy Edit the job in 3.4 and the PROFILE. If PACK is ON, set it OFF with PACK OFF command and resubmit the job and see it resolves the issue. Thanks, Suresh Chacko On Wed, Jun 28, 2017 at 10:28 AM, Lindy Mayfield wrote: > Hello. > > Can someone tell me what

Re: Check out Ransomware Cyberattack Goes Global - Bloomberg

> -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Edward Finnell > Sent: 28 June, 2017 11:00 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Check out Ransomware Cyberattack Goes Global - Bloomberg > > _Ransomware Cyberattack Goes

Check out Ransomware Cyberattack Goes Global - Bloomberg

_Ransomware Cyberattack Goes Global - Bloomberg_ (https://www.bloomberg.com/news/articles/2017-06-28/cyberattack-reaches-asia-as-new-targets-hit-by-ran somware-demand) -- For IBM-MAIN subscribe / signoff / archive access

Re: Who deleted my data set?

> Who deleted my data set? Not me. Seriously: SETR AUDIT(DATASET) in RACF will genereate SMF record for every dataset created/deleted. RACF records are pretty simple to use. -- Radoslaw Skorupka Lodz, Poland ==

Re: Who deleted my data set?

Jesse 1 Robinson wrote: >We have occasional requests from users as to who deleted a particular data >set. Or renamed? Hmmm? Or (mis)handled by HSM space management? Been there in those mess, not a pretty thing of course. >We have access to SMF data for a reasonable period. SAS however was

Re: GRS CNS system recommandations

That is more or less the reasons we moved it to the GDPS K-systems, because they will/should 'always' have sufficient capacity. I think now about also moving it to the production LPAR with the largest capacity. Anyway, it runs in the GRS address space, so it won't be hurt by higher priority

Sources of message: IKJ56700A ENTER JOBNAME CHARACTER(S) -

Hello. Can someone tell me what triggers this message/prompt? IKJ56700A ENTER JOBNAME CHARACTER(S) - One source I know of is when I try to submit something that isn't JCL. But it also happens in weird ways (on different machines) for 'normal' JCL. For example, I have a job card that looks