Re: SEQUENCE# ERRORS IN DIRECTORY
I don't think DIRECTXA is complaining about the sequence numbers one could code beyond col 72. I merely think it is that the AUTOLOG, ACCOUNT, MACHINE and OPTION records follows a device record. For a given user, firts code the non-device statements (like ACCOUNT), then devices (line CONSOLE, SPOOL, LINK, MDISK) 2010/11/11 George Henke/NYLIC george_he...@newyorklife.com How do you get rid of, or renumber, sequence numbers in the DIRECTORY outside of DIRMAINT. I get sequence# errors when I move things around and do DIRECTXA with the (EDIT option. directxa vmuvm direct a (edit z/VM USER DIRECTORY CREATION PROGRAM - VERSION 5 RELEASE 4.0 AUTOLOG AUTOLOG1 OP1 MAINT USE10750 HCPDIR752E STATEMENT SEQUENCE ERROR FOLLOWING USER OPERATOR ACCOUNT 2 OPERATOR USE10760 HCPDIR752E STATEMENT SEQUENCE ERROR FOLLOWING USER OPERATOR MACH ESA USE10770 HCPDIR752E STATEMENT SEQUENCE ERROR FOLLOWING USER OPERATOR OPTION MAINTCCW USE10780 HCPDIR752E STATEMENT SEQUENCE ERROR FOLLOWING USER OPERATOR EOJ DIRECTORY NOT UPDATED -- Kris Buelens, IBM Belgium, VM customer support
Re: SEQUENCE# ERRORS IN DIRECTORY
Right, ty, Kris. I had replaced, inplace, the contents of the PROFILE IBMDFLT to add PARM AUTOCR to I CMS and it did not like the order. Everything is good now. Love that (EDIT option when updating the DIRECTORY outside DIRMAINT. directxa vmuvm direct a (edit z/VM USER DIRECTORY CREATION PROGRAM - VERSION 5 RELEASE 4.0 EOJ DIRECTORY NOT UPDATED Kris Buelens kris.buel...@gmail.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 11/11/2010 02:34 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SEQUENCE# ERRORS IN DIRECTORY I don't think DIRECTXA is complaining about the sequence numbers one could code beyond col 72. I merely think it is that the AUTOLOG, ACCOUNT, MACHINE and OPTION records follows a device record. For a given user, firts code the non-device statements (like ACCOUNT), then devices (line CONSOLE, SPOOL, LINK, MDISK) 2010/11/11 George Henke/NYLIC george_he...@newyorklife.com How do you get rid of, or renumber, sequence numbers in the DIRECTORY outside of DIRMAINT. I get sequence# errors when I move things around and do DIRECTXA with the (EDIT option. directxa vmuvm direct a (edit z/VM USER DIRECTORY CREATION PROGRAM - VERSION 5 RELEASE 4.0 AUTOLOG AUTOLOG1 OP1 MAINT USE10750 HCPDIR752E STATEMENT SEQUENCE ERROR FOLLOWING USER OPERATOR ACCOUNT 2 OPERATOR USE10760 HCPDIR752E STATEMENT SEQUENCE ERROR FOLLOWING USER OPERATOR MACH ESA USE10770 HCPDIR752E STATEMENT SEQUENCE ERROR FOLLOWING USER OPERATOR OPTION MAINTCCW USE10780 HCPDIR752E STATEMENT SEQUENCE ERROR FOLLOWING USER OPERATOR EOJ DIRECTORY NOT UPDATED -- Kris Buelens, IBM Belgium, VM customer support
Re: SEQUENCE# ERRORS IN DIRECTORY
Hi, George. DIRECTXA isn't complaining about sequence *numbers* being out of order in the VMUVM DIRECT file, it's complaining that some of the directory control statements for userid OPERATOR are not in the proper order. For example, the LINK statement must follow any general statements specified in a user's directory entry. The CP Planning and Admin Guide documents the order in which directory control statements can appear in a user's directory entry. Have a good one. DJ On 11/11/2010 01:22 PM, George Henke/NYLIC wrote: How do you get rid of, or renumber, sequence numbers in the DIRECTORY outside of DIRMAINT. I get sequence# errors when I move things around and do DIRECTXA with the (EDIT option. directxa vmuvm direct a (edit z/VM USER DIRECTORY CREATION PROGRAM - VERSION 5 RELEASE 4.0 AUTOLOG AUTOLOG1 OP1 MAINT USE10750 HCPDIR752E STATEMENT SEQUENCE ERROR FOLLOWING USER OPERATOR ACCOUNT 2 OPERATOR USE10760 HCPDIR752E STATEMENT SEQUENCE ERROR FOLLOWING USER OPERATOR MACH ESA USE10770 HCPDIR752E STATEMENT SEQUENCE ERROR FOLLOWING USER OPERATOR OPTION MAINTCCW USE10780 HCPDIR752E STATEMENT SEQUENCE ERROR FOLLOWING USER OPERATOR EOJ DIRECTORY NOT UPDATED -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544
Re: SEQUENCE# ERRORS IN DIRECTORY
Yes, ty, Dave: I had updated, in place, the PROFILE contents of IBMDFLT to add the AUTOCR parm you recommended for the automated IPL and while DIRECTXA does not mind PROFILE up ahead of certain statements, it certainly did have problem with its contents being there. Too many DIRECTXA's without a helmet. Must not think like a computer, cause they don't think either. Dave Jones d...@vsoft-software.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 11/11/2010 02:43 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SEQUENCE# ERRORS IN DIRECTORY Hi, George. DIRECTXA isn't complaining about sequence *numbers* being out of order in the VMUVM DIRECT file, it's complaining that some of the directory control statements for userid OPERATOR are not in the proper order. For example, the LINK statement must follow any general statements specified in a user's directory entry. The CP Planning and Admin Guide documents the order in which directory control statements can appear in a user's directory entry. Have a good one. DJ On 11/11/2010 01:22 PM, George Henke/NYLIC wrote: How do you get rid of, or renumber, sequence numbers in the DIRECTORY outside of DIRMAINT. I get sequence# errors when I move things around and do DIRECTXA with the (EDIT option. directxa vmuvm direct a (edit z/VM USER DIRECTORY CREATION PROGRAM - VERSION 5 RELEASE 4.0 AUTOLOG AUTOLOG1 OP1 MAINT USE10750 HCPDIR752E STATEMENT SEQUENCE ERROR FOLLOWING USER OPERATOR ACCOUNT 2 OPERATOR USE10760 HCPDIR752E STATEMENT SEQUENCE ERROR FOLLOWING USER OPERATOR MACH ESA USE10770 HCPDIR752E STATEMENT SEQUENCE ERROR FOLLOWING USER OPERATOR OPTION MAINTCCW USE10780 HCPDIR752E STATEMENT SEQUENCE ERROR FOLLOWING USER OPERATOR EOJ DIRECTORY NOT UPDATED -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544