PDSE libraries are required for the installation of AION.
This is not advisable.
There are some reasons for it that a PDS/E library is required for the installation of our products.
The following Aion supplied libraries (SYSLIB, RECLIB, DYNRLIB, DATALIB, DLILIB, IOLIB, MQLIB, DYNRDLIB, DYNRELIB, and ADSV7LIB) MUST be a BIN PDS/E library.
These PDS/Es contain binary code for interpreted execution (PROGRAM OBJECT FORMAT 3 member) and other necessary members. Unfortunately, no particular information exists which of these members are type 3.
All .BIN data sets must be installed as .BIN=PDS/E. CleverPath Aion generated data sets such as 'userid.appname.BUILD' and 'userid.appname.BIN' MUST remain in PDS/E format.
Also, you need to use PDS/Es for all user application DLLs built with the XPLINK option.
PTFs are prepared for the aionhlq.LOAD library using the TSO/E TRANSMIT command. Modules that are transmitted from a PDS/E can only be received into a PDS/E. If a module that was transmitted from a PDS/E is received into a PDS, the TSO/E RECEIVE command will mark the PDS as permanently unusable. Afterwards, the PDS would have to be reallocated from scratch, and members would need to be restored from backup sources.
In addition, the members of the the aionhlq.LOAD library are program objects, not load modules. These members must be stored in a PDS/E.
In r10.2, the MAES load module library was a PDS. In r11.0, this library will be distributed as a PDS/E. All r11.0 z/OS modules will be distributed in PDS/E libraries.