How to see the License key for the AS/400 and Moving aplication from one to another

[helpme]

Hi all,

Our application is running in an old AS/400 system(V4r4). And now we have a proposeal to move the complete application from the current system to a new verion (v5r4 or v6r1).

Can anybody worked on this kind of project prevoisly?

and what is the command to see the License
key for AS/400. For the IPL(Initial Program Load) wer need the License key..

Please help...........



Helpme...

[Pete]

Re: How to see the License key for the AS/400 and Moving aplication from one to anot

DSPLICKEY or WRKLICINF should show you your key information.
As for moving an app from V4R4 up, you probably can run it ok on V5R4, but V6R1 will require you to run your software through a conversion tool. There is a Redbook on the IBM site that lets you know what you need to do for conversion, and there is a ptf that loads the ANZOBJCVN command on your system to analyze things for you. That tool however is only for V5R3 and V5R4 systems. Good luck to you, that is a pretty big jump.

Pete

[Chipper]

Re: How to see the License key for the AS/400 and Moving aplication from one to anot

The other issue, if I'm not mistaken is that you can only "jump" two releases at a time. So... the releases are:
V4R4, V4R5, V5R1, V5R2, V5R3, V5R4, V6R1

1) V4R4 to V5R1
2) V5R1 to V5R3
3) V5R3 to V6R1

The other issues is that V4R4 has not been supported for some time now -- not sure how that comes into play.

[Pete]

Re: How to see the License key for the AS/400 and Moving aplication from one to anot

Hi Chipper-
I believe you are right about the OS jumps. However, I don't think that hardware currently running V4R4 could support V6R1. I don't have a System Builder handy, but the 270 series I thought was the oldest hardware that could run V6R1 depending on whether there are SPD requirements.
I read the question as the application is going to be physically moved from an old machine running V4R4 to a new machine running either V5R4 or V6R1. Perhaps the OP can clarify?

Pete

[helpme]

Re: How to see the License key for the AS/400 and Moving aplication from one to anot

Thanks Pete & Chipper,

As IBM is currently not supporting V4r4 Version of iSeries , we are planning to move the entire application running in V4R4 machine to v5r4 or v6r1 physically.


And is there any short method to move the complete library and objects from one machine to another?
I know the SAVOBJ,SABELIB,RSTLIB,RSTOBJ commands
is there any other command that we can use for this?

[tomholden]

Re: How to see the License key for the AS/400 and Moving aplication from one to anot

GO SAVE option 21. it saves everything security, licensed program, etc. then on the new system GO RESTORE option 21 to restore everything from the save.

[Pete]

Re: How to see the License key for the AS/400 and Moving aplication from one to anot

You might have to call in the calvary on this one. If you are writing the savf to media, can the device you write out to on the V4R4 box be attached to the V5R4 box? Also, V6R1 will require observability for the object conversion. If you can put both boxes on a network, you should be able to physically PUT or GET the libraries and/or objects with FTP. I don't remember if Anynet is available on V4R4, or if QFilesvr.400 is around. Gonna need some major planning on this....

Pete

[Pete]

Re: How to see the License key for the AS/400 and Moving aplication from one to anot

Hey Jaime, I just noticed my rep rating is 666! I like it, can you lock that in?

[jtemple]

Re: How to see the License key for the AS/400 and Moving aplication from one to anot

My $.02...

I dont think the OS release difference is going to matter. That would only matter if you were upgrading the OS on the V4R4 box to V5R4. Then you would have to do an intermediate jump. Of course I'm assuming that you will have both boxes at the same time... the V4R4 box and the V5R4 box (yes, I would suggest going to V5R4 first since V6R1 will require program conversion).

If memory serves, what we did was:

* Save all non-IBM libraries - SAVLIB LIB(*ALLUSR)
* Save the system config - SAVCFG
* Save IFS data - SAV - remember to omit QSYS.LIB
* Save security - SAVSECDTA

Then we took the tape and restored in the same order. This assumes that you will be able to hook the same tape drive up to both systems.

The beauty of this approach is you can test your procedure, make sure the software works on the new box, then do it all over again when you're ready to permanently switch. Make sure to document each step during the testing process.

[tomholden]

Re: How to see the License key for the AS/400 and Moving aplication from one to anot

My $.02...

I dont think the OS release difference is going to matter. That would only matter if you were upgrading the OS on the V4R4 box to V5R4. Then you would have to do an intermediate jump. Of course I'm assuming that you will have both boxes at the same time... the V4R4 box and the V5R4 box (yes, I would suggest going to V5R4 first since V6R1 will require program conversion).

If memory serves, what we did was:

* Save all non-IBM libraries - SAVLIB LIB(*ALLUSR)
* Save the system config - SAVCFG
* Save IFS data - SAV - remember to omit QSYS.LIB
* Save security - SAVSECDTA

Then we took the tape and restored in the same order. This assumes that you will be able to hook the same tape drive up to both systems.

The beauty of this approach is you can test your procedure, make sure the software works on the new box, then do it all over again when you're ready to permanently switch. Make sure to document each step during the testing process.

FWIW i would restore the security data first. that will prevent any object ownership changes. if the user profile that owns the objects saved do not exist when they are restore QDFTOWN becomes the "new" owner...which can cause some problems when apps use adopted authority.