Quantcast
Channel: Linux on the mainframe
Viewing all articles
Browse latest Browse all 18

DIRMAINT: Password syntax check

$
0
0

If you're testing the new z/VM using DIRMAINT in a second level installation for example, it could be painful if the "password syntax check" is demanding an appropriate password. For a productive environment that's necessary and recommended, but only for testing not. So how could you switch off this password syntax check? I defined the following user with a simple password.

USER LINSC132 LINSC132 256M 1G G
** 10.199.10.132 S11SP2 **
INCLUDE LNXDFLT
LOADDEV PORTNAME 500507630703C79E
LOADDEV BOOTPROG 0
LOADDEV BR_LBA 0000000000000000
LOADDEV LUN 4014400200000000
MACHINE ESA
OPTION LNKNOPAS APPLMON
DEDICATE 5007 5007

If I'm trying to create this user, DIRMAINT is complaining and reject the request because of the too trivial password. The return code is 3225.

dirm add linsc132

PUN FILE 0132 SENT TO DIRMAINT RDR AS 0105 RECS 0018 CPY 001 0 NOHOLD NOKEEP
Your ADD request has been sent for processing to DIRMAINT at
POKDEV62.
Ready; T=0.02/0.02 14:04:28
DVHREQ2288I Your ADD request for LINSC132 at * has been accepted.
DVHPXV2924E The proposed password is considered to be "trivial"; it
DVHPXV2924E either appears in published examples, is the same as the
DVHPXV2924E user ID or node ID or system affinity, or is the same as the
DVHPXV2924E current password.
DVHADD3225E The new password was rejected by exit
DVHADD3225E PASSWORD_SYNTAX_CHECKING_EXIT.
DVHREQ2289E Your ADD request for LINSC132 at * has failed; with RC =
DVHREQ2289E 3225.

To avoid this message, logon to DIRMAINT. The following message appears:

LOGON DIRMAINT
z/VM Version 6 Release 2.0, Service Level 1202 (64-bit),
built on IBM Virtualization Technology
There is no logmsg data
FILES: NO RDR, 0008 PRT, NO PUN
RECONNECTED AT 14:06:08 UTC TUESDAY 03/26/13

Wakeup caused by console attention on 13/03/26 at 14:06:09.
Manual re-start is required for DIRMAINT. Enter
"DVHBEGIN" or "DVHWAIT" when ready to re-start.
DIRMAINT POKDEV62 - 2013/03/26; T=0.01/0.01 14:06:09

As next modify the file 'CONFIG DATADVH' on disk D and search the expression PASSWORD_SYNTAX_CHECKING_EXIT=.  You'll find the row PASSWORD_SYNTAX_CHECKING_EXIT= DVHPXV EXEC (Required.). Just type a slash in front of the row and a comment replacing "Required" at the end. That's easier to find your modified row next time. 

==> x config datadvh d

CONFIG DATADVH D2 V 80 Trunc=80 Size=1563 Line=0 Col=1 Alt=0
====> /PASSWORD_SYNTAX_CHECKING_EXIT=

|...+....1....+....2....+....3....+....4....+....5....+....6....+....7..
00000 * * * Top of File * * *
00001 /*---------------------------------------------------------------------*

01444 PASSWORD_RANDOM_GENERATOR_EXIT= DVHPXR EXEC (Required.)
01445 / PASSWORD_SYNTAX_CHECKING_EXIT= DVHPXV EXEC (REM DSWT)
01446 / POSIX_CHANGE_NOTIFICATION_EXIT= DVHXPESM EXEC
01447 / PW_NOTICE_PRT_EXIT= DVHXPP EXEC
01448 / REQUEST_AFTER_PROCESSING_EXIT= DVHXRA EXEC

Save the file with ==> file and shutdown DIRMAINT with ==> log.

Again logon  to DIRMAINT, type "dvhbegin". If you could see the message "Waiting for work on..." then you could disconnect DIRMAINT with ==> cp disc.

dvhbegin
DIRMAINT POKDEV62 - 2013/03/26; T=0.08/0.09 14:07:30
Waiting for work on 13/03/26 at 14:07:30.

cp disc
DISCONNECT AT 14:07:52 UTC TUESDAY 03/26/13

Press enter or clear key to continue

Go back to the MAINT and try to create the user again. This time there is a confirmation that our new user is in the directory and placed online. 

dirm add linsc132
PUN FILE 0136 SENT TO DIRMAINT RDR AS 0121 RECS 0018 CPY 001 0 NOHOLD NOKEEP
DVHXMT1191I Your ADD request has been sent for processing to DIRMAINT at
DVHXMT1191I POKDEV62.
Ready; T=0.01/0.02 14:16:40
DVHREQ2288I Your ADD request for LINSC132 at * has been accepted.
DVHBIU3450I The source for directory entry LINSC132 has been updated.
DVHBIU3424I The next ONLINE will take place immediately.
DVHDRC3451I The next ONLINE will take place via delta object directory.

To check the user directory you could get user's entry to the readerlist first and then "receive" it to your MAINT's A disk. A "two-stepper".

dirm for linsc132 get nolock
DVHXMT1191I Your GET request has been sent for processing to DIRMAINT at
DVHXMT1191I POKDEV62.
Ready; T=0.01/0.01 14:17:58

rl
MAINT RDRLIST A0 V 164 Trunc=164 Size=5 Line=1 Col=1 Alt=0

Cmd Filename Filetype Class User at Node Hold Records Date Time
DIRMAINT NEWMAIL PUN A MAINT POKDEV62 NONE 143 3/25 11:30:04
LINUX153 DIRECT PUN A DIRMAINT POKDEV62 NONE 13 3/25 12:13:41
(none) (none) CON T MAINT POKDEV62 NONE 223 3/26 7:39:53
(none) (none) CON T MAINT POKDEV62 NONE 532 3/26 12:30:18
LINSC132 DIRECT PUN A DIRMAINT POKDEV62 NONE 15 3/26 14:18:26

The last entry within the readerlist is the new created user. To copy it to MAINT's A disk, type in the command "receive / (repl" directly to the appropriate line. The replace option (repl is necessary because there is our first entry which we want to replace with the current one from the user directory. 

MAINT RDRLIST A0 V 164 Trunc=164 Size=5 Line=1 Col=1 Alt=0
Cmd Filename Filetype Class User at Node Hold Records Date Time
DIRMAINT NEWMAIL PUN A MAINT POKDEV62 NONE 143 3/25 11:30:04
LINUX153 DIRECT PUN A DIRMAINT POKDEV62 NONE 13 3/25 12:13:41
(none) (none) CON T MAINT POKDEV62 NONE 223 3/26 7:39:53
(none) (none) CON T MAINT POKDEV62 NONE 532 3/26 12:30:18
receive / (replDIRECT PUN A DIRMAINT POKDEV62 NONE 15 3/26 14:18:26

 Exit the readerlist pressing the function key F3. Compare the two entries. The last line has been changed in this example.

LINSC132 DIRECT A0 F 80 Trunc=72 Size=11 Line=0 Col=1 Alt=0
====>

|...+....1....+....2....+....3....+....4....+....5....+....6....+....7.>
* * * Top of File * * *
USER LINSC132 LINSC132 256M 1G G
** 10.199.10.132 S11SP2 **
INCLUDE LNXDFLT
LOADDEV PORTNAME 500507630703C79E
LOADDEV BOOTPROG 0
LOADDEV BR_LBA 0000000000000000
LOADDEV LUN 4014400200000000
MACHINE ESA
OPTION LNKNOPAS APPLMON
DEDICATE 5007 5007
*DVHOPT LNK0 LOG1 RCM1 SMS0 NPW1 LNGAMENG PWC20130326 CRC""
* * * End of File * * *

The post DIRMAINT: Password syntax check appeared first on Linux on the mainframe.


Viewing all articles
Browse latest Browse all 18

Trending Articles