Re: How many IBM i commands are obsolete?

Most if not all of the communication methods that are listed as not being supported and the commands being removed are in the category of no supported hardware that might work with them. IE: token ring. Gone. Bisynch. Gone. Twinaxial, gone. Etc, etc.

Let’s stop having IBM spending money on maintaining that stuff and move on


Jim Oberholtzer
Agile Technology Architects

On Oct 17, 2024, at 9:44 AM, Rob Berendt <robertowenberendt@xxxxxxxxx> wrote:

On currently supported versions of the operating system, how many IBM i
commands are obsolete?

For example, is there a Power system out there which supports IBM i 7.5 and
still has the hardware for the following commands
https://www.ibm.com/docs/en/i/7.5?topic=communications-creating-line-description
Create Line Description (Asynchronous Communications) (CRTLINASC)
Create Line Description (Binary Synchronous Communications) (CRTLINBSC)
Create Line Description (Point to Point Protocol Communications) (CRTLINPPP)
Does anyone use these on a 7.5 system?
I know that 7.5 will be the last release to support bisync as per
https://www.ibm.com/support/pages/node/668193

Other examples:
CRTCTLLWS Although I may be wrong as per WRKCTLD CTLD(*LWS) for that
phantom one for the hmc based system console.
Many of the options on CRTDEVDSP

I am sure there are numerous other commands which are obsolete.
Some of my ideas pertaining to this genre:
https://ibm-power-systems.ideas.ibm.com/ideas/IBMI-I-2663
https://ibm-power-systems.ideas.ibm.com/ideas/IBMI-I-3587
https://ibm-power-systems.ideas.ibm.com/ideas/IBMI-I-1556

Dear God please don't let this descend into a geezer contest lamenting the
loss of card readers, direct attach impact printers and twinax terminals.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.