So, I just did an upgrade of the BCD Software GUI Client (now owned by Fresche Legacy by the way) for a client. This upgraded their older version of Presto to PRESTO 8.1 Server. This also comes with a new Presto Client and Screen Designer adding some nice new tweaks.
The trouble is, the upgrade process (unchanged from this old blog) is pretty simple.
I did experience a sloppy code crash during the IBM i command portion of th upgqade – apparently because my profile didnt have *SECADM rights (I reported this to Fresche Support so hopefully they will add this validation to the upgrader for later releases).Me. Grumbling.
So, the upgrade process imports from your existing PRESTO library and creates a new version.
In my case it imported from my old version in LIB(XL_PRESTO) and created the new version in LIB(XL_PR81)
I want to keep my old library name (XL_PRESTO) and also my old IFS details. It’s a personal ‘library naming tidiness’ thing, and keeps a simple library name for the customer.
If you suspect you have multiple Presto environments but aren’t sure what they are, run this command:
WRKOBJ OBJ(*ALL/PR_HUB) OBJTYPE(*PGM)
The generated list will include all your Presto environment libraries.
You can remove the library XL_PRESTOI from your system at any time after installing the software.
Using command RNMPRLIB you can rename the Presto Lib. This is a custom command that lives in your new version.
Backup and delete the original library – you cannot rename it because it has journals in it and these stop library renames from happening.
CRTSAVF FILE(QGPL/XL_PRESTO) TEXT('Backup of XL_PRESTO after upgrade/rename')
SAVLIB LIB(XL_PRESTO) DEV(SAVF) SAVF(QGPL/XL_PRESTO) TGTRLS(CURRENT)
If you look at the QHTTPSVR subsystem, you should see if you have any PRESTO instances running. In this case you can see that my new XL_PR81 version is active:
Obviously, we need to end the active connections before renaming them:
ENDTCPSVR SERVER(*HTTP) HTTPSVR(XL_PR81)
Once its ended – lets get on with the rename
We need to add the new library to our *LIBL so we can access the command. When the library is renamed it will be renamed within our *LIBL automatically.
RNMPRLIB OLDLIB(XL_PR81) NEWLIB(XL_PRESTO)
NOTE: if you get a message saying “Error: This Library is locked. Use the WRKOBJLCK command to work with the locks.” then just use WRKOBJCLK XL_PR81 *LIB to find if anyone else out there is using it. Politely ask them to sign off. Or rudely. Your call 🙂
During the rename I was bit by a problem:
This looks like the renamer isn’t handling deleting the renamed IFS directory because it has objects in it (we do because we have custom stuff in there)
I just ignored this error, becase I have a full backup of all my stuff to restore manually if it all goes wrong.
Give it an ‘I’ and let it get on.
When the process has finished you will see that your new library is named correctly:
STRTCPSVR SERVER(*HTTP) HTTPSVR( xl_presto )
Remember to make sure your EXODUS subsystem is running:
Now you should be able to connect using your regular URL to get into the wonderful world of IBM I Web Screens (as opposed to the smelly old world of green screen AS400 and iSeries)
NOTE: If you find you are missing a theme file then copy the old theme folder to your new upgraded IFS folder
IBM i Software Developer, Digital Dad, AS400 Anarchist, RPG Modernizer, Alpha Nerd and Passionate Eater of Cheese and Biscuits. Nick Litten Dot Com is a mixture of blog posts that can be sometimes serious, frequently playful and probably down-right pointless all in the space of a day. Enjoy your stay, feel free to comment and in the words of the most interesting man in the world: Stay thirsty my friend.
How to rename IFS Files
Cleaning messy IBM i Integrated File System (IFS) file names
IBM i ACS 5250 EMULATOR FONT – and other ridiculous mumbo jumbo
The State of AS400 iSeries Application Modernization
Email every spool file in an output queue – EMLOUTQ for IBM i
Send IBM i Email including SQL Table Data automatically
I remember the IBM AS400
How to ZIP AS400 library and Email it
Interview Question and Answer – AS400 iSeries