🚀 go-pugleaf

Two questions concerning MACLIBs on CMS.
1. Has anyone written a reasonably safe and efficient COMPRESS command to
   squeeze out unused space from a MACLIB?  The MACLIB COMPRESS option seems
   slightly inefficient concerning disk space usage.  Our system has SMALL
   minidisks and our MACLIBs are L A R G E.  I understand the problems with
   safely copying members from the old maclib to the other, but with a backup
   copy of the MACLIB in spool, I don't think I am in great danger (my system
   doesn't just die in the middle of the day.

2. Is there any way to use a "set of files" instead of a MACLIB for the
   ASSEMBLER SYSLIB filedef?  Guess what, two of us is use ISPF/PDF to develop
   lots of code, macros and structured programs, and they are lirical about
   the "set of file" concept of ISPF/PDF.  This means they can edit lots of
   files with FILETYPE MACRO from one member selection list.
   When they want to use these macros in an assembly, they have to do a MACLIB
   ADD command, and our minidisk space is pretty small.  These two are getting
   fed up of using MACLIBs to do their development, because of the above
   problem.  Compressing your maclib every 20 minutes seems to be frustrating.

   I can see two options:
 - a patch in one of the IEV modules to accept files with some kind of FILETYPE
   before searching in the GLOBAL MACLIBs for a member
 - a FILEDEF exit which you specify on the SYSLIB filedef.  This exit would
   accept the filenames (with asteriks) for SYSLIB and look at any file that
   fits this mask.

Suggestions or help on both accounts is appreciated.