Re: Forced password change held to be harmful -- Was RE: RACF password history was: AW: //STARTING JOB ...

A bit OT, but this, I think, is a good idea: http://www.passwordcard.org/en Best Regards, Thomas Berg ___ Thomas Berg Specialist zOS/RQM/IT Delivery Swedbank AB (Publ) -

Re: Forced password change held to be harmful -- Was RE: RACF password history was: AW: //STARTING JOB ...

On Wed, 14 Jan 2015 11:15:32 -0500, Hobart Spitz wrote: >Under z/VM, SFS has the capability for a user to have the ability to >grant/revoke access to files and directories that are owned by the user's >id. Thus, users can grant and revoke access to/from their own SFS >resources without the bother

Re: Forced password change held to be harmful -- Was RE: RACF password history was: AW: //STARTING JOB ...

assword-sanity/exp-harmful/ > > Charles > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of nitz-...@gmx.net > Sent: Monday, December 29, 2014 6:29 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: RACF password

Re: Forced password change held to be harmful -- Was RE: RACF password history was: AW: //STARTING JOB ...

U] On Behalf Of nitz-...@gmx.net Sent: Monday, December 29, 2014 6:29 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: RACF password history was: AW: //STARTING JOB ... > Check out the SETROPTS HISTORY and MINCHANGE options if you haven't already. Thanks, Tom! I did that and set history according

Re: Forced password change held to be harmful -- Was RE: RACF password history was: AW: //STARTING JOB ...

passwords, > and > are more compelled to write them down. > > http://cryptosmith.com/password-sanity/exp-harmful/ > > Charles > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of nitz-...@gmx.net > S

Forced password change held to be harmful -- Was RE: RACF password history was: AW: //STARTING JOB ...

cryptosmith.com/password-sanity/exp-harmful/ Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of nitz-...@gmx.net Sent: Monday, December 29, 2014 6:29 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: RACF password history was: AW: //STARTING JOB .

RACF password history was: AW: //STARTING JOB ...

> Check out the SETROPTS HISTORY and MINCHANGE options if you haven't already. Thanks, Tom! I did that and set history accordingly. No need for an exit, then! I would set MINCHANGE only if I see that someone tries to change the many passwords that are now kept to get to the (n+1)th password. Ba

Re: AW: //STARTING JOB ...

ibmmain wrote: Although I am thinking about installing a RACF exit that prohibits the 'practise' of changing the password twice to get back at the old password whenever 180 days have expired and the password needs to get changed. Check out the SETROPTS HISTORY and MINCHANGE options if you haven

Re: AW: //STARTING JOB ...

> Yes, it is true. The case you describe is *not* supported. Full stop. Okay, that's good to know. That means that I have to remove the JOB card for STCs from any JCL that sits in a JES2-only proclib concatenation. I guess I don't remember the behaviour prior to started jobs all that well. > W

AW: Re: AW: //STARTING JOB ...

>> You probably mean //STARTING EXEC ... not //STARTING JOB, do you? >I am on vacation right now and cannot test. I know that two lines are >inserted, one of them is a >JOB card, the other an EXEC statement. Nothing gets "inserted". Try to think about it from another point of view: You want to

AW: //STARTING JOB ...

An: IBM-MAIN@LISTSERV.UA.EDU Betreff: AW: AW: //STARTING JOB ... Barbara, did you (or someone else) modify/activate the TSO/E submit exit (IKJEFF10), or the JES2 exits (HASPX02, HASPX20) ? TSO will try to generate a JCL card, when no valid JOB card is found. Described in TSO/E customization guide

Re: AW: //STARTING JOB ...

In , on 12/26/2014 at 09:45 AM, John McKown said: >//IEFPROC.IEFRDER (optional?) Yes; START only generates it if a device name, volume serial number or othe DD parameter is on the START command. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see

Re: AW: //STARTING JOB ...

In <20141226151929.4ae52b84c9b55d029a0d6...@gmx.net>, on 12/26/2014 at 03:19 PM, ibmmain said: >Both are input by forces outside of my control Perhaps by management fiat, but that's not IBM's doing. Put a JOB statement in an IEFJOBS member and IBM won't add another one. >> I tried to describ

Re: AW: //STARTING JOB ...

ent: Friday, December 26, 2014 10:45 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: AW: //STARTING JOB ... On Fri, Dec 26, 2014 at 8:19 AM, ibmmain wrote: > > You probably mean //STARTING EXEC ... not //STARTING JOB, do you? > I am on vacation right now and cannot test. I know that two lines are

Re: AW: //STARTING JOB ...

On Fri, Dec 26, 2014 at 8:19 AM, ibmmain wrote: > > You probably mean //STARTING EXEC ... not //STARTING JOB, do you? > I am on vacation right now and cannot test. I know that two lines are > inserted, one of them is a JOB card, the other an EXEC statement. Both are > input by forces outside of m

AW: AW: //STARTING JOB ...

Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] Im Auftrag von ibmmain Gesendet: Freitag, 26. Dezember 2014 15:19 An: IBM-MAIN@LISTSERV.UA.EDU Betreff: Re: AW: //STARTING JOB ... > You probably mean //STARTING EXEC ... not //STARTING JOB, do you? I am on vacation right now and cannot test

Re: AW: //STARTING JOB ...

> You probably mean //STARTING EXEC ... not //STARTING JOB, do you? I am on vacation right now and cannot test. I know that two lines are inserted, one of them is a JOB card, the other an EXEC statement. Both are input by forces outside of my control (since I haven't found what to tweak to make i

AW: //STARTING JOB ... was: Re: JCLLIB in started proc?

> Nice summary, Peter. Thanks > Do you happen to know who puts in //STARTING JOB ... when MEMBER is only > contained in the JES2 proclib concatenation and not in MSTJCL? You probably mean //STARTING EXEC ... not //STARTING JOB, do you? Well, again, I can only tell from what is my understandi