Join the PROJEX4I IBM i Software Developer Community
Install the PROJEX POWERTOOLS for IBM i Software Developers
Current version uses a simple FTP based installation process, you just need to follow these steps
- Download the Install ZIP file to your PC
- Unzip into a folder on your PC
- From the PC – Run the INSTALL.BAT command to FTP to your IBM i System
- From your IBM i – Run the @INSTALL command to setup the Projex4i environment
Now, sip your coffee, smile self indulgently and use the many commands, utilities and tools.
So lets do this thing:
1 – DOWNLOAD THE DISTRIBUTION ZIP FILE
Download the PROJEX4i ZIP file to your PC
This ZIP file contains a standard IBM i V7.2 *SAVF and simple .BAT file which will install the software on your IBM i System.
When you have downloaded the ZIP file you can see it should look something like this:
Unzip this file to a folder on your PC.
2 – Run the INSTALL.BAT file
You can double-click the install.bat file or run it from a command line. It will prompt you to enter your IBM i System Name, your User ID and your password:
Now we simply follow the prompts and it will give us status messages about how the install is going:
When the upload and restore has finished you will have a library called PROJEX4I on your IBM i SYSTEM.
The library should have at 440+ Objects in it:
3 – Setup the PROJEX4i environment
This gives the application a brief cough and drop, create a environment library, relevant help text and to tailor each command for your system. This will let you set various specific details about how PROJEX will look and feel for your IBM i system:
PROJEX4I/@SETUP USERNAME('your name') COMPANY('your company')
optionally you can add a library to put the *CMDs in. If you have a library that is the developers library list then they will automatically have access to the PROJEX4i utilities so add the optional parm
PROJEX4I/@SETUP USERNAME('your name') COMPANY('your company') DUPCMDLIB(QUSRSYS)
Voila! PROJEX4i is now ready to go 🙂
That wasnt that hard was it? 😉
Installation and setup works best using *SECOFR authority, because the @SETUP command creates an environment library (PROJEXENV), authority lists and change object ownership to a default setting of QPGMR. If you dont have *SECOFR right then use something with QPGMR with authority to Create and Restore libraries and other items such as Output queues, job descriptions and the IBM Job scheduler.
Dont worry, if the setup routine fails with an authority problem – just run it again. It has been designed so that it can be repeated without any problems.