Welcome to the OSSILE project. This project is to serve three purposes:
- This project is to provide, via the open source community, a wide set of utilities for IBM i. They will get built into the OSSILE library.
- This project is to provide working examples of various things in ILE languages (RPG, C, C++)
- This project is to provide working examples of SQL (while not technically ILE, the examples are included here due to strong affinity and usefulness)
Currently included in OSSILE
Useful UDTF's originally sourced from https://bitbucket.org/christianjorgensen/
CRTFRMSTMF originally sourced from https://bitbucket.org/BrianGarland/
GETIPTF, originally sourced from http://bryandietz.us/getiptf.html
C program samples originally sourced from ChrisHird/OSSILE
- BACKUP Program to run backups using BACKUP options and Image Catalogs and copy to remote file server.
- CHKRCVRDLT Program to clean up receivers based on days since detatched.
- CHKOSLVL Program to display the current OS level.
- DSPCSTINF Program to display the constraints attached to a file.
- DSPTRGINF Program to display the triggers attached to a file.
- DSPDQINF Prgram to display a data queue attributes
- DSPUSRIDX Program to display a User Index attributes plus the content (text only).
- FTPCLNT an alternative FTP Client to the OS command line.
- JOBLIST Program to display the currently active jobs and some of their attributes.
- LSTDBRTST Program to display the database relationships for a file.
- RTVJRNOBJ Program to display the objects currently journalled to a journal.
- MD5CRC Program to generate a CRC for the content of a DB file.
- RTVDIRSZ Program to log the content and sizes of a directory plus calculate the total size.
- SRVPGMCHK Program to check the signatures of a service program and a program to ensure the program can call the Service program.
- SYSINFO Program to retrieve and display system status.
- ZLIB ZLIB Open Source for IBM i.
sha256, originally sourced from https://github.com/miguel-r-s/SHA-256 a re-implementation of SHA256 in C. Documentation:
ArrayList, originally sourced from RPG Next Gen. An ArrayList is a one-dimensional array. It is also a dynamic array which means that the size is not set at compile time but at runtime and it can grow if required.
SU, originally sourced from bitbucket.org/cmasseVolubis/volubis. Like Under Linux, become QSECOFR as needed
Linked List, originally sourced from RPG Next Gen. An array allocates memory for all its elements lumped together as one block of memory. In contrast, a linked list allocates space for each element separately in its own block of memory called a linked list element or node. The list gets is overall structure by using pointers to connect all its nodes together like the links in a chain.
Installing OSSILE on your IBM i
Method 1: download the .zip file and compile
- Download https://github.com/OSSILE/OSSILE/archive/master.zip and place it in IFS
From a PASE-capable shell (ssh client, QP2term, etc), run:
jar xvf OSSILE-master.zip
cd OSSILE-master/main && chmod +x ./setup && ./setup
To exclude an item from building, remove it from buildlist.txt or comment it out with a preceding '#'
Method 2: Download *SAVF
- Create a save file object on IBM i.
- Download https://github.com/OSSILE/OSSILE/blob/master/ossile.savfsrc and upload it to the IBM i, replacing the contents of the save file you've created
- Use the RSTLIB command to restore the OSSILE library from the save file. For example:
RSTLIB SAVLIB(OSSILE) DEV(*SAVF) SAVF(MYLIB/MYSAVF)
Method 3: Installing via Relic Package Manager
Each directory in
/main/ is a seperate item, each are installable seperatly with Relic. The base command is
RELICGET PLOC('https://github.com/OSSILE/OSSILE/archive/master.zip') PDIR('OSSILE-master/main/<ITEM>') PNAME(OSSILE), where
<ITEM> is one of those directories. For example:
OSSILE directory structure
These are the main directories within OSSILE:
This directory houses complete, buildable code. In other words, it contains all the tools and utilities we list above as "included in OSSILE". Each subdirectory represents a separate buildable item.
This is where one can find examples of how to accomplish various tasks in ILE languages. They do not need to be working, compilable examples, though that is preferred. Inside this directory, there are subdirectories for the various ILE languages. The code examples are located in the appropriate lanuage directory.
This directory houses examples of how to accomplish various tasks using SQL scripts.