The tool does not support editing of SYSn.IPLPARM data sets.
You can use the tool to generate the member in SYS1.PARMLIB or high_level_qualifier.PARMLIB
and then you can copy the member into the appropriate SYSn.IPLPARM
data set.
The tool assumes that any SYSn.IPLPARM data set is on the same
volume as the specified parmlib data set. It does not support the
concept of a separate IODF and SYSRES volume, nor does it use Master
Catalog to locate a SYSn.IPLPARM data set.
If the tool is running on a partial ship release or a point release,
in the Parmlib Processor Member Selection Panel under the FMID field,
use the LATEST keyword or a full ship release FMID to select the parser
release used to process or verify the SYS1.PARMLIB member that you
selected.
Although the code can detect the presence of a VSAM data set,
it does not have the ability to read one. Therefore, the IODF data
set is only checked for existence. Its contents are not verified.
The Master Catalog information is not verified.
When in EDIT mode, the data in a member is not altered until it
is saved. If you are running in split screen mode, you will not see
the effects of the changes until the EDIT mode changes are saved.
Syntax checking is not done generally for the parmlib members
that the tool lists as supported.
When processing an IEASYMxx parmlib member, the tool manipulates
the data into an internal format. If that internal format exceeds
320080 bytes, the tool will terminate, with a message indicating that
the IEASYMxx member is too large. It takes an IEASYMxx member on the
order of 10000 lines long to reach this limit. If the limit is exceeded,
the tool user will have to specify a different IEASYMxx member, possibly
created from the original member but with data for non-applicable
systems removed.