× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. April 2008

RE: Upgrade from v5r2 to v5r4m5 (was RE: Encrypted Data to File)

Pete,
When upgrading from v5r3 to v5r4 you can still increase size from GO
LICPGM OPTION 5, correct?

Larry

Larry Ketzes | Senior iSeries System Administrator | AIG / ALICO - American
Life Insurance Company
One ALICO Plaza, 600 N. King Street, AMIS | Wilmington, DE 19801 | *:
302.594.2146 | 7: 302.830.4524| *: larry.ketzes@xxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Massiello
Sent: Friday, April 25, 2008 1:54 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Upgrade from v5r2 to v5r4m5 (was RE: Encrypted Data to File)

The i5/OS level of V5R4M5 is V5R4, so there is no problem going from V5R2 to
V5R4M5 of SLIC (5722-999). In fact, I would recommend going to V5R4M5, this
way if you decide to go to a Power6 box, you are set.

When upgrading from V5R4 from v5R2, don't forget that when you increase the
size of the Lic area, you MUST use the API to increase it, vs. going using
Increase License storage space under GO LICPGM option 5.

Pete Massiello

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Wilt, Charles
Sent: Friday, April 25, 2008 1:42 PM
To: Midrange Systems Technical Discussion
Subject: Upgrade from v5r2 to v5r4m5 (was RE: Encrypted Data to File)

Rob,

Do you by chance know if you can upgrade from v5r2 to v5r4m5?

Or can you only go as far as v5r4m0?

Charles Wilt
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307

wiltc@xxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, April 25, 2008 11:26 AM
To: Midrange Systems Technical Discussion
Subject: Re: Encrypted Data to File

No. -Providing- you pass any questions in the V5R4 MTU and the V6R1 MTU
on hardware, I'd upgrade the 550 from V5R3 straight to V6R1 and bypass the
V5R4M5 stuff.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Michael Ryan" <michaelrtr@xxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
04/25/2008 11:19 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Subject
Re: Encrypted Data to File






Since we're getting new hardware, I'd still need to do the V5R3 to
V5R4M5 upgrade on the 550, then the V5R4M6 to V6R1 upgrade on the new
Power6 box, right?

On Fri, Apr 25, 2008 at 11:13 AM, <rob@xxxxxxxxx> wrote:
550 supports V6R1

https://www-304.ibm.com/systems/support/i/planning/upgrade/osmapping.html


Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Michael Ryan" <michaelrtr@xxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
04/25/2008 09:33 AM


Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Subject
Re: Encrypted Data to File






Hi Rob -

Thanks for the heads up. Our BP is talking with the Ops manager right
now. I'm pretty sure they're talking about new hardware. So I'll need
to upgrade from V5R3 to V5R4M5 on the existing 550, and then upgrade
to the (I assume) whatever Power6 box running V6R1?

- Michael

On Fri, Apr 25, 2008 at 9:26 AM, <rob@xxxxxxxxx> wrote:
> Michael,
>
> If your existing hardware supports V6R1 then, by all means, upgrade
to
> that first. If not, then the new hardware will require that you be
at
> V5R4M5 (you did see the M5, right?) before going to it by any
supported
> route.
>
> Our existing hardware did not support V6 (270). And we want to do
some
> stuff like guested lpar on the new box so we upgraded to V5R4M5 on
the
> 270, restored it on to the new box, and will upgrade it to V6R1
today,
> then save it all off and init the new machine so that we can restore
this
> V6R1 lpar as guested.
>
> Rob Berendt
> --
> Group Dekko Services, LLC
> Dept 01.073
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
>
> "Michael Ryan" <michaelrtr@xxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 04/25/2008 07:26 AM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
> To
> "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> cc
>
>
>
> Subject
> Re: Encrypted Data to File
>
>
>
>
>
>
> Thanks Carsten! The plan here is to upgrade to V5R4, but there's
also
> a pending new hardware acquisition, and perhaps an upgrade to V6R1
> instead. I appreciate the information.
>
> - Michael
>
> On Fri, Apr 25, 2008 at 7:14 AM, Flensburg, Carsten
> <Flensburg@xxxxxxxxxx> wrote:
> >
> > The recent series of cryptographic APIs by Example articles are
based
> on
> > the key managament APIs introduced with release V5R4. Some time
ago
I
> > wrote another series of articles covering this topic and
providing
the
> > same functionality, that were based on the APIs available in
release
> > V5R3. You'll find links to these earlier articles at the end of
the
> > article published yesterday, but I've also included them here:
> >
> > APIs by Example: Cryptographic Services APIs, Part 1:
> >
>

http://systeminetwork.com/article/apis-example-cryptographic-services-ap
> > is
> > APIs by Example: Cryptographic Services APIs, Part 2:
> >
>

http://systeminetwork.com/article/apis-example-cryptographic-services-ap
> > is-part-2
> > APIs by Example: Cryptographic Services APIs, Part 3:
> >
>

http://systeminetwork.com/article/apis-example-cryptographic-services-ap
> > is-part-3
> > APIs by Example: Cryptographic Services APIs, Part 4:
> >
>

http://systeminetwork.com/article/apis-example-cryptographic-services-ap
> > is-part-4
> > APIs by Example: Cryptographic Services APIs, Part 5:
> >
>

http://systeminetwork.com/article/apis-example-cryptographic-services-ap
> > is-part-5
> > APIs by Example: Cryptographic Services APIs, Part 6:
> >
>

http://systeminetwork.com/article/apis-example-cryptographic-services-ap
> > is-part-6
> > APIs by Example: Cryptographic Services APIs, Part 7:
> >
>

http://systeminetwork.com/article/apis-example-cryptographic-services-ap
> > is-part-7
> >
> > Happy reading!
> >
> >
> > Best regards,
> > Carsten
> >
> >
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael
Ryan
> >
> > Sent: 25. april 2008 12:44
> > To: Midrange Systems Technical Discussion
> > Subject: Re: Encrypted Data to File
> >
> >
> > Very nice...looks I have some more reading in store! :)
> >
> > Question: What can be used in V5R3? Some of the key management
> utilities
> > are only available in V5R4 and higher, correct?
> >
> > Thanks...
> >
> > On Thu, Apr 24, 2008 at 4:25 PM, Flensburg, Carsten
> > <Flensburg@xxxxxxxxxx> wrote:
> > >
> > > Your assumption is correct, Michael. - Here's some more
information
> > > on the subject that might help explain the use of a salt in
this
> > > specific
> > > context: http://en.wikipedia.org/wiki/Initialization_vector
> > >
> > > As coincidence would have it, this week's programming
newsletter
> also
> >
> > > includes an article covering this topic, together with more
code
> > > examples:
> > >
> > >
>
http://systeminetwork.com/article/apis-example-cryptographic-key-manag
> > > em ent-encrypting-and-decrypting-data-using-key-hierarchy
> >
> >
> > >
> > > The article doesn't appear to be on-line yet, but it should be
soon.
> > > A
> > > (free) associate membership to the System iNetwork is required
to
> > > access the article.
> > >
> > >
> > > Best regards,
> > > Carsten
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: midrange-l-bounces@xxxxxxxxxxxx
> > > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael
Ryan
> > >
> > > Sent: 24. april 2008 18:37
> > > To: Midrange Systems Technical Discussion
> > > Subject: Re: Encrypted Data to File
> > >
> > >
> > >
> > > Good refs Buck...thanks.
> > >
> > > How would this be implemented in the cryptographic APIs? Would
this
> > > be used for the Initialization Vector?
> > >
> > > On Thu, Apr 24, 2008 at 12:21 PM, Buck <kc2hiz@xxxxxxxxx>
wrote:
> > > > Julius wrote:
> > > > > Carsten, could you please explain what "salt value" is.
> > > >
> > > > http://en.wikipedia.org/wiki/Salt_(cryptography)
> > > >
> > > > I've found Bruce Schneier approachable:
http://www.schneier.com/
> >
> > > > -- > > > 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.
> >
> >
> --
> 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.


--
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 e-mail transmission contains information that is intended to be
confidential and privileged. If you receive this e-mail and you are not a
named addressee you are hereby notified that you are not authorized to read,
print, retain, copy or disseminate this communication without the consent of
the sender and that doing so is prohibited and may be unlawful. Please
reply to the message immediately by informing the sender that the message
was misdirected. After replying, please delete and otherwise erase it and
any attachments from your computer system. Your assistance in correcting
this error is appreciated.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.