Try-AS/400 - User contributions [en]

Post-Install Optimizations

2023-09-14T11:20:38Z

Rogueai:

OS/400 provides a lot of default values for variables (affecting the run-time environment) and program options. Some of these make sense, some of them are kept consistent with earlier versions of the OS because of compatibility reasons by IBM.

Some of these recommendations might not be appropriate for you by various reasons. Don't apply blindly. Know what you do, use the online help to retrieve background information on the topic in question.

The findings below are based on V4R5 with annotated exceptions for newer releases.

== Housekeeping ==
These are settings and scheduled jobs to keep your system uncluttered.

=== Change unneeded programs to not run ===
We most likely don't need to run ''lpd'' and ''smtpd'' to run per default.
CHGLPDA AUTOSTART(*NO)
CHGSMTPA AUTOSTART(*NO)

You can easily check all settings at once by using <code>STRDFU OPTION(5)</code> on the file ''QUSRSYS/QATOCSTART''. These are not needed in general. Depending on OS version, not all entries may be available.
* *DIRSRV
* *NETSVR
* *SLP

=== Change uninstalled programs to not run ===
If you did not install the Ultimedia package, you can remove the pre started job from the QSYSWRK subsystem description to make it not generate an error message at IPL time.
RMVPJE SBSD(QSYSWRK) PGM(QUMEDIA/QUMBPJTC)

If you did not install the Directory Services package (aka LDAP), you can remove the auto started jobs from the QSYSWRK subsystem description to make them not generate an error message at IPL time.
RMVAJE SBSD(QSYSWRK) JOB(QGLDPUBA)
RMVAJE SBSD(QSYSWRK) JOB(QGLDPUBE)

Both is valid and tested for V4R5.

If you did not install the performance tools, you don't need trying to start the performance data collector:
RMVAJE SBSD(QCTL) JOB(QPFRCOL)

I can't remember if this is valid for V4R5. It's valid for V3R2, though.

=== Cleanup unneeded stuff ===
These objects come by default at OS install time, are not needed to my knowledge, and thus can be safely deleted:
DLTOUTQ OUTQ(QDKT)
DLTOUTQ OUTQ(QPFROUTQ)
DLTOUTQ OUTQ(QPRINTS)
DLTF FILE(QPRINTS)
DLTOUTQ OUTQ(QPRINT2)
DLTF FILE(QPRINT2)
DLTOUTQ OUTQ(QTPPPOUTQ)
DLTDEVD DEVD(QESPAP)
DLTDEVD DEVD(QIADSP)
DLTDEVD DEVD(QIAPRT)
DLTDEVD DEVD(QQAHOST)
DLTDEVD DEVD(QTIDA)
DLTDEVD DEVD(QTIDA2)
DLTCTLD CTLD(QESCTL)
DLTCTLD CTLD(QTICTL)
DLTLIND LIND(QESLINE)
DLTLIND LIND(QTILINE)

== System Values ==
System values are like environment variables as known from common operating systems. They influence system operation. I recommend the following changes.

=== System Control ===
* Change work environment to separate subsystems for different kind of jobs. This also makes it easy to introduce your own subsystems.
CHGSYSVAL SYSVAL(QCTLSBSD) VALUE('QCTL QSYS')
* Set automatic DST adjustment, and UTC offset. This value is valid for Central Europe (Berlin, Paris, …) '''Note!''' This variable is not available in V4R5.
CHGSYSVAL SYSVAL(QTIMZON) VALUE('QP0100CET2')
* Adjust time to automatically end disconnected interactive jobs (sessions) to one day.
CHGSYSVAL SYSVAL(QDSCJOBITV) VALUE('1440')

=== (Memory) Allocation ===
* Adjust automatic performance values only at runtime, not at IPL.<ref>If you change the amount of memory for the machine, temporarily adjust the value to '2', make the memory change and then change the value back to '3' — no further IPL needed.</ref>
CHGSYSVAL SYSVAL(QPFRADJ) VALUE('3')
* Allow memory pools to self adjust the paging block size depending on jobs running. This is called ''Expert Cache''. You can adjust the maximum active jobs per pool in the <code>WRKSHRPOOL</code> display.<ref>Press <code>F21</code> to switch to view 2 or 3 to have adjustment possibilities.</ref>
CHGSHRPOOL POOL(*BASE) PAGING(*CALC)
CHGSHRPOOL POOL(*INTERACT) PAGING(*CALC)
CHGSHRPOOL POOL(*SPOOL) PAGING(*CALC)
* Reservations for job related data structures at IPL time. See <code>DSPSYSSTS</code> and set to slightly more than the ''Jobs in System'' value to be seen there.<ref>Press <code>F21</code> to switch to view 2 or 3 to see the overall job count.</ref>
CHGSYSVAL SYSVAL(QTOTJOB) VALUE(100)
* Reservations for job related data structures at IPL time. See <code>WRKACTJOB</code> and set to slightly more than the ''Active Jobs'' value to be seen there.
CHGSYSVAL SYSVAL(QACTJOB) VALUE(95)
* Maximize TCP buffers for maximum performance, especially on faster links.
CHGTCPA TCPRCVBUF(8388608) TCPSNDBUF(8388608)
* Make sure, database tasks can use system resources as needed.
CHGSYSVAL SYSVAL(QQRYDEGREE) VALUE(*OPTIMIZE)
* When interactive jobs require more CPU time than being allowed by default (2 seconds),<ref>This is set in *CLS objects.</ref> to finish a block of processing, allow that memory to be taken from the *BASE pool. Advantage: The QINTER subsystem pool will not be subject to auto adjustment because of jobs which are supposed to run in batch.
CHGSYSVAL SYSVAL(QTSEPOOL) VALUE(*BASE)

=== Message-and-Logging ===
* Allow immediate deletion of problem reports.
CHGSYSVAL SYSVAL(QPRBHLDITV) VALUE(0)
* Do not log software errors. We can't do much about these anyway, seen from a hobbyist viewpoint.
CHGSYSVAL SYSVAL(QSFWERRLOG) VALUE(*NOLOG)
* Maximize Central Syslog (viewable with <code>DSPLOG</code> size to lessen rotation frequency. Depending on OS version only ''VALUE(32767)'' may be valid.
CHGSYSVAL SYSVAL(QHSTLOGSIZ) VALUE(*DAILY)
* Raise allowed unsuccessful sign on tries before taking action.
CHGSYSVAL SYSVAL(QMAXSIGN) VALUE('15')
* Minimize logging for sessions disconnected beause of device errors.
CHGSYSVAL SYSVAL(QDEVRCYACN) VALUE(*ENDJOBNOLIST)

=== Security System Values ===
* Unrestrict automatic creation of system objects triggered by external (network) requests.
CHGSYSVAL SYSVAL(QAUTOVRT) VALUE(*NOMAX)
* Allow restore with all security relevant flags.
CHGSYSVAL SYSVAL(QALWOBJRST) VALUE(*ALL)
* For TCP connections to work, we need encrypted passwords.
CHGDDMTCPA PWDRQD(*ENCRYPTED)
* Allow ''QSYSOPR'' signon to all devices.
CHGSYSVAL SYSVAL(QLMTSECOFR) VALUE('0')
* Raise maximum password length to maximum value.<ref>In newer OS versions, an additional variable ''QPWDLVL'' allows even longer passwords.</ref>
CHGSYSVAL SYSVAL(QPWDMAXLEN) VALUE(10)
* Raise minimum passsword length for security reasons.
CHGSYSVAL SYSVAL(QPWDMINLEN) VALUE(8)

=== Misc ===
* PTF install shall be done on unattended IPL time, and don't try to report problems to IBM directly.<ref>Needs prior setup for ''Electronic Customer Support''.</ref>
CHGSRVA PTFINSTYP(*DLYALL) RPTPRBAUTO(*NO)
* Provide European style formatting.
CHGSYSVAL SYSVAL(QCURSYM) VALUE('€')
CHGSYSVAL SYSVAL(QDECFMT) VALUE('J')
CHGSYSVAL SYSVAL(QSRTSEQ) VALUE(*LANGIDUNQ)<ref>This value isn't available with V4R5. You can use ''*LANGIDSHR'' there.</ref>
CHGSYSVAL SYSVAL(QDATFMT) VALUE('DMY')<ref>Default value for 2924 (US English) is MDY.</ref>
* Allow background compiling in PDM as ordinary user, and submitting batch jobs in general.
GRTOBJAUT OBJ(QGPL/QBATCH) OBJTYPE(*JOBD) USER(*PUBLIC) AUT(*USE)
* Tweaking automatic cleanup (like ''logrotate'').
CHGCLNUP ALWCLNUP(*YES) STRTIME('02:22:22') USRMSG(7) SYSMSG(3) SYSPRT(7) SYSLOG(14) CALITM(*KEEP)
* Change general SNA networking attributes. This is one '''long''' line. Take care to get it completely.
CHGNETA JOBACN(*SEARCH) VRTAUTODEV(254) MDMCNTRYID(DE)

=== Charset Conversion ===
In addition, OS/400 has a default value of 65535 for <code>QCCSID</code>. It should be set to a value being dependent on the installed language, to enable automatic translation of data on disk to the display device, and back. For Germany, the correct value is 273, and for US, it's 37. A good hint is to check your 5250 emulator program for possible values.

== IPL Customization ==
With this procedure, the current startup program for the OS can be retrieved for easy customization.
RTVCLSRC PGM(QSTRUP) SRCFILE(QCLSRC)
WRKMBRPDM FILE(QCLSRC) MBR(QSTRUP) MBRTYPE(CLP)
CRTCLPGM PGM(QGPL/QSTRUP)

To activate your changes, run <code>WRKSYSVAL SYSVAL(QSTRUPPGM)</code> and change the values to reflect the new program object in QGPL. '''Note''': On a used system's install, the previous owner might have already done a customized QSTRUP. See <code>DSPSYSVAL QSTRUPPGM</code> which one is the currently set startup program before accidentally overwriting!

Notable use cases for changing <code>QSTRUP</code> would be to make SNA Distribution Services, and TCP/IP (on older releases than V4R5) start at IPL time.

New entries must be located after the ''IF COND'' statement and ''DONE:'' label. Always put a ''MONMSG MSGID(CPF0000)'' after each statement. Failing to do so will not ignore any errors but make the IPL script terminate abnormally in case of an error and possibly leave you with an inaccessible system.

Examples:
* Start TCP/IP:
QSYS/STRTCP
MONMSG MSGID(CPF0000)

* Start SNADS:
QSYS/STRSBS SBSD(QSNADS)
MONMSG MSGID(CPF0000)

== Change Program Defaults ==
This establishes different default behavior of some programs which makes life somewhat easier.<ref>Some people highly oppose against changing default values because the default values have been provided for a reason. But then, the <code>CHGCMDDFT</code> also has been provided for a reason.</ref> At least noting down the changed programs and their former values is recommended, for example in <code>QGPL/QTXTSRC.CMDDFT</code>.
<blockquote>'''Note:''' CL applications might run a command with the changed default values, in turn combining (new) defaults and submitted parameters into an invalid combination of parameters which might lead to run-time errors.</blockquote>

* File creation and change defaults:
** Enforce immediate return to program error handling instead of make programs seem to hang (<code>wait…</code>),
** Enforce reusing deleted record space,<ref>If there is no access path defined, sequentially read records are no longer guaranteed to *be in timely order (FIFO)!</ref>
** Remove sizing restrictions,<ref>A runaway process filling the disks to 100 % is not stopped prior!</ref>
** Use a smaller access path size for probably increased performance,
** Allow automatic LF rebuild when running <code>chgpf</code>.
CHGCMDDFT CMD(CRTPF) NEWDFT('SIZE(*NOMAX *N *N) WAITFILE(*IMMED) WAITRCD(*IMMED) REUSEDLT(*YES)')
CHGCMDDFT CMD(CRTSRCPF) NEWDFT('SIZE(*NOMAX *N *N) ACCPTHSIZ(*MAX4GB)')
CHGCMDDFT CMD(CHGPF) NEWDFT('DLTDEPLF(*YES) SIZE(*NOMAX *N *N) WAITFILE(*IMMED) WAITRCD(*IMMED) REUSEDLT(*YES)')
CHGCMDDFT CMD(CRTLF) NEWDFT('WAITFILE(*IMMED) WAITRCD(*IMMED) ACCPTHSIZ(*MAX4GB)')
CHGCMDDFT CMD(CHGLF) NEWDFT('WAITFILE(*IMMED) WAITRCD(*IMMED) ACCPTHSIZ(*MAX4GB)')
* Menus usually go into the library with the application's other objects. Change current library to there, so applications can find their objects.<ref>It might be beneficial to individually use <code>CURLIB(*NOCHG)</code> for higher level menu objects being put into libraries which are part of the default library search list (''*LIBL'') — such as ''QGPL'' — to not needlessly change the default library in a for some users unexpected way.</ref>
CHGCMDDFT CMD(CRTMNU) NEWDFT('CURLIB(*MNULIB)')
* No unnecessary wait for power down. <code>CONFIRM(*NO)</code> can be added for newer releases to suppress prompting.
CHGCMDDFT CMD(PWRDWNSYS) NEWDFT('OPTION(*IMMED) ENDSBSOPT(*NOJOBLOG)')
* Don't waste time displaying a not so very much interesting screen prior to connection.
CHGCMDDFT CMD(STRPASTHR) NEWDFT('PASTHRSCN(*NO)')

Be aware that reinstalls, or applying PTFs can overwrite command objects and thus their default values.

== Regular Cleanup jobs ==
See job comment TEXT for details. These are '''long''' lines. Take care to get it completely.
ADDJOBSCDE JOB(PRGPRB) CMD(DLTPRB STATUS(*CLOSED)) FRQ(*WEEKLY) SCDDATE(*NONE) SCDDAY(*ALL) SCDTIME('13:22:00') MSGQ(*LIBL/QSYSOPR) TEXT('Purge closed and deletable problem entries')
ADDJOBSCDE JOB(RCLTMPSTG) CMD(RCLTMPSTG DAYS(30)) FRQ(*MONTHLY) SCDDATE(*MONTHSTR) SCDDAY(*NONE) SCDTIME('13:24:00') MSGQ(*LIBL/QSYSOPR) TEXT('Reclaim temporary storage')
ADDJOBSCDE JOB(RTVDSKINF) CMD(RTVDSKINF) FRQ(*MONTHLY) SCDDATE(*MONTHSTR) SCDDAY(*NONE) SCDTIME('13:34:00') MSGQ(*LIBL/QSYSOPR) TEXT('Retrieve disk space stats')
ADDJOBSCDE JOB(QPGMRCLR) CMD(CLRMSGQ MSGQ(QPGMR) CLEAR(*KEEPUNANS)) FRQ(*WEEKLY) SCDDATE(*NONE) SCDDAY(*ALL) SCDTIME('07:07:07') RCYACN(*NOSBM) MSGQ(*NONE) TEXT('Delete uninteresting messages')

== Re-Enable InfoSeeker ==
Only necessary for newer V4R4 and newer. If the command isn't known, don't bother: Then your release is so new that it's gone entirely.

See also: [[Reviving InfoSeeker]]

CRTDTAARA DTAARA(QUSRSYS/QBMGINFSKR) TYPE(*CHAR) LEN(8)<ref>Works in V4R5. The <code>STRINFSKR</code> command is not included anymore in IBM i 7.1, and probably earlier releases.</ref>

== Additional Steps tested with V7R2 ==
After trying to enter SST, one gets the message that the password has expired. But the password cannot be changed. Re-IPL in manual mode, or force DST display via control panel.

* Choose ''5. Work with DST environment'' and ''3. Service tools user IDs''.
** Disable the "backdoor" profile ''11111111'',
** ''Change password'' for ''QSECOFR'', ''Set password to expired'' to ''2=No''.
* Press F12 and choose ''5. Work with DST environment'' and ''6. Service tools security data''.
** Enter 0 into the field ''8. Password expiration interval in days'', 8 into the ''Selection'' field, and press return.
** Enter a high number (like 12) into the field ''9. Maximum sign-on attempts allowed'', 9 into the ''Selection'' field, and press return.
** Enter 0 into the field ''10. Duplicate password control'', 10 into the ''Selection'' field, and press return.

Now exit DST.

You may choose to enter SST, enter 7 for ''Work with system security'', and set ''Allow a service tools user ID with a default and expired password to change its own password'' to ''1=Yes''. Since we changed password expiry to ''never'', this step is entirely optional.

== See also ==
* [[Change Command Defaults for File-Commands]]
* [[How to properly shut down your AS/400]]

== Weblinks ==
* [https://archive.midrange.com/midrange-l/199912/msg01738.html STRINFSKR], Midrange Mailing-List

== Footnotes ==
<references />

[[Category: System Administration]]

Post-Install Optimizations

2023-06-23T16:20:21Z

Rogueai:

OS/400 provides a lot of default values for variables (affecting the run-time environment) and program options. Some of these make sense, some of them are kept consistent with earlier versions of the OS because of compatibility reasons by IBM.

Some of these recommendations might not be appropriate for you by various reasons. Don't apply blindly. Know what you do, use the online help to retrieve background information on the topic in question.

The findings below are based on V4R5 with annotated exceptions for newer releases.

== Housekeeping ==
These are settings and scheduled jobs to keep your system uncluttered.

=== Change unneeded programs to not run ===
We most likely don't need to run ''lpd'' and ''smtpd'' to run per default.
CHGLPDA AUTOSTART(*NO)
CHGSMTPA AUTOSTART(*NO)

You can easily check all settings at once by using <code>STRDFU OPTION(5)</code> on the file ''QUSRSYS/QATOCSTART''. These are not needed in general. Depending on OS version, not all entries may be available.
* *DIRSRV
* *NETSVR
* *SLP

=== Change uninstalled programs to not run ===
If you did not install the Ultimedia package, you can remove the pre started job from the QSYSWRK subsystem description to make it not generate an error message at IPL time.
RMVPJE SBSD(QSYSWRK) PGM(QUMEDIA/QUMBPJTC)

If you did not install the Directory Services package (aka LDAP), you can remove the auto started jobs from the QSYSWRK subsystem description to make them not generate an error message at IPL time.
RMVAJE SBSD(QSYSWRK) JOB(QGLDPUBA)
RMVAJE SBSD(QSYSWRK) JOB(QGLDPUBE)

Both is valid and tested for V4R5.

=== Cleanup unneeded stuff ===
These objects come by default at OS install time, are not needed to my knowledge, and thus can be safely deleted:
DLTOUTQ OUTQ(QDKT)
DLTOUTQ OUTQ(QPFROUTQ)
DLTOUTQ OUTQ(QPRINTS)
DLTF FILE(QPRINTS)
DLTOUTQ OUTQ(QPRINT2)
DLTF FILE(QPRINT2)
DLTOUTQ OUTQ(QTPPPOUTQ)
DLTDEVD DEVD(QESPAP)
DLTDEVD DEVD(QIADSP)
DLTDEVD DEVD(QIAPRT)
DLTDEVD DEVD(QQAHOST)
DLTDEVD DEVD(QTIDA)
DLTDEVD DEVD(QTIDA2)
DLTCTLD CTLD(QESCTL)
DLTCTLD CTLD(QTICTL)
DLTLIND LIND(QESLINE)
DLTLIND LIND(QTILINE)

== System Values ==
System values are like environment variables as known from common operating systems. They influence system operation. I recommend the following changes.

=== System Control ===
* Change work environment to separate subsystems for different kind of jobs. This also makes it easy to introduce your own subsystems.
CHGSYSVAL SYSVAL(QCTLSBSD) VALUE('QCTL QSYS')
* Set automatic DST adjustment, and UTC offset. This value is valid for Central Europe (Berlin, Paris, …) '''Note!''' This variable is not available in V4R5.
CHGSYSVAL SYSVAL(QTIMZON) VALUE('QP0100CET2')
* Adjust time to automatically end disconnected interactive jobs (sessions) to one day.
CHGSYSVAL SYSVAL(QDSCJOBITV) VALUE('1440')

=== (Memory) Allocation ===
* Adjust automatic performance values only at runtime, not at IPL.<ref>If you change the amount of memory for the machine, temporarily adjust the value to '2', make the memory change and then change the value back to '3' — no further IPL needed.</ref>
CHGSYSVAL SYSVAL(QPFRADJ) VALUE('3')
* Allow memory pools to self adjust the paging block size depending on jobs running. This is called ''Expert Cache''. You can adjust the maximum active jobs per pool in the <code>WRKSHRPOOL</code> display.<ref>Press <code>F21</code> to switch to view 2 or 3 to have adjustment possibilities.</ref>
CHGSHRPOOL POOL(*BASE) PAGING(*CALC)
CHGSHRPOOL POOL(*INTERACT) PAGING(*CALC)
CHGSHRPOOL POOL(*SPOOL) PAGING(*CALC)
* Reservations for job related data structures at IPL time. See <code>DSPSYSSTS</code> and set to slightly more than the ''Jobs in System'' value to be seen there.<ref>Press <code>F21</code> to switch to view 2 or 3 to see the overall job count.</ref>
CHGSYSVAL SYSVAL(QTOTJOB) VALUE(100)
* Reservations for job related data structures at IPL time. See <code>WRKACTJOB</code> and set to slightly more than the ''Active Jobs'' value to be seen there.
CHGSYSVAL SYSVAL(QACTJOB) VALUE(95)
* Maximize TCP buffers for maximum performance, especially on faster links.
CHGTCPA TCPRCVBUF(8388608) TCPSNDBUF(8388608)
* Make sure, database tasks can use system resources as needed.
CHGSYSVAL SYSVAL(QQRYDEGREE) VALUE(*OPTIMIZE)
* When interactive jobs require more CPU time than being allowed by default (2 seconds),<ref>This is set in *CLS objects.</ref> to finish a block of processing, allow that memory to be taken from the *BASE pool. Advantage: The QINTER subsystem pool will not be subject to auto adjustment because of jobs which are supposed to run in batch.
CHGSYSVAL SYSVAL(QTSEPOOL) VALUE(*BASE)

=== Message-and-Logging ===
* Allow immediate deletion of problem reports.
CHGSYSVAL SYSVAL(QPRBHLDITV) VALUE(0)
* Do not log software errors. We can't do much about these anyway, seen from a hobbyist viewpoint.
CHGSYSVAL SYSVAL(QSFWERRLOG) VALUE(*NOLOG)
* Maximize Central Syslog (viewable with <code>DSPLOG</code> size to lessen rotation frequency. Depending on OS version only ''VALUE(32767)'' may be valid.
CHGSYSVAL SYSVAL(QHSTLOGSIZ) VALUE(*DAILY)
* Raise allowed unsuccessful sign on tries before taking action.
CHGSYSVAL SYSVAL(QMAXSIGN) VALUE('15')
* Minimize logging for sessions disconnected beause of device errors.
CHGSYSVAL SYSVAL(QDEVRCYACN) VALUE(*ENDJOBNOLIST)

=== Security System Values ===
* Unrestrict automatic creation of system objects triggered by external (network) requests.
CHGSYSVAL SYSVAL(QAUTOVRT) VALUE(*NOMAX)
* Allow restore with all security relevant flags.
CHGSYSVAL SYSVAL(QALWOBJRST) VALUE(*ALL)
* For TCP connections to work, we need encrypted passwords.
CHGDDMTCPA PWDRQD(*ENCRYPTED)
* Allow ''QSYSOPR'' signon to all devices.
CHGSYSVAL SYSVAL(QLMTSECOFR) VALUE('0')
* Raise maximum password length to maximum value.<ref>In newer OS versions, an additional variable ''QPWDLVL'' allows even longer passwords.</ref>
CHGSYSVAL SYSVAL(QPWDMAXLEN) VALUE(10)
* Raise minimum passsword length for security reasons.
CHGSYSVAL SYSVAL(QPWDMINLEN) VALUE(8)

=== Misc ===
* PTF install shall be done on unattended IPL time, and don't try to report problems to IBM directly.<ref>Needs prior setup for ''Electronic Customer Support''.</ref>
CHGSRVA PTFINSTYP(*DLYALL) RPTPRBAUTO(*NO)
* Provide European style formatting.
CHGSYSVAL SYSVAL(QCURSYM) VALUE('€')
CHGSYSVAL SYSVAL(QDECFMT) VALUE('J')
CHGSYSVAL SYSVAL(QSRTSEQ) VALUE(*LANGIDUNQ)<ref>This value isn't available with V4R5. You can use ''*LANGIDSHR'' there.</ref>
* Allow background compiling in PDM as ordinary user, and submitting batch jobs in general.
GRTOBJAUT OBJ(QGPL/QBATCH) OBJTYPE(*JOBD) USER(*PUBLIC) AUT(*USE)
* Tweaking automatic cleanup (like ''logrotate'').
CHGCLNUP ALWCLNUP(*YES) STRTIME('02:22:22') USRMSG(7) SYSMSG(3) SYSPRT(7) SYSLOG(14) CALITM(*KEEP)
* Change general SNA networking attributes. This is one '''long''' line. Take care to get it completely.
CHGNETA JOBACN(*SEARCH) VRTAUTODEV(254) MDMCNTRYID(DE)

=== Charset Conversion ===
In addition, OS/400 has a default value of 65535 for <code>QCCSID</code>. It should be set to a value being dependent on the installed language, to enable automatic translation of data on disk to the display device, and back. For Germany, the correct value is 273, and for US, it's 37. A good hint is to check your 5250 emulator program for possible values.

== IPL Customization ==
With this procedure, the current startup program for the OS can be retrieved for easy customization.
RTVCLSRC PGM(QSTRUP) SRCFILE(QCLSRC)
WRKMBRPDM FILE(QCLSRC) MBR(QSTRUP) MBRTYPE(CLP)
CRTCLPGM PGM(QGPL/QSTRUP)

To activate your changes, run <code>WRKSYSVAL SYSVAL(QSTRUPPGM)</code> and change the values to reflect the new program object in QGPL. '''Note''': On a used system's install, the previous owner might have already done a customized QSTRUP. See <code>DSPSYSVAL QSTRUPPGM</code> which one is the currently set startup program before accidentally overwriting!

Notable use cases for changing <code>QSTRUP</code> would be to make SNA Distribution Services, and TCP/IP (on older releases than V4R5) start at IPL time.

New entries must be located after the ''IF COND'' statement and ''DONE:'' label. Always put a ''MONMSG MSGID(CPF0000)'' after each statement. Failing to do so will not ignore any errors but make the IPL script terminate abnormally in case of an error and possibly leave you with an inaccessible system.

Examples:
* Start TCP/IP:
QSYS/STRTCP
MONMSG MSGID(CPF0000)

* Start SNADS:
QSYS/STRSBS SBSD(QSNADS)
MONMSG MSGID(CPF0000)

== Change Program Defaults ==
This establishes different default behavior of some programs which makes life somewhat easier.<ref>Some people highly oppose against changing default values because the default values have been provided for a reason. But then, the <code>CHGCMDDFT</code> also has been provided for a reason.</ref> Noting down the changed programs and their former values is recommended, for example in <code>QGPL/QTXTSRC.CMDDFT</code>.

* File creation and change defaults: Enforce immediate return to program error handling instead of make programs seem to hang.
CHGCMDDFT CMD(CRTPF) NEWDFT('SIZE(*NOMAX *N *N) WAITFILE(*IMMED) WAITRCD(*IMMED) REUSEDLT(*YES)')
CHGCMDDFT CMD(CHGPF) NEWDFT('DLTDEPLF(*YES) SIZE(*NOMAX *N *N) WAITFILE(*IMMED) WAITRCD(*IMMED) REUSEDLT(*YES)')
CHGCMDDFT CMD(CRTLF) NEWDFT('WAITFILE(*IMMED) WAITRCD(*IMMED)')
CHGCMDDFT CMD(CHGLF) NEWDFT('WAITFILE(*IMMED) WAITRCD(*IMMED)')
* Menus usually go into the library with the application's other objects. Change current library to there, so applications can find their objects.<ref>It might be beneficial to individually use <code>CURLIB(*NOCHG)</code> for higher level menu objects being put into libraries which are part of the default library search list (''*LIBL'') — such as ''QGPL'' — to not needlessly change the default library in a for some users unexpected way.</ref>
CHGCMDDFT CMD(CRTMNU) NEWDFT('CURLIB(*MNULIB)')
* No unnecessary wait for power down. <code>CONFIRM(*NO)</code> can be added for newer releases to suppress prompting.
CHGCMDDFT CMD(PWRDWNSYS) NEWDFT('OPTION(*IMMED) ENDSBSOPT(*NOJOBLOG)')
* Don't waste time displaying a not so very much interesting screen prior to connection.
CHGCMDDFT CMD(STRPASTHR) NEWDFT('PASTHRSCN(*NO)')

== Regular Cleanup jobs ==
See job comment TEXT for details. These are '''long''' lines. Take care to get it completely.
ADDJOBSCDE JOB(PRGPRB) CMD(DLTPRB STATUS(*CLOSED)) FRQ(*WEEKLY) SCDDATE(*NONE) SCDDAY(*ALL) SCDTIME('13:22:00') MSGQ(*LIBL/QSYSOPR) TEXT('Purge closed and deletable problem entries')
ADDJOBSCDE JOB(RCLTMPSTG) CMD(RCLTMPSTG DAYS(30)) FRQ(*MONTHLY) SCDDATE(*MONTHSTR) SCDDAY(*NONE) SCDTIME('13:24:00') MSGQ(*LIBL/QSYSOPR) TEXT('Reclaim temporary storage')
ADDJOBSCDE JOB(RTVDSKINF) CMD(RTVDSKINF) FRQ(*MONTHLY) SCDDATE(*MONTHSTR) SCDDAY(*NONE) SCDTIME('13:34:00') MSGQ(*LIBL/QSYSOPR) TEXT('Retrieve disk space stats')
ADDJOBSCDE JOB(QPGMRCLR) CMD(CLRMSGQ MSGQ(QPGMR) CLEAR(*KEEPUNANS)) FRQ(*WEEKLY) SCDDATE(*NONE) SCDDAY(*ALL) SCDTIME('07:07:07') RCYACN(*NOSBM) MSGQ(*NONE) TEXT('Delete uninteresting messages')

== Re-Enable InfoSeeker ==
See also: [[Reviving InfoSeeker]]

CRTDTAARA DTAARA(QUSRSYS/QBMGINFSKR) TYPE(*CHAR) LEN(8)<ref>Works in V4R5. The <code>STRINFSKR</code> command is not included anymore in IBM i 7.1, and probably earlier releases.</ref>

== Additional Steps for at least V7R2 and probably newer ==
After trying to enter SST, one gets the message that the password has expired. But the password cannot be changed. Re-IPL in manual mode, or force DST display via control panel.

* Choose ''5. Work with DST environment'' and ''3. Service tools user IDs''.
** Disable the "backdoor" profile ''11111111'',
** ''Change password'' for ''QSECOFR'', ''Set password to expired'' to ''2=No''.
* Press F12 and choose ''5. Work with DST environment'' and ''6. Service tools security data''.
** Enter 0 into the field ''8. Password expiration interval in days'', 8 into the ''Selection'' field, and press return.
** Enter a high number (like 12) into the field ''9. Maximum sign-on attempts allowed'', 9 into the ''Selection'' field, and press return.
** Enter 0 into the field ''10. Duplicate password control'', 10 into the ''Selection'' field, and press return.

Now exit DST.

You may choose to enter SST, enter 7 for ''Work with system security'', and set ''Allow a service tools user ID with a default and expired password to change its own password'' to ''1=Yes''. Since we changed password expiry to ''never'', this step is entirely optional.

== See also ==
* [[Change Command Defaults for File-Commands]]
* [[How to properly shut down your AS/400]]

== Weblinks ==
* [https://archive.midrange.com/midrange-l/199912/msg01738.html STRINFSKR], Midrange Mailing-List

== Footnotes ==
<references />

[[Category: System Administration]]

User:Rogueai

2023-06-23T07:47:31Z

Rogueai: /* Cannot perform CHGNETA due to active APPC */

This page currently serves as my "braindump" to keep track of various findings while I explore the AS/400 world.

All the information available here is tested on the machine available to me: AS/400 9406-170 V4R2

== Screenshot script for tn5250j ==
While researching and trying out new things, I often find myself taking screenshots or saving the screen content as text.
To ease this process I wrote a simple jython script that can be used with tn5250j.

The script saves the current screen as both a txt and a png file.

The script must be placed inside <code>$HOME/.tn5250j/scripts</code> as a python source file, e.g.: <code>myScript.py</code>.
It can then be referenced from the "Macros" menu. A keybind can also be assigned to further ease the process.

Currently, output files are stored in <code>$HOME/Documents/as400/screens</code>, with the file names being in the format <code>screen-<yyyyMMdd-HHmmss>.[txt|png]</code>.
I'd suggest reviewing the script and customizing it to your liking before running it for the first time.

<syntaxhighlight lang="python">
from org.tn5250j.tools.encoder import EncodeComponent

from java.text import SimpleDateFormat
from java.util import Date
from java.lang import String
from java.lang import StringBuffer
from java.lang import System
from java.io import File

def fillBuffer(screen, sb):
chars = screen.getScreenAsChars()
c = screen.getColumns()
l = screen.getRows() * c

x = 0
y = 0
while x < l:
sb.append(chars[x])
if y == c - 1:
sb.append('\n')
y = 0
else :
y += 1
x += 1

print "--------------- tn5250j printScreen script start ------------"

home = System.getProperty("user.home")
filename = 'screen-' + SimpleDateFormat("yyyyMMdd-HHmmss").format(Date())
filepath = home + '/Documents/as400/screens/' + filename

screen = _session.getScreen()
sb = StringBuffer()

fillBuffer(screen, sb)

screen_txt = open(filepath + '.txt','w')
screen_txt.write(sb.toString())
screen_txt.close()

screen_png = open(filepath + '.png','w')
EncodeComponent.encode(EncodeComponent.PNG, _session, screen_png)
screen_png.close()

print "---------------- tn5250j printScreen script end -------------"

</syntaxhighlight>

== JTOpen/jt400 ==

This is a short list of notes about IBM' open source project [https://github.com/IBM/JTOpen JTOpen] aka jt400.

<blockquote>
JTOpen is the open source software product known as the "IBM Toolbox for Java." It is also commonly referred to "jt400" or simply "the toolbox."
In short, this package provides a set of Java classes that enable applications to integrate with IBM i
</blockquote>

The project's readme reports compatibility between different version of OS/400 as follows:
<syntaxhighlight>
Toolbox Installs on Connects to
release LPP release OS/400 version OS/400 version
------- -------------- -------------- --------------
V4R2 5763JC1 V3R2M0 V3R2 and up V3R2 and up
V4R3 5763JC1 V3R2M1 V3R2 and up V3R2 and up
V4R4 5769JC1 V4R2M0 V4R2 and up V4R2 and up
V4R5 5769JC1 V4R5M0 V4R3 and up V4R2 and up
V5R1 5722JC1 V5R1M0 V4R4 and up V4R3 and up
V5R2 5722JC1 V5R2M0 V4R5 and up V4R5 and up
V5R3(*) 5722JC1 V5R3M0 V5R1 and up V5R1 and up
V5R4(**) 5722JC1 V5R4M0 V5R2 and up V5R2 and up
JTOpen 1.x Not applicable Not applicable V4R3 and up
JTOpen 2.x Not applicable Not applicable V4R4 and up
JTOpen 3.x Not applicable Not applicable V4R5 and up
JTOpen 4.0-4.2 Not applicable Not applicable V4R5 and up
JTOpen 4.3-4.7 5722JC1 V5R3M0 V5R1 and up V5R1 and up
JTOpen 4.8+ 5722JC1 V5R4M0 V5R2 and up V5R2 and up
JTOpen 6.1+ 5761JC1 V6R1M0 V5R3 and up V5R3 and up
JTOpen 7.0+ 5770SS1 V7R1M0 V5R4 and up V5R4 and up

(*) Note: Toolbox release V5R3 is equivalent to JTOpen 4.3.
(**) Note: Toolbox release V5R4 is equivalent to JTOpen 4.8.
</syntaxhighlight>

The project was originally named "Java Toolbox", and later open sourced and rebranded as JTOpen 1.x.
The readme seems to imply that JTOpen (the open source version) has never been compatible with V4R2, however tn5250j is currently using JTOpen 10.5 and it seems to be working.

The reason could be that jt400 is actually a collection of modules, and tn5250j might be using only part of them. As a counter example, the latest ACS uses JTOpen 11.5 and doesn't work on V4R2, attempting to connect would fail. Tests on that side have pointed out to a possible change in the way JDBC connections are established.

The latest known version of JTOpen that's able to establish a JDBC connection is 5.3, as verified by running this simple JUnit test:
<syntaxhighlight lang="java">
public class JDBCTest {

@Test
public void test() throws SQLException {
AS400JDBCDriver driver = new AS400JDBCDriver();
DriverManager.registerDriver(driver);
Connection connection = DriverManager.getConnection("jdbc:as400://hostname", "user", "pass");
}

}
</syntaxhighlight>
Running this test using JTOpen 5.4 against V4R2 will result in a "General security error", which is the same error you'd get when trying to start a 5250 session on ACS.

Specifically, the AS/400 returns a: <code>SQL state 08004: The application server rejected establishment of the connection.</code>[https://www.ibm.com/docs/en/db2/9.7?topic=messages-sqlstate]

== Cannot perform CHGNETA due to active APPC ==

I got this error when trying to change my system's name from CHGNETA.

According to: [https://www.ibm.com/support/pages/qilanm3601-controller-description QILANM3601 Controller Description] (archive: [https://web.archive.org/web/20230623060930/https://www.ibm.com/support/pages/qilanm3601-controller-description])

<blockquote>
QILANM3601 controller description can cause some problems with the system. QILANM3601 is no longer supported and should be deleted.
</blockquote>

For my use case I decided to just disable it for the time being:

* <code>WRKCTLD</code>
* Locate <code>QILANM3601 *APPC</code>
* <code>8</code>, <code>2</code>

== Footnotes ==
<references />

User:Rogueai

2023-06-23T06:34:38Z

Rogueai:

This page currently serves as my "braindump" to keep track of various findings while I explore the AS/400 world.

All the information available here is tested on the machine available to me: AS/400 9406-170 V4R2

== Screenshot script for tn5250j ==
While researching and trying out new things, I often find myself taking screenshots or saving the screen content as text.
To ease this process I wrote a simple jython script that can be used with tn5250j.

The script saves the current screen as both a txt and a png file.

The script must be placed inside <code>$HOME/.tn5250j/scripts</code> as a python source file, e.g.: <code>myScript.py</code>.
It can then be referenced from the "Macros" menu. A keybind can also be assigned to further ease the process.

Currently, output files are stored in <code>$HOME/Documents/as400/screens</code>, with the file names being in the format <code>screen-<yyyyMMdd-HHmmss>.[txt|png]</code>.
I'd suggest reviewing the script and customizing it to your liking before running it for the first time.

<syntaxhighlight lang="python">
from org.tn5250j.tools.encoder import EncodeComponent

from java.text import SimpleDateFormat
from java.util import Date
from java.lang import String
from java.lang import StringBuffer
from java.lang import System
from java.io import File

def fillBuffer(screen, sb):
chars = screen.getScreenAsChars()
c = screen.getColumns()
l = screen.getRows() * c

x = 0
y = 0
while x < l:
sb.append(chars[x])
if y == c - 1:
sb.append('\n')
y = 0
else :
y += 1
x += 1

print "--------------- tn5250j printScreen script start ------------"

home = System.getProperty("user.home")
filename = 'screen-' + SimpleDateFormat("yyyyMMdd-HHmmss").format(Date())
filepath = home + '/Documents/as400/screens/' + filename

screen = _session.getScreen()
sb = StringBuffer()

fillBuffer(screen, sb)

screen_txt = open(filepath + '.txt','w')
screen_txt.write(sb.toString())
screen_txt.close()

screen_png = open(filepath + '.png','w')
EncodeComponent.encode(EncodeComponent.PNG, _session, screen_png)
screen_png.close()

print "---------------- tn5250j printScreen script end -------------"

</syntaxhighlight>

== JTOpen/jt400 ==

This is a short list of notes about IBM' open source project [https://github.com/IBM/JTOpen JTOpen] aka jt400.

<blockquote>
JTOpen is the open source software product known as the "IBM Toolbox for Java." It is also commonly referred to "jt400" or simply "the toolbox."
In short, this package provides a set of Java classes that enable applications to integrate with IBM i
</blockquote>

The project's readme reports compatibility between different version of OS/400 as follows:
<syntaxhighlight>
Toolbox Installs on Connects to
release LPP release OS/400 version OS/400 version
------- -------------- -------------- --------------
V4R2 5763JC1 V3R2M0 V3R2 and up V3R2 and up
V4R3 5763JC1 V3R2M1 V3R2 and up V3R2 and up
V4R4 5769JC1 V4R2M0 V4R2 and up V4R2 and up
V4R5 5769JC1 V4R5M0 V4R3 and up V4R2 and up
V5R1 5722JC1 V5R1M0 V4R4 and up V4R3 and up
V5R2 5722JC1 V5R2M0 V4R5 and up V4R5 and up
V5R3(*) 5722JC1 V5R3M0 V5R1 and up V5R1 and up
V5R4(**) 5722JC1 V5R4M0 V5R2 and up V5R2 and up
JTOpen 1.x Not applicable Not applicable V4R3 and up
JTOpen 2.x Not applicable Not applicable V4R4 and up
JTOpen 3.x Not applicable Not applicable V4R5 and up
JTOpen 4.0-4.2 Not applicable Not applicable V4R5 and up
JTOpen 4.3-4.7 5722JC1 V5R3M0 V5R1 and up V5R1 and up
JTOpen 4.8+ 5722JC1 V5R4M0 V5R2 and up V5R2 and up
JTOpen 6.1+ 5761JC1 V6R1M0 V5R3 and up V5R3 and up
JTOpen 7.0+ 5770SS1 V7R1M0 V5R4 and up V5R4 and up

(*) Note: Toolbox release V5R3 is equivalent to JTOpen 4.3.
(**) Note: Toolbox release V5R4 is equivalent to JTOpen 4.8.
</syntaxhighlight>

The project was originally named "Java Toolbox", and later open sourced and rebranded as JTOpen 1.x.
The readme seems to imply that JTOpen (the open source version) has never been compatible with V4R2, however tn5250j is currently using JTOpen 10.5 and it seems to be working.

The reason could be that jt400 is actually a collection of modules, and tn5250j might be using only part of them. As a counter example, the latest ACS uses JTOpen 11.5 and doesn't work on V4R2, attempting to connect would fail. Tests on that side have pointed out to a possible change in the way JDBC connections are established.

The latest known version of JTOpen that's able to establish a JDBC connection is 5.3, as verified by running this simple JUnit test:
<syntaxhighlight lang="java">
public class JDBCTest {

@Test
public void test() throws SQLException {
AS400JDBCDriver driver = new AS400JDBCDriver();
DriverManager.registerDriver(driver);
Connection connection = DriverManager.getConnection("jdbc:as400://hostname", "user", "pass");
}

}
</syntaxhighlight>
Running this test using JTOpen 5.4 against V4R2 will result in a "General security error", which is the same error you'd get when trying to start a 5250 session on ACS.

Specifically, the AS/400 returns a: <code>SQL state 08004: The application server rejected establishment of the connection.</code>[https://www.ibm.com/docs/en/db2/9.7?topic=messages-sqlstate]

== Cannot perform CHGNETA due to active APPC ==

I got this error when trying to change my system's name from CHGNETA.

According to: [https://www.ibm.com/support/pages/qilanm3601-controller-description QILANM3601 Controller Description] (archive: [https://web.archive.org/web/20230623060930/https://www.ibm.com/support/pages/qilanm3601-controller-description])

<blockquote>
QILANM3601 controller description can cause some problems with the system. QILANM3601 is no longer supported and should be deleted.
</blockquote>

For my use case I decided to just disable it for the time being:

* <code>WRKCTLD</code>
* Locale <code>QILANM3601 *APPC</code>
* <code>8</code>, <code>2</code>

== Footnotes ==
<references />

User:Rogueai

2023-06-04T12:15:45Z

Rogueai: Fixed tn5250j script

User:Rogueai

2023-06-03T16:45:26Z

Rogueai:

This page currently serves as my "braindump" to keep track of various findings while I explore the AS/400 world.

All the information available here is tested on the machine available to me: AS/400 9406-170 V4R2

== Screenshot script for tn5250j ==
While researching and trying out new things, I often find myself taking screenshots or saving the screen content as text.
To ease this process I wrote a simple jython script that can be used with tn5250j.

The script saves the current screen as both a txt and a png file.

The script must be placed inside <code>$HOME/.tn5250j/scripts</code> as a python source file, e.g.: <code>myScript.py</code>.
It can then be referenced from the "Macros" menu. A keybind can also be assigned to further ease the process.

Currently, output files are stored in <code>$HOME/Documents/as400/screens</code>, with the file names being in the format <code>screen-<yyyyMMdd-HHmmss>.[txt|png]</code>.
I'd suggest reviewing the script and customizing it to your liking before running it for the first time.

<syntaxhighlight lang="python">
from org.tn5250j.tools.encoder import EncodeComponent

from java.text import SimpleDateFormat
from java.util import Date
from java.lang import String
from java.lang import StringBuffer
from java.lang import System
from java.io import File

def fillBuffer(screen, sb):
chars = screen.getScreenAsChars()
c = screen.getColumns()
l = screen.getRows() * c
col = 0
x = 0
while x < l:
sb.append(chars[x])
if col == c:
sb.append('\n')
col = 0
x += 1
col += 1

print "--------------- tn5250j printScreen script start ------------"

home = System.getProperty("user.home")
filename = 'screen-' + SimpleDateFormat("yyyyMMdd-HHmmss").format(Date())
filepath = home + '/Documents/as400/screens/' + filename

screen = _session.getScreen()
sb = StringBuffer()

fillBuffer(screen, sb)

screen_txt = open(filepath + '.txt','w')
screen_txt.write(sb.toString())
screen_txt.close()

screen_png = open(filepath + '.png','w')
EncodeComponent.encode(EncodeComponent.PNG, _session, screen_png)
screen_png.close()

print "---------------- tn5250j printScreen script end -------------"

</syntaxhighlight>

== JTOpen/jt400 ==

This is a short list of notes about IBM' open source project [https://github.com/IBM/JTOpen JTOpen] aka jt400.

<blockquote>
JTOpen is the open source software product known as the "IBM Toolbox for Java." It is also commonly referred to "jt400" or simply "the toolbox."
In short, this package provides a set of Java classes that enable applications to integrate with IBM i
</blockquote>

The project's readme reports compatibility between different version of OS/400 as follows:
<syntaxhighlight>
Toolbox Installs on Connects to
release LPP release OS/400 version OS/400 version
------- -------------- -------------- --------------
V4R2 5763JC1 V3R2M0 V3R2 and up V3R2 and up
V4R3 5763JC1 V3R2M1 V3R2 and up V3R2 and up
V4R4 5769JC1 V4R2M0 V4R2 and up V4R2 and up
V4R5 5769JC1 V4R5M0 V4R3 and up V4R2 and up
V5R1 5722JC1 V5R1M0 V4R4 and up V4R3 and up
V5R2 5722JC1 V5R2M0 V4R5 and up V4R5 and up
V5R3(*) 5722JC1 V5R3M0 V5R1 and up V5R1 and up
V5R4(**) 5722JC1 V5R4M0 V5R2 and up V5R2 and up
JTOpen 1.x Not applicable Not applicable V4R3 and up
JTOpen 2.x Not applicable Not applicable V4R4 and up
JTOpen 3.x Not applicable Not applicable V4R5 and up
JTOpen 4.0-4.2 Not applicable Not applicable V4R5 and up
JTOpen 4.3-4.7 5722JC1 V5R3M0 V5R1 and up V5R1 and up
JTOpen 4.8+ 5722JC1 V5R4M0 V5R2 and up V5R2 and up
JTOpen 6.1+ 5761JC1 V6R1M0 V5R3 and up V5R3 and up
JTOpen 7.0+ 5770SS1 V7R1M0 V5R4 and up V5R4 and up

(*) Note: Toolbox release V5R3 is equivalent to JTOpen 4.3.
(**) Note: Toolbox release V5R4 is equivalent to JTOpen 4.8.
</syntaxhighlight>

The project was originally named "Java Toolbox", and later open sourced and rebranded as JTOpen 1.x.
The readme seems to imply that JTOpen (the open source version) has never been compatible with V4R2, however tn5250j is currently using JTOpen 10.5 and it seems to be working.

The reason could be that jt400 is actually a collection of modules, and tn5250j might be using only part of them. As a counter example, the latest ACS uses JTOpen 11.5 and doesn't work on V4R2, attempting to connect would fail. Tests on that side have pointed out to a possible change in the way JDBC connections are established.

The latest known version of JTOpen that's able to establish a JDBC connection is 5.3, as verified by running this simple JUnit test:
<syntaxhighlight lang="java">
public class JDBCTest {

@Test
public void test() throws SQLException {
AS400JDBCDriver driver = new AS400JDBCDriver();
DriverManager.registerDriver(driver);
Connection connection = DriverManager.getConnection("jdbc:as400://hostname", "user", "pass");
}

}
</syntaxhighlight>
Running this test using JTOpen 5.4 against V4R2 will result in a "General security error", which is the same error you'd get when trying to start a 5250 session on ACS.

Specifically, the AS/400 returns a: <code>SQL state 08004: The application server rejected establishment of the connection.</code>[https://www.ibm.com/docs/en/db2/9.7?topic=messages-sqlstate]

User:Rogueai

2023-06-03T15:37:04Z

Rogueai:

User:Rogueai

2023-05-29T05:47:40Z

Rogueai: AS/400 personal notes