Hi Charles,
Possibilities of the post shipment are (I would say) kind of unlimited.
i have done post shipment processing for more then 10 years already (even when it was not yet available by Endevor itself), everything running under the altid (now it is enabled by Endevor from V17). Db2 binds and Cics new copies are quite obvious. I also did Idms updates (new copies and IDD updates, generations etc,). I also created jobs in the post shipment to be executed in the scheduler in Prod. Another one I did was doing ftp job submission to the prod lpar and retrieving the job output automatically (ftp fetaure). I also created a connection between RA (Release Automation aka Nolio) and Endevor to have the deployment done by RA instead of Endevor. RA then will take care of updating the Endevor instance with ship date/time and failure/success.
If you need different Jcllib statements per destination of more then 2 or 3 lines, you need to do some tweaking in the Endevor Ispf Skeletons (mainly) and 2 or 3 Panels. With this you can have as many Jclorder statement lines as you like.
The way I work, is to generate members in what I call Shipinfo datasets. They are created in the Endevor processors and shipped as script-files. Basically it contains the element name, processor group and an indication whether it is Db2 (or not). Flattening this script-file allows you to sort (and include) special types/processor groups and Db2 modules to be bound. Some customers create the Bind statements already in a processor and ship those.
regards Piet