TCPIP profile needs better handling for deprecated parms / out of order parms

Hi IBM,
This past weekend, we had the upgrade on our production systems AMVS ,
where we moved from 2.1 to 2.2,post the IPL we had TCPIP that came up
without IPSEC as we had a degraded parm in the IPCONFIG block.

The problem was that a deprecated key word for claw devices was still
in the TCP/IP profile. This prevented TCP/IP from reading in the
IPCONFIG statements which unfortunately also included the IPSec
keyword. So AMvS came up with IPSecurity = no and so pagent does not
give iked its polices and looks like iked had the issue.

We removed the keyword and reipléd and it came up good.

00.09.33 STC18614 EZZ0334I IP FORWARDING IS DISABLED
00.09.33 STC18614 EZZ0351I SOURCEVIPA SUPPORT IS ENABLED
00.09.33 STC18614 EZZ0754I IPSEC STATEMENT WAS NOT PROCESSED BECAUSE
IP SECURITY IS NOT ENABLED
00.09.33 STC18614 EZZ0338I TCP PORTS 1 THRU 1023 ARE RESERVED
00.09.33 STC18614 EZZ0338I UDP PORTS 1 THRU 1023 ARE RESERVED

IPCONFIG NODATAGRAMFWD
SOURCEVIPA
STOPONCLAWERROR
MULTIPATH
PATHMTUDISCOVERY
NOSEGMENTATIONOFFLOAD
IPSECURITY
QDIOACCELERATOR
IGNOREREDIRECT

We understand that this parameter is not supported by 2.2, but we would
need a better handling of these situations by having a RFE to have all
the valid parameters accepted and only drop the invalid ones when
processing a configuration.

Also, the order of the parameters sometimes makes a difference if a
parameter will be used or not. All parameters should be analyzed and
accepted if valid not dropped just because they follow instead of
precede another parameter..

Also one more thing we would like to see for the IPCONFIG/TCPCONFIG
type portion of the profile is to have a begin and end block ,so the
stack knows it has to read the entire block till it reaches the END
portion for the corresponding set of statements. Like
VIPADYNAMIC/ENDVIPADYNAMIC or BEGINROUTES /ENDROUTES

So we need to have the IPCONFIG / TCPCONFIG sort of profile statements, to be changed to block statement format