Ignacio Valdes Implementation Log/Episode37 - Revision history

DavidWhitten: DavidWhitten moved page Episode37 to Ignacio Valdes Implementation Log/Episode37

2020-11-13T04:56:09Z

← Older revision	Revision as of 04:56, 13 November 2020
(No difference)

2020-11-13T04:55:51Z

← Older revision		Revision as of 04:55, 13 November 2020
Line 1:		Line 1:
			[[Ignacio_Valdes_Implementation_Log]]
			<pre>

	'''''Update 8/28/2011:''''' If your system is locked up, you have to up the MAX SIGNON ALLOWED as below. After that to prevent it from happening again you run XUS PROCESS COUNT CLEANUP and have Taskman run XUS PROCESS COUNT CLEANUP periodically. Sam says every hour.		'''''Update 8/28/2011:''''' If your system is locked up, you have to up the MAX SIGNON ALLOWED as below. After that to prevent it from happening again you run XUS PROCESS COUNT CLEANUP and have Taskman run XUS PROCESS COUNT CLEANUP periodically. Sam says every hour.

Line 1,729:		Line 1,732:
	Regards		Regards
	-- Bhaskar		-- Bhaskar
			</pre>

2012-04-26T18:32:00Z

Added a glossary link to Verification~

← Older revision		Revision as of 18:32, 26 April 2012
Line 88:		Line 88:

	Validation:		Validation:
	For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear		For [[verification~\|Verification]] purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
	Send Discard		Send Discard

Line 566:		Line 566:

	Validation:		Validation:
	For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear		For [[verification~\|Verification]] purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
	Send Discard		Send Discard

2012-03-05T12:12:39Z

Added glossary link to Prompt~

← Older revision		Revision as of 12:12, 5 March 2012
Line 587:		Line 587:
	Reply to author \| Forward \| Print \| Individual message \| Show original \| Report this message \| Find messages by this author		Reply to author \| Forward \| Print \| Individual message \| Show original \| Report this message \| Find messages by this author
	The only way I could login and increase the maximum number of users		The only way I could login and increase the maximum number of users
	was by using putty.exe into the server and getting to a gtm prompt		was by using putty.exe into the server and getting to a gtm [[prompt~\|Prompt]]
	direct. That was successful. -- IV		direct. That was successful. -- IV

Line 744:		Line 744:

	> The only way I could login and increase the maximum number of users		> The only way I could login and increase the maximum number of users
	> was by using putty.exe into the server and getting to a gtm prompt		> was by using putty.exe into the server and getting to a gtm [[prompt~\|Prompt]]
	> direct. That was successful. -- IV		> direct. That was successful. -- IV

Line 918:		Line 918:

	> > The only way I could login and increase the maximum number of users		> > The only way I could login and increase the maximum number of users
	> > was by using putty.exe into the server and getting to a gtm prompt		> > was by using putty.exe into the server and getting to a gtm [[prompt~\|Prompt]]
	> > direct. That was successful. -- IV		> > direct. That was successful. -- IV

2011-08-29T02:38:02Z

← Older revision		Revision as of 02:38, 29 August 2011
Line 1:		Line 1:
	Update 8/28/2011: If your system is locked up, you have to up the MAX SIGNON ALLOWED as below. After that to prevent it from happening again you run XUS PROCESS COUNT CLEANUP and have Taskman run XUS PROCESS COUNT CLEANUP periodically. Sam says every hour.		'''''Update 8/28/2011:''''' If your system is locked up, you have to up the MAX SIGNON ALLOWED as below. After that to prevent it from happening again you run XUS PROCESS COUNT CLEANUP and have Taskman run XUS PROCESS COUNT CLEANUP periodically. Sam says every hour.

	I received the dreaded Maximum number of users already signed on to		I received the dreaded Maximum number of users already signed on to

2011-08-29T02:36:26Z

← Older revision		Revision as of 02:36, 29 August 2011
Line 1:		Line 1:
			Update 8/28/2011: If your system is locked up, you have to up the MAX SIGNON ALLOWED as below. After that to prevent it from happening again you run XUS PROCESS COUNT CLEANUP and have Taskman run XUS PROCESS COUNT CLEANUP periodically. Sam says every hour.

	I received the dreaded Maximum number of users already signed on to		I received the dreaded Maximum number of users already signed on to
	this processor problem as well as a Netcall see ^XTER error (not exact		this processor problem as well as a Netcall see ^XTER error (not exact

2009-09-23T18:10:08Z

2009-09-09T14:39:49Z

2009-09-04T03:51:33Z

2009-09-04T03:44:53Z