Configuring and maintaining a subsystem description on the system i require quite some effort in terms of figuring out exactly how the many subsystem entry types should be dealt with. A subsystem description includes subsystem entries of many different types, such as autostart job, prestart job, workstation name and type, job queue, routing and communication entries. When creating a subsystem description the most appealing option is therefore often to copy an existing subsystem description and subsequently modify it to meet your actual needs.
While the Work with Subsystem Description (WRKSBSD) command allows you to see all the subsystem entries currently associated with the subsystem, there’s no way to manipulate these entries directly using this command. In stead you have to evoke a variety of add, change and remove commands for the specific subsystem entry type(s) that you need to perform some type of action against. This means entering all the information by hand, including the subsystem name and library. This approach is of course more error prone and time consuming than using list options supporting the pre-selection of already known command parameters. To alleviate this shortcoming I decided to provide Work with commands for the different subsystem entry types.
I’ve previously created a couple of subsystem entry commands for other purposes than the practical ones specifically pursued here, Adding to these an array of new subsystem entry commands, it is my intention in this article series to cover all subsystem entry types, and eventually to also provide a new Work with Subsystem Entries (WRKSBSE) command to front-end all these new commands.
Articles on Apis 