Enhance SNDPTFORD command: Increase PTF limit to 300, add RLS parameter

Modernize the SNDPTFORD command to improve security remediation and simplify multi-version partition migration setups without drastically changing the core command architecture.

With the increasing number of critical security vulnerabilities (CVEs) affecting open-source and native components on IBM i, administrators need to rapidly order large numbers of PTFs. The current rigid limit of 20 PTFs per command forces administrators to script multiple separate calls.

Furthermore, performing an OS upgrade always requires downloading and preparing critical security patches (CVE fixes) and specific PTF Groups for the target release. Properly managing OS version directly inside SNDPTFORD is essential; it avoids the risky and inefficient requirement of having to temporarily align or update the current partition's to the level of other systems just to pull the correct fixes. Streamlining this process directly from the native command eliminates unnecessary manual overhead and accelerates time-to-patch for critical security vulnerabilities during infrastructure lifecycles.

Proposed Enhancements:

1. Increase PTFID Limit to a Constant of 300:
   • Expand the max repetitions allowed in the PTFID list parameter from 20 to 300 elements (matching standard extended list limits found in other IBM i commands like APYPTF).
2. Add a RLS (OS Release) Parameter:
   • Introduce a RLS parameter (e.g., *CURRENT, V7R5M0, V7R6M0) similar to the parameter used in SAVOBJ or CRTCLPGM.
   • This will allow administrators to explicitly bypass the partition's local level 
3. Incorporate a CVE-based Ordering Mechanism:
   • Introduce a way to order PTFs directly linked to specific security vulnerabilities (e.g., via a new parameter like CVEID or allowing CVE IDs to be processed within the PTFID field).
   • This addresses the constant influx of CVEs and streamlines audit remediation directly from the green screen.