Noctam/DWP/ACS Test Harness/Existing System/CISSIM/Command Line Tools - Revision history

Stuart: Removed extraneous .py's

2021-10-19T08:28:16Z

Removed extraneous .py's

← Older revision		Revision as of 08:28, 19 October 2021
Line 413:		Line 413:
	DCI and PD; 2 groups of cert and private key files for serving.		DCI and PD; 2 groups of cert and private key files for serving.

	Used in [[#pdcall~~.py~~\|pdcall]], [[#pdserve~~.py~~\|pdserve]] and [[#pdstub~~.py~~\|pdstub]] programs, and in some test functions		Used in [[#pdcall\|pdcall]], [[#pdserve\|pdserve]] and [[#pdstub\|pdstub]] programs, and in some test functions
	in [[#sslutils~~.py~~\|sslutils]].		in [[#sslutils\|sslutils]].

	== checkport ==		== checkport ==
Line 434:		Line 434:
	the 12 fields and their sizes defined as fixed length byte arrays.		the 12 fields and their sizes defined as fixed length byte arrays.

	It's only used in [[#pdtux~~.py~~\|pdtux]] for extracting the data from an incoming DCI struct. The equivalent for a PD		It's only used in [[#pdtux\|pdtux]] for extracting the data from an incoming DCI struct. The equivalent for a PD
	record is [[#w80construct~~.py~~\|w80construct]]		record is [[#w80construct\|w80construct]]

	== extractodis ==		== extractodis ==
Line 446:		Line 446:
	* {{c\|<filename>.write.sh}}: to write the transaction for ACS emulation (just writing the record out)		* {{c\|<filename>.write.sh}}: to write the transaction for ACS emulation (just writing the record out)
	* {{c\|<filename>.conv.sh}}: to write the transaction for CIS emulation (calling [[#CONVERT2E\|pddump.py CONVERT2E]])		* {{c\|<filename>.conv.sh}}: to write the transaction for CIS emulation (calling [[#CONVERT2E\|pddump.py CONVERT2E]])
	* {{c\|<filename>.db.sh}}: to write the transaction to the 'database' for serving (calling [[#pddb~~.py~~\|pddb~~.py~~]])		* {{c\|<filename>.db.sh}}: to write the transaction to the 'database' for serving (calling [[#pddb\|pddb]])

	Aside from some very ropey python issues (mix of tabs and spaces in leading whitespace - very verboten in python),		Aside from some very ropey python issues (mix of tabs and spaces in leading whitespace - very verboten in python),
Line 452:		Line 452:

	This is the oldschool format; it's dealing with the records as is, rather than moving them to the date/nino-based		This is the oldschool format; it's dealing with the records as is, rather than moving them to the date/nino-based
	database used by [[#pdserved~~.py~~\|pdserved]] and beyond; the pddb output is used in the original		database used by [[#pdserved\|pdserved]] and beyond; the pddb output is used in the original
	[[#pdserve~~.py~~\|pdserve]] program too. It's still valid for the 'write.sh', I guess, but I suspect that's all.		[[#pdserve\|pdserve]] program too. It's still valid for the 'write.sh', I guess, but I suspect that's all.

	== fpcapprec ==		== fpcapprec ==
Line 460:		Line 460:
	{{obsolete}}		{{obsolete}}

	This was used in [[#pdtux~~.py~~\|pdtux]], but is no longer used. The using has been deleted, so I can't see the context.		This was used in [[#pdtux\|pdtux]], but is no longer used. The using has been deleted, so I can't see the context.

	== getfieldoffset ==		== getfieldoffset ==
Line 473:		Line 473:
	''Library file''		''Library file''

	This provides a few constants for keycodes, used in [[#pdedit~~.py~~\|pdedit]] and [[#pdscreen~~.py~~\|pdscreen~~.py~~]].		This provides a few constants for keycodes, used in [[#pdedit\|pdedit]] and [[#pdscreen\|pdscreen]].

	To be honest, it really needn't be here. The function key and some other constants are already defined in the curses		To be honest, it really needn't be here. The function key and some other constants are already defined in the curses
	module; most of the rest are defined in the curses.ascii module. {{c\|UP_LIST}} is home-made, but really doesn't		module; most of the rest are defined in the curses.ascii module. {{c\|UP_LIST}} is home-made, but really doesn't
	deserve its own file; any home-grown key values could go in the [[#pdscreen~~.py~~\|pdscreen]] file.		deserve its own file; any home-grown key values could go in the [[#pdscreen\|pdscreen]] file.

	== loadninos ==		== loadninos ==
Line 604:		Line 604:
	''Library file''		''Library file''

	Like [[#dci9n3rec~~.py~~\|dci9n3rec]], this can be called from the command line, but it also seems a bit pointless.		Like [[#dci9n3rec\|dci9n3rec]], this can be called from the command line, but it also seems a bit pointless.
	I guess it's for testing purposes.		I guess it's for testing purposes.

Line 612:		Line 612:
	works too?		works too?

	It's only used in [[#pdtux~~.py~~\|pdtux]] for extracting the data from an incoming DCI struct. The equivalent for a DCI		It's only used in [[#pdtux\|pdtux]] for extracting the data from an incoming DCI struct. The equivalent for a DCI
	record is [[#dci9n3rec~~.py~~\|dci9n3rec]]		record is [[#dci9n3rec\|dci9n3rec]]

	= Files in pdlayouts =		= Files in pdlayouts =

Stuart: Filled out pretty much everything.

2021-10-19T08:26:49Z

Filled out pretty much everything.

Show changes

Stuart: Expanded on pdserved and pdstub

2021-10-18T09:30:59Z

Expanded on pdserved and pdstub

← Older revision		Revision as of 09:30, 18 October 2021
Line 321:		Line 321:

	== pdserved ==		== pdserved ==
	An upgraded version of [[#pdserve\|pdserve]]. I~~'ll examine~~ the ~~differences shortly -~~ there ~~are quite~~ a ~~lot~~.		An upgraded version of [[#pdserve\|pdserve]] with NPS support and separate message directories.

			Usage: pdserved.py <port> -P <pddfolder> -D <dcifolder> [-N <npsfolder>]

			Aside from working in Python3 and adding the NPS handling which was added in [[#pdservep\|pdservep]], this primarily
			implements the separation of the data directories into 'PD', 'DCI' and 'NPS' folders. These could all be the same
			folder (I think), but the option is there now to have different ones for each type. Presumably, you might want
			different PD responses for different services, but you want to use the same DCI/NPS responses each time, so this
			saves on a load of copying and pasting.

	~~{{todo\|Analyse differences between pdserve and pdserved.}}~~

	== pdservedt ==		== pdservedt ==
Line 338:		Line 345:
	first value in any of the following tuples. If it does (in this case, the 20th and 100th time a dialog is processed		first value in any of the following tuples. If it does (in this case, the 20th and 100th time a dialog is processed
	within the server), it will use the timing associated with that number. Reasonably straightforward.		within the server), it will use the timing associated with that number. Reasonably straightforward.

			'''Note:''' This seems the most sensible one to draw a 'proper' version from. If we want to re-do the timing, then
			we could branch from [[#pdserved\|pdserved]] instead... it certainly needs changing a bit (the config is dire - a
			hardcoded filename in a directory reached using a relative path... ugh), and it's quite simplistic, but it does
			work.

	== pdservep ==		== pdservep ==
Line 354:		Line 366:

	== pdstub ==		== pdstub ==
			Stub server which provides more flexible lookup and response-modification than pdserve.

			Usage: pdstub <configfile> [<port>]

			This program provides a basic server which serves PD, DCI and NPS. Rather than a straight NINo/Rundate lookup, it
			uses search parameters to determine which response file to return for a request, and it allows replacement of data
			in that response file with static parameters, or inputs derived from the request.

			It uses a single messages folder, rather than the separated responses folder of pdserve and each request/response
			mapping is defined in a single line within the config file.

	== pdstubt ==		== pdstubt ==

Stuart: Updated with initial pdserve/pdstub findings

2021-10-15T12:32:53Z

Updated with initial pdserve/pdstub findings

@@ Line 321: / Line 321: @@
 == pdserved ==
 == pdservedt ==
 == pdservep ==
 == pdshow ==
 Shows and edits a base64-encoded file, extracting the dialog and direction from the filename.
@@ Line 332: / Line 354: @@
 == pdstub ==
 == pdstubt ==
 == pdstubtt ==
 == pdtux ==

Stuart: Added most of the stuff - just the server/stub programs and non-PD ones left to do.

2021-10-14T20:52:08Z

Added most of the stuff - just the server/stub programs and non-PD ones left to do.

Show changes

Stuart at 00:13, 12 October 2021

2021-10-12T00:13:55Z

← Older revision		Revision as of 00:13, 12 October 2021
Line 158:		Line 158:

	= pdacs =		= pdacs =

			Usage: pdacs <service> <dialog> <requestfile> <replyfile>



	= pdconvertall =		= pdconvertall =
	= pdconvertone =		= pdconvertone =
Line 194:		Line 199:
	= paths =		= paths =
	= ports =		= ports =
			Library file.

			This just holds all the ports for the CIS swimlanes and returns the appropriate ports for a given swimlane when asked, in the form {{c\|(pdd-port, dci-port, host)}}.

	= selectserver =		= selectserver =
	= sslutils =		= sslutils =

Stuart: Added placeholders for the other python files in the cissim directory

2021-10-11T15:48:20Z

Added placeholders for the other python files in the cissim directory

← Older revision		Revision as of 15:48, 11 October 2021
Line 153:		Line 153:

	At least, I think that's what it does - because I couldn't get [[#pdserve\|pdserve]] running, I had very little to test, so this is conjecture and glancery.		At least, I think that's what it does - because I couldn't get [[#pdserve\|pdserve]] running, I had very little to test, so this is conjecture and glancery.

			----
			I've just dumped all the 'pd' python files here for further processing.

			= pdacs =
			= pdconvertall =
			= pdconvertone =
			= pdconvert =
			= pddata =
			= pddump =
			= pdout =
			= pdparams =
			= pdproxy =
			= pdreadall =
			= pdreadoneedit =
			= pdreadone =
			= pdscreen =
			= pdserved =
			= pdservedt =
			= pdservep =
			= pdshow =
			= pdstub =
			= pdstubt =
			= pdstubtt =
			= pdtux =

			----
			And the non-'pd' python files:

			= certs =
			= checkport =
			= dci9n3rec =
			= extractodis =
			= fpcapprec =
			= getfieldoffset =
			= key =
			= loadninos =
			= logextract =
			= npsload =
			= paths =
			= ports =
			= selectserver =
			= sslutils =
			= temp =
			= teststub =
			= utils =
			= vmeutils =
			= w80construct =

Stuart: /* pdserve */ Spacing

2021-10-11T15:38:30Z

pdserve: Spacing

← Older revision		Revision as of 15:38, 11 October 2021
Line 128:		Line 128:
	print(s.server_version, end=' ')		print(s.server_version, end=' ')
	^		^

	SyntaxError: invalid syntax		SyntaxError: invalid syntax

Stuart: /* pdserve */ Added missing error for pdserve/python2

2021-10-11T15:38:08Z

pdserve: Added missing error for pdserve/python2

← Older revision		Revision as of 15:38, 11 October 2021
Line 127:		Line 127:
	File "../cissim/pdserve.py", line 68		File "../cissim/pdserve.py", line 68
	print(s.server_version, end=' ')		print(s.server_version, end=' ')
	^		^

			SyntaxError: invalid syntax

	In Python 3:		In Python 3:
	$ python ../cissim/pdserve.py pdserve.test.config 9927		$ python ../cissim/pdserve.py pdserve.test.config 9927

Stuart: Added a few more programs and their (loose) usages

2021-10-11T15:36:56Z

Added a few more programs and their (loose) usages

@@ Line 3: / Line 3: @@
 This page tries to exhaustively go through all of them. It fails. But it continues to try.
 = pdutils =
@@ Line 64: / Line 80: @@
   PD350/1151/RQST/R
 might have worked better, with a structured system, be it XML or JSON or YAML or whatever. Since I don't really understand which things would be better grouped together, I'll leave this as an idle thought for now.