HP3000-L Archives

December 2005, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
David N Lukenbill <[log in to unmask]>
Reply To:
David N Lukenbill <[log in to unmask]>
Date:
Tue, 6 Dec 2005 12:26:15 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (289 lines)
Reid,

Yup, that's pretty strong evidence!  On my system, LOCATTR=$00040000, and
is being preserved.  I'm wondering if there's a bug in BULDACCT or the
OS.....

In your BULDACCT job:
      :calc 268435455
      268435455, $FFFFFFF, %1777777777       <--- Seven "F"s.

What's being set:
      :calc -1
      -1, $FFFFFFFF, %37777777777     <--- Eight "F"s.

The difference may be that I'm setting LOCATTR on users, not accounts.


David N. Lukenbill
Computer Sciences Corporation



|---------+---------------------------->
|         |           Reid Baxter      |
|         |           <reid.e.baxter   |
|         |           @jpmchase.com>   |
|         |           Sent by: HP-3000 |
|         |           Systems          |
|         |           Discussion       |
|         |           <[log in to unmask]
|         |           TC.EDU>          |
|         |                            |
|         |                            |
|         |           2005/12/06 12:06 |
|         |           PM               |
|         |           Please respond to|
|         |           reid.e.baxter    |
|---------+---------------------------->
  >------------------------------------------------------------------------------------------------------------------------------|
  |                                                                                                                              |
  |       To:       [log in to unmask]                                                                                       |
  |       cc:                                                                                                                    |
  |       Subject:  Re: [HP3000-L] MPE local attribute on userid                                                                 |
  >------------------------------------------------------------------------------------------------------------------------------|




David,

Here is the evidence that STRONGLY suggests that buldacct does not adhere
to the correct locattrr. (We are running the same version).

:buldacct ableprod

BUILD ACCOUNT PROGRAM FOR DIRECTORY MIGRATION. Version A.50.26

*** HIERARCHICAL DIRECTORIES WILL be processed. ***
*** ROOT HIERARCHICAL DIRECTORIES WILL NOT be processed. ***
Groups with PRIV VOL=YES will have HOMEVS= and ONVS= options.
**ABLEPROD ONVS=APPLDB_VS
ACCOUNT ABLEPROD ADDED TO FILE

Please check that the manager.sys passwords on the job card of
Buldjob1 and Buldjob2 are consistent with the target system

build account JOB "BULDJOB1" built..
Setcatalog JOB "BULDJOB2" built..
:editor
HP32201A.09.00 EDIT/3000 TUE, DEC  6, 2005, 11:00 AM
(C) HEWLETT-PACKARD CO. 1993
/t buldjob1,unn
l 1/20
    1     !JOB BULDJOB1,manager/.sys/,pub;hipri;OUTCLASS=,2
    2     !  comment BULDJOB1 created TUE, DEC  6, 2005, 11:00 AM
    3     !  continue
    4     !  setvar hpautocont true
    5     !  continue
    6     !  SETVAR BULDJOB 0
    7     !  SETVAR BULDACCTS 0
    8     !  SETVAR GROUPERR 0
    9     !  SETVAR BULDDIRS 0
   10     !  SETVAR DIRERROR 0
   11     !  SETVAR BULDACDS 0
   12     !  SETVAR ACDERROR 0
   13     !  setvar account 0
   14     !  continue
   15     !  NEWACCT  ABLEPROD,mgr;&
   16     !  PASS=;&
   17     !  LOCATTR=268435455;&
   18     !  FILES=;CPU=;CONNECT=;&
   19     !  MAXPRI=CS;&
   20     !  CAP= &
/:listacct ableprod
********************
ACCOUNT: ABLEPROD

DISC SPACE: 521728(SECTORS)     PASSWORD: **
CPU TIME  : 79609(SECONDS)      LOC ATTR: $FFFFFFFF
CONNECT TIME: 290050(MINUTES)   SECURITY--READ    : AC
DISC LIMIT: UNLIMITED                     WRITE   : AC
CPU LIMIT : UNLIMITED                     APPEND  : AC
CONNECT LIMIT: UNLIMITED                  LOCK    : AC
MAX PRI  : 150                            EXECUTE : ANY
GRP UFID : $05690001 $42C90211 $0077B8D2 $92822869 $0A67EAB4
USER UFID: $00000000 $00000000 $00000000 $00000000 $00000000
CAP: AM,AL,GL,DI,CV,UV,LG,NA,NM,ND,SF,BA,IA,MR,DS,PH
/e



END OF SUBSYSTEM
:
:calc 1*-1
-1, $FFFFFFFF, %37777777777
:
Regards,

Reid E. Baxter




                      David N Lukenbill

                      <[log in to unmask]        To:
[log in to unmask]

                      >                        cc:

                      Sent by: HP-3000         Subject:  Re: [HP3000-L] MPE
local attribute on userid
                      Systems

                      Discussion

                      <[log in to unmask]

                      tc.edu>



                      12/06/2005 11:35

                      AM

                      Please respond to

                      David N Lukenbill






Reid,

Could you double check that BULDACCT doesn't honor the LOCATTRs?  It seems
to be honoring it on my system, but I may have a different version.  (I'm
on BULDACCT A.50.26)  I run BULDACCT on my production account, then alter
the account name to be my development/test account.  I then purge the users
in the development account, and stream BULDJOB1 to re-create the current
production users in the development/test account.  When I check the local
attributes in the development/test account, they're set.

David N. Lukenbill
Computer Sciences Corporation




|---------+---------------------------->
|         |           Reid Baxter      |
|         |           <reid.e.baxter   |
|         |           @jpmchase.com>   |
|         |           Sent by: HP-3000 |
|         |           Systems          |
|         |           Discussion       |
|         |           <[log in to unmask]
|         |           TC.EDU>          |
|         |                            |
|         |                            |
|         |           2005/12/06 10:57 |
|         |           AM               |
|         |           Please respond to|
|         |           reid.e.baxter    |
|---------+---------------------------->

>------------------------------------------------------------------------------------------------------------------------------|


  |
|
  |       To:       [log in to unmask]
|
  |       cc:
|
  |       Subject:  Re: [HP3000-L] MPE local attribute on userid
|

>------------------------------------------------------------------------------------------------------------------------------|






Ray,

I don't know if you are experiencing the same thing we have, but we to have
an application which is constructed such that if the loc attr is not set
correctly on the DR server/app, one cannot successfully run the
application. We found that in running buldacct on a nightly basis on our
production box and transferring buldjob1 and buldjob2 over to the DR server
to insure that all users created on the production server are replicated on
the DR server, that buldacct does not 'honor' the loc attr from the
production server. Thus, every time we stream the buldjobs on the DR we
must insure that a altacct xxx;locattr=-1 and altuser mgr.xxx;locsttr=-1
are set AFTER the buljob1 runs. (The local attribute for the application is
"-1").

Could this be your dilemma ?

Regards,

Reid E. Baxter




                      Raymond Familar

                      <far_north_flip@Y        To:
[log in to unmask]

                      AHOO.COM>                cc:

                      Sent by: HP-3000         Subject:  [HP3000-L] MPE
local attribute on userid
                      Systems

                      Discussion

                      <[log in to unmask]

                      tc.edu>



                      12/06/2005 10:13

                      AM

                      Please respond to

                      Raymond Familar






Hello.
I recently performed a failover test for an applicaiton that tracks some
userid information.  The local attribute (LOC ATTR) is tracked, so when a
user logs in on the DR system, if their LOC ATTR does not match, then they
cannot log in.  I do not recall this being much of an issue in past DR
tests, so I assume they matched during the last test (6-12 months ago).
Under what circumstances would a userid LOC ATTR be changed.  We use Vesoft
Sec/3000 in our environment.

Thanks.
Ray

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2