Re: 6.1 and 7.1

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Yes...

Build we have 100+ field boxes that are setup basically identically.  We
have to know how to build new boxes for a new location.

I don't believe we have build policies for our one of kind corporate boxes.

Charles



On Fri, Jun 21, 2013 at 8:01 AM, Paul Nelson <nelsonp@xxxxxxxxxxxxx> wrote:

> Funny you should mention a big three accounting firm. This is an actual
> request from one of the youngsters doing the audit at a client of mine:
>
> "We are in the process of performing our infrastructure reviews as part of
> our audit procedures and are trying to determine the best approach to take.
>
> If possible, we would like to be able to test one AS400 server, instead of
> testing one AS400 server for every application.  This said, is there a
> build
> policy that dictates how AS400 servers are set up/configured?  This would
> help us gain comfort that all AS400 servers are built the same."
>
> Anybody ever been asked for a "build policy"?
>
> Paul Nelson
> Cell 708-670-6978
> Office 512-392-2577
> nelsonp@xxxxxxxxxxxxx
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
> Sent: Friday, June 21, 2013 6:45 AM
> To: Midrange Systems Technical Discussion
> Subject: Re: 6.1 and 7.1
>
> John,
>
> Where did you read
> <snip>
> "1)  We have a pc running CA over hospital network as console.  I read
> that the connection would have to be revalidated.  I am unclear as to
> what that means."
> </snip>
> Context really matters.  If you read it in the IBM i Access for Windows
> Administrators Guide that will have a whole different meaning than if you
> read it in "System 34 audit instructions upgraded to AS/400 by my big
> three accounting firm" or the HIPAA Guide for IT Administrators.
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to:  2505 Dekko Drive
>           Garrett, IN 46738
> Ship to:  Dock 108
>           6928N 400E
>           Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> From:   "TheBorg" <sjl_abc@xxxxxxxxxxx>
> To:     midrange-l@xxxxxxxxxxxx,
> Date:   06/21/2013 01:24 AM
> Subject:        Re: 6.1 and 7.1
> Sent by:        midrange-l-bounces@xxxxxxxxxxxx
>
>
>
> "Validation" means that the regulating or certifying authority (perhaps
> the
> FDA) requires that you have a test script which "validates" hardware and
> software systems, and that it has passed the validation test.  If you
> don't
> have a test script, one will need to be created, old test scripts may need
>
> to be revised for additional testing, depending on what changed on the IBM
> i
> side.
>
> More importantly than your console, however, your hospital applications
> could require revalidation if any significant changes occur because of an
> IBM i version upgrade.
>
> For example, if you had to install a newer/different version of an
> application you would probably required to revalidate that application,
> and
> if any of its interfaces to other applications were modified those
> applications would need validation as well.
>
> -sjl
>
>
> "John McKee"  wrote in message
> news:mailman.1179.1371786364.9013.midrange-l@xxxxxxxxxxxx...
>
> My boss initially felt one vendor would not work at 7.1, since 6.1 was
> all that he saw on their website.  He is following up on this.  From
> what I have read in the 7.1 and 6.1 MTUs, I don't see issues.
>
> Maybe ill-informed questions, but I am unsure how to research this:
>
>
> 1)  We have a pc running CA over hospital network as console.  I read
> that the connection would have to be revalidated.  I am unclear as to
> what that means.
>
> 2) Image catalog appears to be only created on the LS.  Thus LS has to
> have sufficient space for all DVD images.  I thought that was
> interesting.
>
>
> John McKee
>
> On Thu, Jun 20, 2013 at 10:05 PM, Pete Massiello - ML
> <pmassiello-ml@xxxxxxxxxxxx> wrote:
> > How about versions of domino unsupported, AnyNet supported at 6.1 but
> not
> > at 7.1, Different versions of Java supported for 6.1 & 7.1 with removal
> of
> > option 10 at 7.1, Websphere 6.0 not supported at 7.1, but supported at
> > 6.1.  Operations Direct Console supported at 6.1 & not at 7.1, should I
> > continue?
> >
> > Depending on which hardware you have, if it is old it could support 6.1,
>
> > but not 7.1.
> >
> > I would highly recommend going to 7.1 in every upgrade, but there are
> > reasons to upgrade just to 6.1 if any of the above will cause you an
> > issue. This is why we have Memo to Users and the Upgrade roadmap.  There
>
> > is more of a difference between 6.1 & 7.1 than just the DVD labels.
> >
> >         Pete
> >
> > --
> > Pete Massiello
> > iTech Solutions
> > http://www.itechsol.com
> > http://www.iInTheCloud.com
> >
> >
> >
> >
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John McKee
> > Sent: Thursday, June 20, 2013 3:06 PM
> > To: Midrange Systems Technical Discussion
> > Subject: 6.1 and 7.1
> >
> > Object conversion at 6.1.  What could possibly be a hurdle at 7.1?  I
> > didn't want to hijack the thread where an upgrade from a v level is
> being
> > discussed.
> >
> > John McKee
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
> > unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
> > moment to review the archives at http://archive.midrange.com/midrange-l.
> >
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.