Post-Install Optimizations - Revision history

PoC: Undo revision 1586 by PoC (talk): Doesn't work in context.

2025-10-28T09:50:55Z

Undo revision 1586 by PoC (talk): Doesn't work in context.

← Older revision		Revision as of 11:50, 28 October 2025
Line 169:		Line 169:
	* Don't waste time displaying a not so very much interesting screen prior to connection.		* Don't waste time displaying a not so very much interesting screen prior to connection.
	CHGCMDDFT CMD(STRPASTHR) NEWDFT('PASTHRSCN(*NO)')		CHGCMDDFT CMD(STRPASTHR) NEWDFT('PASTHRSCN(*NO)')
	* Send spooled output to what's defined in the job description instead of what's currently defined.
	~~CHGCMDDFT CMD(SBMJOB) NEWDFT('PRTDEV(JOBD) OUTQ(JOBD)')~~

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

PoC: /* Change Program Defaults */ This help that logs go where they belong by default when using wrkjobscde option 10

2025-10-20T20:10:58Z

Change Program Defaults: This help that logs go where they belong by default when using wrkjobscde option 10

← Older revision		Revision as of 22:10, 20 October 2025
Line 169:		Line 169:
	* Don't waste time displaying a not so very much interesting screen prior to connection.		* Don't waste time displaying a not so very much interesting screen prior to connection.
	CHGCMDDFT CMD(STRPASTHR) NEWDFT('PASTHRSCN(*NO)')		CHGCMDDFT CMD(STRPASTHR) NEWDFT('PASTHRSCN(*NO)')
			* Send spooled output to what's defined in the job description instead of what's currently defined.
			CHGCMDDFT CMD(SBMJOB) NEWDFT('PRTDEV(JOBD) OUTQ(JOBD)')

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

PoC: /* Change Program Defaults */ More preciise

2025-08-27T18:22:12Z

Change Program Defaults: More preciise

← Older revision		Revision as of 20:22, 27 August 2025
Line 170:		Line 170:
	CHGCMDDFT CMD(STRPASTHR) NEWDFT('PASTHRSCN(*NO)')		CHGCMDDFT CMD(STRPASTHR) NEWDFT('PASTHRSCN(*NO)')

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

	== Regular Cleanup jobs ==		== Regular Cleanup jobs ==

PoC: /* Change Program Defaults */ More precise

2025-08-27T18:20:17Z

Change Program Defaults: More precise

← Older revision		Revision as of 20:20, 27 August 2025
Line 150:		Line 150:
	== Change Program Defaults ==		== 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>.		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>		<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. As far as I'm aware, my proposed changes are compatible with such situations.</blockquote>

	* File creation and change defaults:		* File creation and change defaults:

PoC: /* Additional Steps tested with V7R2 */ More specific

2024-10-18T09:16:40Z

Additional Steps tested with V7R2: More specific

← Older revision		Revision as of 11:16, 18 October 2024
Line 187:		Line 187:

	== Additional Steps tested with V7R2 ==		== 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''', do not IPL but enter DST.		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''', do not IPL but enter DST, and change password as directed.

	* Choose ''5. Work with DST environment'' and ''3. Service tools user IDs''.		* Choose ''5. Work with DST environment'' and ''3. Service tools user IDs''.

PoC: /* Additional Steps tested with V7R2 */ Better wording

2024-10-14T14:04:26Z

Additional Steps tested with V7R2: Better wording

← Older revision		Revision as of 16:04, 14 October 2024
Line 187:		Line 187:

	== Additional Steps tested with V7R2 ==		== 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~~.		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''', do not IPL but enter DST.

	* Choose ''5. Work with DST environment'' and ''3. Service tools user IDs''.		* Choose ''5. Work with DST environment'' and ''3. Service tools user IDs''.
	** Disable the "backdoor" profile ''11111111'',		** Disable the "backdoor" profile ''11111111'',
	** ''Change password'' for ''QSECOFR'', ''Set password to expired'' to ''2=No''.		** ''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''.		* Press F12 and choose ''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 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 a high number (like 12) into the field ''9. Maximum sign-on attempts allowed'', 9 into the ''Selection'' field, and press return.

PoC: /* (Memory) Allocation */ Better explanations

2024-09-05T15:22:47Z

(Memory) Allocation: Better explanations

← Older revision		Revision as of 17:22, 5 September 2024
Line 65:		Line 65:

	=== (Memory) Allocation ===		=== (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>		* 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> This allows the system to automatically adjust memory allocations and activity levels to minimize paging (disk I/O).
	CHGSYSVAL SYSVAL(QPFRADJ) VALUE('3')		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>		* 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>
Line 71:		Line 71:
	CHGSHRPOOL POOL(INTERACT) PAGING(CALC)		CHGSHRPOOL POOL(INTERACT) PAGING(CALC)
	CHGSHRPOOL POOL(SPOOL) 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>		* 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 when the system is working "normal".<ref>Press <code>F21</code> to switch to view 2 or 3 to see the overall job count.</ref>
	CHGSYSVAL SYSVAL(QTOTJOB) VALUE(100)		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.		* 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 when the system is working "normal".
	CHGSYSVAL SYSVAL(QACTJOB) VALUE(95)		CHGSYSVAL SYSVAL(QACTJOB) VALUE(95)
	* Maximize TCP buffers for maximum performance, especially on faster links.		* Maximize TCP buffers for maximum performance, especially on faster links.

PoC: /* System Control */ remark

2024-09-05T15:13:35Z

System Control: remark

← Older revision		Revision as of 17:13, 5 September 2024
Line 59:		Line 59:
	* Change work environment to separate subsystems for different kind of jobs. This also makes it easy to introduce your own subsystems.		* 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')		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.		* Set automatic DST adjustment, and UTC offset. This value is valid for Central Europe (Berlin, Paris, …) '''Note!''' This variable is not available in V4R5. See [[#Weblinks\|Weblinks]] below.
	CHGSYSVAL SYSVAL(QTIMZON) VALUE('QP0100CET2')		CHGSYSVAL SYSVAL(QTIMZON) VALUE('QP0100CET2')
	* Adjust time to automatically end disconnected interactive jobs (sessions) to one day.		* Adjust time to automatically end disconnected interactive jobs (sessions) to one day.

PoC: /* Weblinks */ +link

2024-09-05T15:12:50Z

Weblinks: +link

← Older revision		Revision as of 17:12, 5 September 2024
Line 207:		Line 207:
	== Weblinks ==		== Weblinks ==
	* [https://archive.midrange.com/midrange-l/199912/msg01738.html STRINFSKR], Midrange Mailing-List		* [https://archive.midrange.com/midrange-l/199912/msg01738.html STRINFSKR], Midrange Mailing-List
			* [https://github.com/PoC-dev/as400-autodst as400-autodst], GitHub

	== Footnotes ==		== Footnotes ==

PoC: /* Change uninstalled programs to not run */ Expanded

2024-09-05T15:10:44Z

Change uninstalled programs to not run: Expanded

← Older revision		Revision as of 17:10, 5 September 2024
Line 26:		Line 26:
	RMVAJE SBSD(QSYSWRK) JOB(QGLDPUBE)		RMVAJE SBSD(QSYSWRK) JOB(QGLDPUBE)

	Both is valid and tested for V4R5.		Both is valid and tested for V4R5. Note that newer releases moved the background jobs to the base OS so there is no error message when starting them. I have not tested if they're required to run, though.

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

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

	=== Cleanup unneeded stuff ===		=== Cleanup unneeded stuff ===