The Dreaming - User contributions [en]

User:Stuart

2025-10-30T17:01:25Z

Stuart: Added holiday 2026 link

{{nav/stuart}}
My user page. Not much of anything on it at the moment... except...

== Marvel Puzzle Quest ==
* Strange Sights: Doom -> Maggia -> Hand
** Because there are more movers to the left of the above, and they get harder day after day.

== TODO ==
This space intentionally left blank.

== [[User:Stuart/Scratchpad|My Scratchpad]] ==
Which is primarily a work-in-progress pad on which I sketch out work in various states of not done.

== [[User:Stuart/Scratchpad II|My Second Scratchpad]] ==
For when the first scratchpad is in use / gets too full (like, er, now).

== [[:Category:Best Ofs|Best Ofs]] ==
A record of the tapes I made when I were a nipper, so I might recreate them and wallow in nostalgia and cringe at my appalling music taste.

== Global Bookmarks ==
* [[Holiday/2026]]
* [[User:Stuart/Honeymoon]]
* [[User:Stuart/Dad]]
* [[User:Stuart/Git Aliases]]
* [[User:Stuart/Public Keys]]
* [[User:Stuart/Leave Sheet]]
* [https://blog.habets.se/2011/07/OpenSSH-certificates.html OpenSSH Certificates]
* [[Waterdeep: Dragon Heist]]
* [[Jobs/FLAC Conversion]]
* [[Tech/Network]]
* [[Game Board/Print And Play]]
* [[User:Stuart/Meal Planning|''Meal Planning'']]
** [[User:Stuart/Meal Planning/2022-11-14|14/11/2022]]
* ''DWP Stuff''
** [[Noctam/DWP/ACS Test Harness|ACS Test Harness]]

== Additional command line options for EAC ==
LAME:
-V0 --add-id3v2 --pad-id3v2 --ta "%artist%" --tt "%title%" --tg "%genre%" --tl "%albumtitle%" --ty "%year%" --tn "%tracknr%/%numtracks%" %source% %dest%
(not keen on the track number output, though; I may tweak that)

Looking into the LAME options, you kinda have to hand-craft most of the tags (partially limited LAME implementation; partially limited ID3 implementation).
[https://hydrogenaud.io/index.php?topic=95917.0 This topic on HydrogenAudio] explains how to about it.

I also installed [https://sourceforge.net/projects/taginspector/ Tag Inspector] to have a look at the tags on ''dream'' - specifically Ayreon tags for multi-disc albums.
There were quite a few {{c|TXXX: DISCNUMBER}} type things mentioned on, er, "a web page". Which unfortunately, I can't find, but it shouldn't be too hard to piece together.
----
FLAC:
-6 -V -T "ARTIST=%artist%" -T "TITLE=%title%" -T "ALBUM=%albumtitle%" -T "DATE=%year%" -T "TRACKNUMBER=%tracknr%" -T "GENRE=%genre%" -T "COMMENT=%comment%" -T "BAND=%albuminterpret%" -T "ALBUMARTIST=%artist%" -T "COMPOSER=%composer%" %haslyrics%--tag-from-file=LYRICS="%lyricsfile%"%haslyrics% -T "DISCNUMBER=%cdnumber%" -T "TOTALDISCS=%totalcds%" -T "TOTALTRACKS=%numtracks%" %hascover%--picture="%coverfile%"%hascover% %source% -o %dest%

User:Liz

2025-09-28T16:30:46Z

Stuart: Added Holiday Link

* [[Holiday/2026]]

Bit of a cheat sheet:

= Heading One =

== Heading Two ==

=== Heading Three ===
(etc)

See? ''Now'' - '''it''' exists.
* And
* this
* is bullets

# And
# this
# is a numbered list

And this is
preformatted code (ie.
start with a space

To break a para in pre code,
Write a space and then press enter

[[Image:Destruction Of The Endless.jpg|thumb|200px]]

{|class="wikitable"
!Column One
!Column Two
!Column Three
|-
|Row 2 Cell 1
|Row 2 Cell 2
|Row 2 Cell 3
|-
|colspan="2"|Row 3 Cell 1-2
|Row 3 Cell 3
|}

Holiday/2026

2025-09-14T17:57:53Z

Stuart: Formatting

Interrail Global Pass Adult
7 Travel Days within 1 month
1st class
968 euro each

September best time to go.

=== Day 1 ===
Travel Day 1: 
* Lancaster -> London. Around 3 hrs.
* London to Brussels: Eurostar train from London St Pancras to Brussels-Midi. Around 2 hrs.
* Brussels to Cologne. Around 2 hours.

=== Day 1 - 2 (1 night) ===
Travel Day 2:
* Cologne to Hamburg, a journey of around 4 hours.

=== Days 2 - 5 (3 nights) ===
Travel Day 3:
* Hamburg to Copenhagen: From Hamburg, take the train to Copenhagen, the capital of Denmark. Around 5 hrs.

=== Days 5 - 8 (3 nights) ===
Travel Day 4:
* Copenhagen to Gothenburg: From Copenhagen, proceed by train to Gothenburg, Sweden. Around 3 hrs and 30 minutes.

=== Days 8 - 11 (3 nights) ===
Travel Day 5:
* Gothenburg to Oslo: Finally, catch a train from Gothenburg to Oslo, which takes approximately 3 hours and 40 minutes.

=== Days 11 - 14 (3 nights) ===
Travel Day 6:
* Oslo to Myrdal
* Flam Railway - 30% of with interrail (https://www.norwaysbest.com/en/things-to-do/the-flam-railway)
* Mydral to Bergen

=== Days 14 - 17 (3 nights) ===
Travel Day 7:
* Bergen to Oslo

=== Day 17+ ===
Fly Home

Notes.....

Bergen Card includes travel and discounts on the fjord cruise....plus the finicular

Could do an organised thing if we wanted - Round trip to Oslo

https://www.fjordtours.com/en/norway/tours/packages/unesco-geirangerfjord-and-norway-in-a-nutshell

Holiday/2026

2025-09-14T13:46:14Z

Stuart: Frist

This space intentionally left blank

User:Stuart

2025-06-26T18:27:52Z

Stuart: Puzzle Quest section added

{{nav/stuart}}
My user page. Not much of anything on it at the moment... except...

== Marvel Puzzle Quest ==
* Strange Sights: Doom -> Maggia -> Hand
** Because there are more movers to the left of the above, and they get harder day after day.

== TODO ==
This space intentionally left blank.

== [[User:Stuart/Scratchpad|My Scratchpad]] ==
Which is primarily a work-in-progress pad on which I sketch out work in various states of not done.

== [[User:Stuart/Scratchpad II|My Second Scratchpad]] ==
For when the first scratchpad is in use / gets too full (like, er, now).

== [[:Category:Best Ofs|Best Ofs]] ==
A record of the tapes I made when I were a nipper, so I might recreate them and wallow in nostalgia and cringe at my appalling music taste.

== Global Bookmarks ==
* [[User:Stuart/Honeymoon]]
* [[User:Stuart/Dad]]
* [[User:Stuart/Git Aliases]]
* [[User:Stuart/Public Keys]]
* [[User:Stuart/Leave Sheet]]
* [https://blog.habets.se/2011/07/OpenSSH-certificates.html OpenSSH Certificates]
* [[Waterdeep: Dragon Heist]]
* [[Jobs/FLAC Conversion]]
* [[Tech/Network]]
* [[Game Board/Print And Play]]
* [[User:Stuart/Meal Planning|''Meal Planning'']]
** [[User:Stuart/Meal Planning/2022-11-14|14/11/2022]]
* ''DWP Stuff''
** [[Noctam/DWP/ACS Test Harness|ACS Test Harness]]

== Additional command line options for EAC ==
LAME:
-V0 --add-id3v2 --pad-id3v2 --ta "%artist%" --tt "%title%" --tg "%genre%" --tl "%albumtitle%" --ty "%year%" --tn "%tracknr%/%numtracks%" %source% %dest%
(not keen on the track number output, though; I may tweak that)

Looking into the LAME options, you kinda have to hand-craft most of the tags (partially limited LAME implementation; partially limited ID3 implementation).
[https://hydrogenaud.io/index.php?topic=95917.0 This topic on HydrogenAudio] explains how to about it.

I also installed [https://sourceforge.net/projects/taginspector/ Tag Inspector] to have a look at the tags on ''dream'' - specifically Ayreon tags for multi-disc albums.
There were quite a few {{c|TXXX: DISCNUMBER}} type things mentioned on, er, "a web page". Which unfortunately, I can't find, but it shouldn't be too hard to piece together.
----
FLAC:
-6 -V -T "ARTIST=%artist%" -T "TITLE=%title%" -T "ALBUM=%albumtitle%" -T "DATE=%year%" -T "TRACKNUMBER=%tracknr%" -T "GENRE=%genre%" -T "COMMENT=%comment%" -T "BAND=%albuminterpret%" -T "ALBUMARTIST=%artist%" -T "COMPOSER=%composer%" %haslyrics%--tag-from-file=LYRICS="%lyricsfile%"%haslyrics% -T "DISCNUMBER=%cdnumber%" -T "TOTALDISCS=%totalcds%" -T "TOTALTRACKS=%numtracks%" %hascover%--picture="%coverfile%"%hascover% %source% -o %dest%

To-do

2022-11-15T10:46:02Z

Stuart: Moved to DONE

A page detailing the things that I need to do... I'll put something more formal together later.

Things I might have to do something with:

= CURRENT =

== Home Insurance ==
* https://account.policyexpert.co.uk/summary
* Add ring... value?
* Policy number: 35666001262083
* End date: 20/01/2023
* Cover level: Silver Home Insurance
* 0330 0600 601

= DONE =
== Atlas Alarms ==
* https://sites.google.com/atlasalarms.co.uk/atlasalarms-co-uk/home
* 01254 873232
* service@atlasalarms.co.uk
----
'''14/11/2022 11:00''' 
Dave, the surveyor, to call me back on my mobile to organise something.

'''15/11/2022 10:30''' 
Dave called back, he's coming round at 13:00 on Friday (18/11/2022).

== Booking meal in Grasmere ==
* Wed 23/11/2022
----
'''14/11/2022 12:45''' 
Called, left a message

'''14/11/2022 13:00''' 
They called back prompt-ish; booked for 23/11/2022 18:30

User:Stuart/Meal Planning/2022-11-14

2022-11-14T13:38:04Z

Stuart: WIP

== Rules ==
Allowed one each of:
* pasta
* rice
* potatoes
* bread

Exceptions allowed when eating out. S'a treat, innit?

= Diary =

== Monday ==
* Lunch: ''missed''
* Dinner: Ragu with **pasta**
** Leftovers

== Tuesday ==
* Lunch: Chicken, Vegetable & Pearl Barley soup
** Source: ''A Soup For Every Day''; Page: 334
* Dinner:

== Wednesday ==
* Lunch:
* Dinner:

== Thursday ==
* Lunch: Chicken & Chorizo Gumbo
** Source: ''A Soup For Every Day''; Page: 340
* Dinner: Out with Chris & Claire

== Friday ==
* Lunch:
* Dinner: Sausages braised in red wine, served with champ mash (**potatoes**)
** Source: ''Complete Cookery Course''; Page: 178

== Saturday ==
* Lunch:
* Dinner:

== Sunday ==
* Lunch: Apple, Cider salad with melted Camembert dressing
** Source: ''Winter Collection''; Page: 40
* Dinner:

= Ingredients =

= Addenda =
== For later consideration ==
* Camembert croquettes with fresh date and apple chutney
** Source: ''Winter Collection''; Page: 38/39

User:Stuart

2022-11-14T13:16:30Z

Stuart: /* Global Bookmarks */

{{nav/stuart}}
My user page. Not much of anything on it at the moment... except...

== TODO ==
This space intentionally left blank.

== [[User:Stuart/Scratchpad|My Scratchpad]] ==
Which is primarily a work-in-progress pad on which I sketch out work in various states of not done.

== [[User:Stuart/Scratchpad II|My Second Scratchpad]] ==
For when the first scratchpad is in use / gets too full (like, er, now).

== [[:Category:Best Ofs|Best Ofs]] ==
A record of the tapes I made when I were a nipper, so I might recreate them and wallow in nostalgia and cringe at my appalling music taste.

== Global Bookmarks ==
* [[User:Stuart/Honeymoon]]
* [[User:Stuart/Dad]]
* [[User:Stuart/Git Aliases]]
* [[User:Stuart/Public Keys]]
* [[User:Stuart/Leave Sheet]]
* [https://blog.habets.se/2011/07/OpenSSH-certificates.html OpenSSH Certificates]
* [[Waterdeep: Dragon Heist]]
* [[Jobs/FLAC Conversion]]
* [[Tech/Network]]
* [[Game Board/Print And Play]]
* [[User:Stuart/Meal Planning|''Meal Planning'']]
** [[User:Stuart/Meal Planning/2022-11-14|14/11/2022]]
* ''DWP Stuff''
** [[Noctam/DWP/ACS Test Harness|ACS Test Harness]]

== Additional command line options for EAC ==
LAME:
-V0 --add-id3v2 --pad-id3v2 --ta "%artist%" --tt "%title%" --tg "%genre%" --tl "%albumtitle%" --ty "%year%" --tn "%tracknr%/%numtracks%" %source% %dest%
(not keen on the track number output, though; I may tweak that)

Looking into the LAME options, you kinda have to hand-craft most of the tags (partially limited LAME implementation; partially limited ID3 implementation).
[https://hydrogenaud.io/index.php?topic=95917.0 This topic on HydrogenAudio] explains how to about it.

I also installed [https://sourceforge.net/projects/taginspector/ Tag Inspector] to have a look at the tags on ''dream'' - specifically Ayreon tags for multi-disc albums.
There were quite a few {{c|TXXX: DISCNUMBER}} type things mentioned on, er, "a web page". Which unfortunately, I can't find, but it shouldn't be too hard to piece together.
----
FLAC:
-6 -V -T "ARTIST=%artist%" -T "TITLE=%title%" -T "ALBUM=%albumtitle%" -T "DATE=%year%" -T "TRACKNUMBER=%tracknr%" -T "GENRE=%genre%" -T "COMMENT=%comment%" -T "BAND=%albuminterpret%" -T "ALBUMARTIST=%artist%" -T "COMPOSER=%composer%" %haslyrics%--tag-from-file=LYRICS="%lyricsfile%"%haslyrics% -T "DISCNUMBER=%cdnumber%" -T "TOTALDISCS=%totalcds%" -T "TOTALTRACKS=%numtracks%" %hascover%--picture="%coverfile%"%hascover% %source% -o %dest%

To-do

2022-11-14T12:52:01Z

Stuart: Added Grasmere meal

A page detailing the things that I need to do... I'll put something more formal together later.

Things I might have to do something with:

= CURRENT =
== Atlas Alarms ==
* https://sites.google.com/atlasalarms.co.uk/atlasalarms-co-uk/home
* 01254 873232
* service@atlasalarms.co.uk
----
'''11:00''' 
Dave, the surveyor, to call me back on my mobile to organise something.

== Home Insurance ==
* https://account.policyexpert.co.uk/summary
* Add ring... value?
* Policy number: 35666001262083
* End date: 20/01/2023
* Cover level: Silver Home Insurance
* 0330 0600 601

== Booking meal in Grasmere ==
* Wed 23/11/2022
----
'''12:45''' 
Called, left a message

To-do

2022-11-14T11:02:21Z

Stuart: Formatting

To-do

2022-11-14T11:01:20Z

Stuart: Cleared the old stuff - new stuff added.

A page detailing the things that I need to do... I'll put something more formal together later.

Things I might have to do something with:

= CURRENT =
== Atlas Alarms ==
* https://sites.google.com/atlasalarms.co.uk/atlasalarms-co-uk/home
* 01254 873232
* service@atlasalarms.co.uk
----
*11:00* 
Dave, the surveyor, to call me back on my mobile to organise something.

== Home Insurance ==
* https://account.policyexpert.co.uk/summary
* Add ring... value?
* Policy number: 35666001262083
* End date: 20/01/2023
* Cover level: Silver Home Insurance
* 0330 0600 601

User:Stuart/Dad

2022-09-20T06:12:33Z

Stuart: "journal entry" -> "something"

=== My Dad ===

My Dad was a teacher. 
He taught me to accept people as they are and not as I think they should be. 
He taught me to make plans but always be prepared for them to be thrown away at the first instance. 
He tried, a few times, to teach me ship stability, but that never took. 
He taught me the contentment you could achieve by sitting on the top of a mountain and enjoying being there. 
And the satisfaction you could achieve with a nice pint after the walk. 

My Dad was a student. 
He wanted to learn about everyone he met. 
He'd greet a waiter in a cafe with the same enthusiasm that he'd greet an old friend, and be genuinely interested to learn about them and their life in the same way. 
He was learning to speak Spanish, to play the accordion, forever learning new skills on the computer. 
He was always trying to improve, never just accepting that he was done and there was no point in changing any more. 

My Dad was a counsellor. 
He would listen, without judgement or impatience, to anyone who needed to talk. 
He would be the rock you could rely on when you were unsure of the ground you were standing on. 

My Dad was all of these things and more and I miss him. 

----

I'm going to finish with something he wrote after he completed his Camino:
<blockquote style="font-style: italic">
I am very very happy.

Words to describe the feeling in all its depth and richness are so difficult to find. 
Life it seems cannot stop giving me gift after gift. I am reminded of Meister Eckhart 
and his description of an overflowingness of Life that cannot stop giving. Also of that 
poetic piece from Davina of Findhorn.

My feelings are of gratitude and surprise, reassurance and encouragement, thankfulness 
for the rich blessings that I am given, the Friendships I am given, surprise at what 
comes 'out of the blue', trust in life, awareness of the transience of life and the 
willingness to embrace the joys I am given knowing that all my life experiences are 
transient except where we are all headed.
</blockquote>

----

User:Stuart/Dad

2022-09-19T21:41:34Z

Stuart: Removed the other quotes

=== My Dad ===

My Dad was a teacher. 
He taught me to accept people as they are and not as I think they should be. 
He taught me to make plans but always be prepared for them to be thrown away at the first instance. 
He tried, a few times, to teach me ship stability, but that never took. 
He taught me the contentment you could achieve by sitting on the top of a mountain and enjoying being there. 
And the satisfaction you could achieve with a nice pint after the walk. 

My Dad was a student. 
He wanted to learn about everyone he met. 
He'd greet a waiter in a cafe with the same enthusiasm that he'd greet an old friend, and be genuinely interested to learn about them and their life in the same way. 
He was learning to speak Spanish, to play the accordion, forever learning new skills on the computer. 
He was always trying to improve, never just accepting that he was done and there was no point in changing any more. 

My Dad was a counsellor. 
He would listen, without judgement or impatience, to anyone who needed to talk. 
He would be the rock you could rely on when you were unsure of the ground you were standing on. 

My Dad was all of these things and more and I miss him. 

----

I'm going to finish with a journal entry he wrote after he completed his Camino:
<blockquote style="font-style: italic">
I am very very happy.

Words to describe the feeling in all its depth and richness are so difficult to find. 
Life it seems cannot stop giving me gift after gift. I am reminded of Meister Eckhart 
and his description of an overflowingness of Life that cannot stop giving. Also of that 
poetic piece from Davina of Findhorn.

My feelings are of gratitude and surprise, reassurance and encouragement, thankfulness 
for the rich blessings that I am given, the Friendships I am given, surprise at what 
comes 'out of the blue', trust in life, awareness of the transience of life and the 
willingness to embrace the joys I am given knowing that all my life experiences are 
transient except where we are all headed.
</blockquote>

----

User:Stuart/Dad

2022-09-19T21:01:20Z

Stuart: And another finish

=== My Dad ===

My Dad was a teacher. 
He taught me to accept people as they are and not as I think they should be. 
He taught me to make plans but always be prepared for them to be thrown away at the first instance. 
He tried, a few times, to teach me ship stability, but that never took. 
He taught me the contentment you could achieve by sitting on the top of a mountain and enjoying being there. 
And the satisfaction you could achieve with a nice pint after the walk. 

My Dad was a student. 
He wanted to learn about everyone he met. 
He'd greet a waiter in a cafe with the same enthusiasm that he'd greet an old friend, and be genuinely interested to learn about them and their life in the same way. 
He was learning to speak Spanish, to play the accordion, forever learning new skills on the computer. 
He was always trying to improve, never just accepting that he was done and there was no point in changing any more. 

My Dad was a counsellor. 
He would listen, without judgement or impatience, to anyone who needed to talk. 
He would be the rock you could rely on when you were unsure of the ground you were standing on. 

My Dad was all of these things and more and I miss him. 

----

I'm going to finish with a short excerpt from his favourite book - 'The Prophet' by Kahlil Gibran:
<blockquote style="font-style: italic">
Say not "I have found the truth", but rather "I have found a truth". 
Say not "I have found the path of the soul." 
Say, rather, "I have met the soul walking on my path." 
For the soul walks on all paths.
</blockquote>

----

I'm going to finish with a short excerpt from his favourite book - 'The Prophet' by Kahlil Gibran:
<blockquote style="font-style: italic">
"You give but little when you give of your possessions.
It is when you give of yourself that you truly give."
</blockquote>

----

I'm going to finish with a journal entry he wrote after he completed his Camino:
<blockquote style="font-style: italic">
I am very very happy.

Words to describe the feeling in all its depth and richness are so difficult to find. 
Life it seems cannot stop giving me gift after gift. I am reminded of Meister Eckhart 
and his description of an overflowingness of Life that cannot stop giving. Also of that 
poetic piece from Davina of Findhorn.

My feelings are of gratitude and surprise, reassurance and encouragement, thankfulness 
for the rich blessings that I am given, the Friendships I am given, surprise at what 
comes 'out of the blue', trust in life, awareness of the transience of life and the 
willingness to embrace the joys I am given knowing that all my life experiences are 
transient except where we are all headed.
</blockquote>

----

User:Stuart/Dad

2022-09-19T20:52:23Z

Stuart: Formattings

=== My Dad ===

My Dad was a teacher. 
He taught me to accept people as they are and not as I think they should be. 
He taught me to make plans but always be prepared for them to be thrown away at the first instance. 
He tried, a few times, to teach me ship stability, but that never took. 
He taught me the contentment you could achieve by sitting on the top of a mountain and enjoying being there. 
And the satisfaction you could achieve with a nice pint after the walk. 

My Dad was a student. 
He wanted to learn about everyone he met. 
He'd greet a waiter in a cafe with the same enthusiasm that he'd greet an old friend, and be genuinely interested to learn about them and their life in the same way. 
He was learning to speak Spanish, to play the accordion, forever learning new skills on the computer. 
He was always trying to improve, never just accepting that he was done and there was no point in changing any more. 

My Dad was a counsellor. 
He would listen, without judgement or impatience, to anyone who needed to talk. 
He would be the rock you could rely on when you were unsure of the ground you were standing on. 

My Dad was all of these things and more and I miss him. 

----

I'm going to finish with a short excerpt from his favourite book - 'The Prophet' by Kahlil Gibran:
<blockquote style="font-style: italic">
Say not "I have found the truth", but rather "I have found a truth". 
Say not "I have found the path of the soul." 
Say, rather, "I have met the soul walking on my path." 
For the soul walks on all paths.
</blockquote>

----

I'm going to finish with a journal entry he wrote after he completed his Camino:
<blockquote style="font-style: italic">
I am very very happy.

Words to describe the feeling in all its depth and richness are so difficult to find. 
Life it seems cannot stop giving me gift after gift. I am reminded of Meister Eckhart 
and his description of an overflowingness of Life that cannot stop giving. Also of that 
poetic piece from Davina of Findhorn.

My feelings are of gratitude and surprise, reassurance and encouragement, thankfulness 
for the rich blessings that I am given, the Friendships I am given, surprise at what 
comes 'out of the blue', trust in life, awareness of the transience of life and the 
willingness to embrace the joys I am given knowing that all my life experiences are 
transient except where we are all headed.
</blockquote>

----

User:Stuart/Dad

2022-09-19T20:51:54Z

Stuart: Added journal entry - not sure which way to go yet.

=== My Dad ===

My Dad was a teacher. 
He taught me to accept people as they are and not as I think they should be. 
He taught me to make plans but always be prepared for them to be thrown away at the first instance. 
He tried, a few times, to teach me ship stability, but that never took. 
He taught me the contentment you could achieve by sitting on the top of a mountain and enjoying being there. 
And the satisfaction you could achieve with a nice pint after the walk. 

My Dad was a student. 
He wanted to learn about everyone he met. 
He'd greet a waiter in a cafe with the same enthusiasm that he'd greet an old friend, and be genuinely interested to learn about them and their life in the same way. 
He was learning to speak Spanish, to play the accordion, forever learning new skills on the computer. 
He was always trying to improve, never just accepting that he was done and there was no point in changing any more. 

My Dad was a counsellor. 
He would listen, without judgement or impatience, to anyone who needed to talk. 
He would be the rock you could rely on when you were unsure of the ground you were standing on. 

My Dad was all of these things and more and I miss him. 

----

I'm going to finish with a short excerpt from his favourite book - 'The Prophet' by Kahlil Gibran:
<blockquote style="font-style: italic">
Say not "I have found the truth", but rather "I have found a truth". 
Say not "I have found the path of the soul." 
Say, rather, "I have met the soul walking on my path." 
For the soul walks on all paths.
</blockquote>

----

I'm going to finish with a journal entry he wrote after he completed his Camino:
<blockquote style="font-style: italic">
I am very very happy.

Words to describe the feeling in all its depth and richness are so difficult to find.
Life it seems cannot stop giving me gift after gift. I am reminded of Meister Eckhart
and his description of an overflowingness of Life that cannot stop giving. Also of that
poetic piece from Davina of Findhorn.

My feelings are of gratitude and surprise, reassurance and encouragement, thankfulness
for the rich blessings that I am given, the Friendships I am given, surprise at what
comes 'out of the blue', trust in life, awareness of the transience of life and the
willingness to embrace the joys I am given knowing that all my life experiences are
transient except where we are all headed.
</blockquote>

----

User:Stuart/Dad

2022-09-19T20:45:57Z

Stuart: Tidy up

User:Stuart/Dad

2022-09-19T20:43:25Z

Stuart: Created page with "My Dad was a teacher. He taught me to accept people as they are and not as I think they should be. He taught me to make plans but always be prepared for them to be thr..."

My Dad was a teacher. 
He taught me to accept people as they are and not as I think they should be. 
He taught me to make plans but always be prepared for them to be thrown away at the first instance. 
He tried, a few times, to teach me ship stability, but that never took. 
He taught me the contentment you could achieve by sitting on the top of a mountain and enjoying being there. 
And the satisfaction you could achieve with a nice pint after the walk. 

My Dad was a student. 
He wanted to learn about everyone he met. 
He'd greet a waiter in a cafe with the same enthusiasm that he'd greet an old friend, and be genuinely interested to learn about them and their life in the same way. 
He was learning to speak Spanish, to play the accordion, forever learning new skills on the computer. 
He was always trying to improve, never just accepting that he was done and there was no point in changing any more. 

My Dad was a counsellor. 
He would listen, without judgement or impatience, to anyone who needed to talk. 
He would be the rock you could rely on when you were unsure of the ground you were standing on. 

My Dad was all of these things and more.
I'm going to finish with a short excerpt from his favourite book - 'The Prophet' by Kahlil Gibran.
<blockquote>
Say not "I have found the truth", but rather "I have found a truth". 
Say not "I have found the path of the soul." 
Say, rather, "I have met the soul walking on my path." 
For the soul walks on all paths.

</blockquote>

User:Stuart

2022-09-19T19:32:22Z

Stuart: Added a Dad link

{{nav/stuart}}
My user page. Not much of anything on it at the moment... except...

== TODO ==
This space intentionally left blank.

== [[User:Stuart/Scratchpad|My Scratchpad]] ==
Which is primarily a work-in-progress pad on which I sketch out work in various states of not done.

== [[User:Stuart/Scratchpad II|My Second Scratchpad]] ==
For when the first scratchpad is in use / gets too full (like, er, now).

== [[:Category:Best Ofs|Best Ofs]] ==
A record of the tapes I made when I were a nipper, so I might recreate them and wallow in nostalgia and cringe at my appalling music taste.

== Global Bookmarks ==
* [[User:Stuart/Honeymoon]]
* [[User:Stuart/Dad]]
* [[User:Stuart/Git Aliases]]
* [[User:Stuart/Public Keys]]
* [[User:Stuart/Leave Sheet]]
* [https://blog.habets.se/2011/07/OpenSSH-certificates.html OpenSSH Certificates]
* [[Waterdeep: Dragon Heist]]
* [[Jobs/FLAC Conversion]]
* [[Tech/Network]]
* [[Game Board/Print And Play]]
* ''DWP Stuff''
** [[Noctam/DWP/ACS Test Harness|ACS Test Harness]]

== Additional command line options for EAC ==
LAME:
-V0 --add-id3v2 --pad-id3v2 --ta "%artist%" --tt "%title%" --tg "%genre%" --tl "%albumtitle%" --ty "%year%" --tn "%tracknr%/%numtracks%" %source% %dest%
(not keen on the track number output, though; I may tweak that)

Looking into the LAME options, you kinda have to hand-craft most of the tags (partially limited LAME implementation; partially limited ID3 implementation).
[https://hydrogenaud.io/index.php?topic=95917.0 This topic on HydrogenAudio] explains how to about it.

I also installed [https://sourceforge.net/projects/taginspector/ Tag Inspector] to have a look at the tags on ''dream'' - specifically Ayreon tags for multi-disc albums.
There were quite a few {{c|TXXX: DISCNUMBER}} type things mentioned on, er, "a web page". Which unfortunately, I can't find, but it shouldn't be too hard to piece together.
----
FLAC:
-6 -V -T "ARTIST=%artist%" -T "TITLE=%title%" -T "ALBUM=%albumtitle%" -T "DATE=%year%" -T "TRACKNUMBER=%tracknr%" -T "GENRE=%genre%" -T "COMMENT=%comment%" -T "BAND=%albuminterpret%" -T "ALBUMARTIST=%artist%" -T "COMPOSER=%composer%" %haslyrics%--tag-from-file=LYRICS="%lyricsfile%"%haslyrics% -T "DISCNUMBER=%cdnumber%" -T "TOTALDISCS=%totalcds%" -T "TOTALTRACKS=%numtracks%" %hascover%--picture="%coverfile%"%hascover% %source% -o %dest%

User:Stuart/Honeymoon

2022-06-07T17:58:49Z

Stuart: Added The Ardross

Options for holiday cottage for honeymoon fun:

== Cornwall ==
* [https://www.holidaycottages.co.uk/cottage/45739-kennack-heights--kennack-sands?n=7&sd=05092022 Kennack Heights]

== Highlands ==
* [https://www.cottages-and-castles.co.uk/cottages/the-lovat-mackenzie?sd=10092022 Lovat, near Inverness]
* [https://www.cottages-and-castles.co.uk/cottages/the-ardross-residence?sd=10092022 The Ardross Residence, ''actually'' Inverness]

== Something to consider for lads walking holiday ==
* [https://www.cottages-and-castles.co.uk/cottages/dhivach-lodge--drumnadrochit?sd=09092022 Dhivach Lodge - Drumnadrochit]

User:Stuart/Honeymoon

2022-06-07T17:53:05Z

Stuart: Added potential lads lodge in Scotland

Options for holiday cottage for honeymoon fun:

== Cornwall ==
* [https://www.holidaycottages.co.uk/cottage/45739-kennack-heights--kennack-sands?n=7&sd=05092022 Kennack Heights]

== Highlands ==
* [https://www.cottages-and-castles.co.uk/cottages/the-lovat-mackenzie?sd=10092022 Lovat, near Inverness]

== Something to consider for lads walking holiday ==
* [https://www.cottages-and-castles.co.uk/cottages/dhivach-lodge--drumnadrochit?sd=09092022 Dhivach Lodge - Drumnadrochit]

User:Stuart/Honeymoon

2022-06-07T17:46:48Z

Stuart: Added highlands section

User:Stuart/Honeymoon

2022-06-07T16:45:42Z

Stuart: First cut - Kennack Heights

Options for holiday cottage for honeymoon fun:

== Cornwall ==
* [https://www.holidaycottages.co.uk/cottage/45739-kennack-heights--kennack-sands?n=7&sd=05092022 Kennack Heights]

User:Stuart

2022-06-07T16:44:35Z

Stuart: Added Honeymoon page

{{nav/stuart}}
My user page. Not much of anything on it at the moment... except...

== TODO ==
This space intentionally left blank.

== [[User:Stuart/Scratchpad|My Scratchpad]] ==
Which is primarily a work-in-progress pad on which I sketch out work in various states of not done.

== [[User:Stuart/Scratchpad II|My Second Scratchpad]] ==
For when the first scratchpad is in use / gets too full (like, er, now).

== [[:Category:Best Ofs|Best Ofs]] ==
A record of the tapes I made when I were a nipper, so I might recreate them and wallow in nostalgia and cringe at my appalling music taste.

== Global Bookmarks ==
* [[User:Stuart/Honeymoon]]
* [[User:Stuart/Git Aliases]]
* [[User:Stuart/Public Keys]]
* [[User:Stuart/Leave Sheet]]
* [https://blog.habets.se/2011/07/OpenSSH-certificates.html OpenSSH Certificates]
* [[Waterdeep: Dragon Heist]]
* [[Jobs/FLAC Conversion]]
* [[Tech/Network]]
* [[Game Board/Print And Play]]
* ''DWP Stuff''
** [[Noctam/DWP/ACS Test Harness|ACS Test Harness]]

== Additional command line options for EAC ==
LAME:
-V0 --add-id3v2 --pad-id3v2 --ta "%artist%" --tt "%title%" --tg "%genre%" --tl "%albumtitle%" --ty "%year%" --tn "%tracknr%/%numtracks%" %source% %dest%
(not keen on the track number output, though; I may tweak that)

Looking into the LAME options, you kinda have to hand-craft most of the tags (partially limited LAME implementation; partially limited ID3 implementation).
[https://hydrogenaud.io/index.php?topic=95917.0 This topic on HydrogenAudio] explains how to about it.

I also installed [https://sourceforge.net/projects/taginspector/ Tag Inspector] to have a look at the tags on ''dream'' - specifically Ayreon tags for multi-disc albums.
There were quite a few {{c|TXXX: DISCNUMBER}} type things mentioned on, er, "a web page". Which unfortunately, I can't find, but it shouldn't be too hard to piece together.
----
FLAC:
-6 -V -T "ARTIST=%artist%" -T "TITLE=%title%" -T "ALBUM=%albumtitle%" -T "DATE=%year%" -T "TRACKNUMBER=%tracknr%" -T "GENRE=%genre%" -T "COMMENT=%comment%" -T "BAND=%albuminterpret%" -T "ALBUMARTIST=%artist%" -T "COMPOSER=%composer%" %haslyrics%--tag-from-file=LYRICS="%lyricsfile%"%haslyrics% -T "DISCNUMBER=%cdnumber%" -T "TOTALDISCS=%totalcds%" -T "TOTALTRACKS=%numtracks%" %hascover%--picture="%coverfile%"%hascover% %source% -o %dest%

Game Board/Print And Play

2022-05-23T11:24:17Z

Stuart: Full howto plus ingredients added

== Card Printing ==
For reasonable feel cards:
=== Martin Gonzalvez ===
* [https://www.youtube.com/watch?v=00h0KFbkViA How to make print and play cards]
* [https://www.youtube.com/watch?v=jSnM6j9Nqh8 Print and play cards that riffle shuffle]

=== Rachel Bruner ===
* [https://www.youtube.com/watch?v=geJGoGsSUxE Print and play cards made like playing cards]
* [https://www.youtube.com/watch?v=DgNJmAkO1_M How To Make Game Cards that Shuffle - Print and Play Tutorial]

=== Howto ===
Ingredients:
* 90-100 gsm linen paper (e.g. [https://www.amazon.co.uk/Southworth-Linen-Business-Pounds-P564CK/dp/B0087D7ZAU Southworth 25% 90gsm Cotton Paper]
* 3mm laminating pouches
* Acrylic sealer (e.g. [https://www.amazon.com/Mod-Podge-Acrylic-12-Ounce-1469/dp/B003VY9DNM/?th=1 Mod Podge Clear Acrylic Matte Sealer]
* Spray glue

Briefly:
# Print, single-sided; front down the left, back down the right
# Fold the paper such that the front and back match up, unfold again ready for the core laminate sheet
# Spray the glue over the back of the paper
# Insert one sheet of the laminating pouch (tear the sheets apart for this) into the fold and press the glued paper onto it - it must line up
# Use the other side of the laminate sheet for another 4 cards done the same way as above
# Trim off all excess laminate - you want just paper showing, no clear laminate parts
# Put it through the laminator
# Cut and corner each card

This will work great for the Arkham Horror like stuff, especially once sleeved.

User:Stuart

2022-05-23T11:08:02Z

Stuart: Added Print And Play; Removed obsolete TODOs.

{{nav/stuart}}
My user page. Not much of anything on it at the moment... except...

== TODO ==
This space intentionally left blank.

== [[User:Stuart/Scratchpad|My Scratchpad]] ==
Which is primarily a work-in-progress pad on which I sketch out work in various states of not done.

== [[User:Stuart/Scratchpad II|My Second Scratchpad]] ==
For when the first scratchpad is in use / gets too full (like, er, now).

== [[:Category:Best Ofs|Best Ofs]] ==
A record of the tapes I made when I were a nipper, so I might recreate them and wallow in nostalgia and cringe at my appalling music taste.

== Global Bookmarks ==
* [[User:Stuart/Git Aliases]]
* [[User:Stuart/Public Keys]]
* [[User:Stuart/Leave Sheet]]
* [https://blog.habets.se/2011/07/OpenSSH-certificates.html OpenSSH Certificates]
* [[Waterdeep: Dragon Heist]]
* [[Jobs/FLAC Conversion]]
* [[Tech/Network]]
* [[Game Board/Print And Play]]
* ''DWP Stuff''
** [[Noctam/DWP/ACS Test Harness|ACS Test Harness]]

== Additional command line options for EAC ==
LAME:
-V0 --add-id3v2 --pad-id3v2 --ta "%artist%" --tt "%title%" --tg "%genre%" --tl "%albumtitle%" --ty "%year%" --tn "%tracknr%/%numtracks%" %source% %dest%
(not keen on the track number output, though; I may tweak that)

Looking into the LAME options, you kinda have to hand-craft most of the tags (partially limited LAME implementation; partially limited ID3 implementation).
[https://hydrogenaud.io/index.php?topic=95917.0 This topic on HydrogenAudio] explains how to about it.

I also installed [https://sourceforge.net/projects/taginspector/ Tag Inspector] to have a look at the tags on ''dream'' - specifically Ayreon tags for multi-disc albums.
There were quite a few {{c|TXXX: DISCNUMBER}} type things mentioned on, er, "a web page". Which unfortunately, I can't find, but it shouldn't be too hard to piece together.
----
FLAC:
-6 -V -T "ARTIST=%artist%" -T "TITLE=%title%" -T "ALBUM=%albumtitle%" -T "DATE=%year%" -T "TRACKNUMBER=%tracknr%" -T "GENRE=%genre%" -T "COMMENT=%comment%" -T "BAND=%albuminterpret%" -T "ALBUMARTIST=%artist%" -T "COMPOSER=%composer%" %haslyrics%--tag-from-file=LYRICS="%lyricsfile%"%haslyrics% -T "DISCNUMBER=%cdnumber%" -T "TOTALDISCS=%totalcds%" -T "TOTALTRACKS=%numtracks%" %hascover%--picture="%coverfile%"%hascover% %source% -o %dest%

File:New-tube-map.jpg

2022-05-20T14:57:03Z

Stuart: Stuart uploaded a new version of File:New-tube-map.jpg

Tube map, including Elizabeth line

Tube

2022-05-20T14:56:31Z

Stuart: Just link to the image. Far nicer

[[Media:New-tube-map.jpg|Tube Map]]

Tube

2022-05-20T14:49:01Z

Stuart: Added tube map

[[File:New-tube-map.jpg]]

File:New-tube-map.jpg

2022-05-20T14:48:07Z

Stuart: Tube map, including Elizabeth line

Tube map, including Elizabeth line

User:Stuart

2022-03-20T09:32:14Z

Stuart: /* 18/03/2022 */ Library done

{{nav/stuart}}
My user page. Not much of anything on it at the moment... except...

== TODO ==
=== 18/03/2022 ===
* Dukes:
** Cancel standing order (joint account? yes, and not due til 14/11, so no great rush)
** Phone/call/go round and organise new friends payments
* <s>Homeserve:</s>
** <s>Call them up and see why a 50% rise in price; maybe cancel. Probably cancel.</s>
* <s>Library books</s>
** <s>not due til 24/03, but all read now.</s>
* Co-op Bank
** <s>Look into / setup new security requirements</s>
*** ''Had a look - this can wait; they ain't ready, and 1* reviews from last year, getting no better. Co-op really are crap.''
** <s>2 invoices to Riverside to pay; see Accounts below.</s>
* Accounts
** <s>2 invoices to put into Sage</s>
** <s>Both invoices need paying; See Co-op Bank above</s>
** Company accounts for last year to sign and return
** Bring bank transactions up to date
*** Maybe write a little program to convert co-op CSV to sage CSV
* Edinburgh
** Look for somewhere to eat on Sunday evening
** Maybe Sunday afternoon too
** Pick up tickets from station

== [[User:Stuart/Scratchpad|My Scratchpad]] ==
Which is primarily a work-in-progress pad on which I sketch out work in various states of not done.

== [[User:Stuart/Scratchpad II|My Second Scratchpad]] ==
For when the first scratchpad is in use / gets too full (like, er, now).

== [[:Category:Best Ofs|Best Ofs]] ==
A record of the tapes I made when I were a nipper, so I might recreate them and wallow in nostalgia and cringe at my appalling music taste.

== Global Bookmarks ==
* [[User:Stuart/Git Aliases]]
* [[User:Stuart/Public Keys]]
* [[User:Stuart/Leave Sheet]]
* [https://blog.habets.se/2011/07/OpenSSH-certificates.html OpenSSH Certificates]
* [[Waterdeep: Dragon Heist]]
* [[Jobs/FLAC Conversion]]
* [[Tech/Network]]
* ''DWP Stuff''
** [[Noctam/DWP/ACS Test Harness|ACS Test Harness]]

== Additional command line options for EAC ==
LAME:
-V0 --add-id3v2 --pad-id3v2 --ta "%artist%" --tt "%title%" --tg "%genre%" --tl "%albumtitle%" --ty "%year%" --tn "%tracknr%/%numtracks%" %source% %dest%
(not keen on the track number output, though; I may tweak that)

Looking into the LAME options, you kinda have to hand-craft most of the tags (partially limited LAME implementation; partially limited ID3 implementation).
[https://hydrogenaud.io/index.php?topic=95917.0 This topic on HydrogenAudio] explains how to about it.

I also installed [https://sourceforge.net/projects/taginspector/ Tag Inspector] to have a look at the tags on ''dream'' - specifically Ayreon tags for multi-disc albums.
There were quite a few {{c|TXXX: DISCNUMBER}} type things mentioned on, er, "a web page". Which unfortunately, I can't find, but it shouldn't be too hard to piece together.
----
FLAC:
-6 -V -T "ARTIST=%artist%" -T "TITLE=%title%" -T "ALBUM=%albumtitle%" -T "DATE=%year%" -T "TRACKNUMBER=%tracknr%" -T "GENRE=%genre%" -T "COMMENT=%comment%" -T "BAND=%albuminterpret%" -T "ALBUMARTIST=%artist%" -T "COMPOSER=%composer%" %haslyrics%--tag-from-file=LYRICS="%lyricsfile%"%haslyrics% -T "DISCNUMBER=%cdnumber%" -T "TOTALDISCS=%totalcds%" -T "TOTALTRACKS=%numtracks%" %hascover%--picture="%coverfile%"%hascover% %source% -o %dest%

User:Stuart

2022-03-18T13:32:58Z

Stuart: /* 18/03/2022 */

{{nav/stuart}}
My user page. Not much of anything on it at the moment... except...

== TODO ==
=== 18/03/2022 ===
* Dukes:
** Cancel standing order (joint account? yes, and not due til 14/11, so no great rush)
** Phone/call/go round and organise new friends payments
* <s>Homeserve:</s>
** <s>Call them up and see why a 50% rise in price; maybe cancel. Probably cancel.</s>
* Library books
** not due til 24/03, but all read now.
* Co-op Bank
** <s>Look into / setup new security requirements</s>
*** ''Had a look - this can wait; they ain't ready, and 1* reviews from last year, getting no better. Co-op really are crap.''
** <s>2 invoices to Riverside to pay; see Accounts below.</s>
* Accounts
** <s>2 invoices to put into Sage</s>
** <s>Both invoices need paying; See Co-op Bank above</s>
** Company accounts for last year to sign and return
** Bring bank transactions up to date
*** Maybe write a little program to convert co-op CSV to sage CSV
* Edinburgh
** Look for somewhere to eat on Sunday evening
** Maybe Sunday afternoon too
** Pick up tickets from station

== [[User:Stuart/Scratchpad|My Scratchpad]] ==
Which is primarily a work-in-progress pad on which I sketch out work in various states of not done.

== [[User:Stuart/Scratchpad II|My Second Scratchpad]] ==
For when the first scratchpad is in use / gets too full (like, er, now).

== [[:Category:Best Ofs|Best Ofs]] ==
A record of the tapes I made when I were a nipper, so I might recreate them and wallow in nostalgia and cringe at my appalling music taste.

== Global Bookmarks ==
* [[User:Stuart/Git Aliases]]
* [[User:Stuart/Public Keys]]
* [[User:Stuart/Leave Sheet]]
* [https://blog.habets.se/2011/07/OpenSSH-certificates.html OpenSSH Certificates]
* [[Waterdeep: Dragon Heist]]
* [[Jobs/FLAC Conversion]]
* [[Tech/Network]]
* ''DWP Stuff''
** [[Noctam/DWP/ACS Test Harness|ACS Test Harness]]

== Additional command line options for EAC ==
LAME:
-V0 --add-id3v2 --pad-id3v2 --ta "%artist%" --tt "%title%" --tg "%genre%" --tl "%albumtitle%" --ty "%year%" --tn "%tracknr%/%numtracks%" %source% %dest%
(not keen on the track number output, though; I may tweak that)

Looking into the LAME options, you kinda have to hand-craft most of the tags (partially limited LAME implementation; partially limited ID3 implementation).
[https://hydrogenaud.io/index.php?topic=95917.0 This topic on HydrogenAudio] explains how to about it.

I also installed [https://sourceforge.net/projects/taginspector/ Tag Inspector] to have a look at the tags on ''dream'' - specifically Ayreon tags for multi-disc albums.
There were quite a few {{c|TXXX: DISCNUMBER}} type things mentioned on, er, "a web page". Which unfortunately, I can't find, but it shouldn't be too hard to piece together.
----
FLAC:
-6 -V -T "ARTIST=%artist%" -T "TITLE=%title%" -T "ALBUM=%albumtitle%" -T "DATE=%year%" -T "TRACKNUMBER=%tracknr%" -T "GENRE=%genre%" -T "COMMENT=%comment%" -T "BAND=%albuminterpret%" -T "ALBUMARTIST=%artist%" -T "COMPOSER=%composer%" %haslyrics%--tag-from-file=LYRICS="%lyricsfile%"%haslyrics% -T "DISCNUMBER=%cdnumber%" -T "TOTALDISCS=%totalcds%" -T "TOTALTRACKS=%numtracks%" %hascover%--picture="%coverfile%"%hascover% %source% -o %dest%

User:Stuart

2022-03-18T13:14:46Z

Stuart: /* 18/03/2022 */

{{nav/stuart}}
My user page. Not much of anything on it at the moment... except...

== TODO ==
=== 18/03/2022 ===
* Dukes:
** Cancel standing order (joint account? yes, and not due til 14/11, so no great rush)
** Phone/call/go round and organise new friends payments
* <s>Homeserve:</s>
** <s>Call them up and see why a 50% rise in price; maybe cancel. Probably cancel.</s>
* Library books
** not due til 24/03, but all read now.
* Co-op Bank
** Look into / setup new security requirements
** <s>2 invoices to Riverside to pay; see Accounts below.</s>
* Accounts
** <s>2 invoices to put into Sage</s>
** <s>Both invoices need paying; See Co-op Bank above</s>
** Company accounts for last year to sign and return
** Bring bank transactions up to date
*** Maybe write a little program to convert co-op CSV to sage CSV
* Edinburgh
** Look for somewhere to eat on Sunday evening
** Maybe Sunday afternoon too
** Pick up tickets from station

== [[User:Stuart/Scratchpad|My Scratchpad]] ==
Which is primarily a work-in-progress pad on which I sketch out work in various states of not done.

== [[User:Stuart/Scratchpad II|My Second Scratchpad]] ==
For when the first scratchpad is in use / gets too full (like, er, now).

== [[:Category:Best Ofs|Best Ofs]] ==
A record of the tapes I made when I were a nipper, so I might recreate them and wallow in nostalgia and cringe at my appalling music taste.

== Global Bookmarks ==
* [[User:Stuart/Git Aliases]]
* [[User:Stuart/Public Keys]]
* [[User:Stuart/Leave Sheet]]
* [https://blog.habets.se/2011/07/OpenSSH-certificates.html OpenSSH Certificates]
* [[Waterdeep: Dragon Heist]]
* [[Jobs/FLAC Conversion]]
* [[Tech/Network]]
* ''DWP Stuff''
** [[Noctam/DWP/ACS Test Harness|ACS Test Harness]]

== Additional command line options for EAC ==
LAME:
-V0 --add-id3v2 --pad-id3v2 --ta "%artist%" --tt "%title%" --tg "%genre%" --tl "%albumtitle%" --ty "%year%" --tn "%tracknr%/%numtracks%" %source% %dest%
(not keen on the track number output, though; I may tweak that)

Looking into the LAME options, you kinda have to hand-craft most of the tags (partially limited LAME implementation; partially limited ID3 implementation).
[https://hydrogenaud.io/index.php?topic=95917.0 This topic on HydrogenAudio] explains how to about it.

I also installed [https://sourceforge.net/projects/taginspector/ Tag Inspector] to have a look at the tags on ''dream'' - specifically Ayreon tags for multi-disc albums.
There were quite a few {{c|TXXX: DISCNUMBER}} type things mentioned on, er, "a web page". Which unfortunately, I can't find, but it shouldn't be too hard to piece together.
----
FLAC:
-6 -V -T "ARTIST=%artist%" -T "TITLE=%title%" -T "ALBUM=%albumtitle%" -T "DATE=%year%" -T "TRACKNUMBER=%tracknr%" -T "GENRE=%genre%" -T "COMMENT=%comment%" -T "BAND=%albuminterpret%" -T "ALBUMARTIST=%artist%" -T "COMPOSER=%composer%" %haslyrics%--tag-from-file=LYRICS="%lyricsfile%"%haslyrics% -T "DISCNUMBER=%cdnumber%" -T "TOTALDISCS=%totalcds%" -T "TOTALTRACKS=%numtracks%" %hascover%--picture="%coverfile%"%hascover% %source% -o %dest%

User:Stuart

2022-03-18T13:04:24Z

Stuart: /* 18/03/2022 */

{{nav/stuart}}
My user page. Not much of anything on it at the moment... except...

== TODO ==
=== 18/03/2022 ===
* Dukes:
** Cancel standing order (joint account? yes, and not due til 14/11, so no great rush)
** Phone/call/go round and organise new friends payments
* <s>Homeserve:</s>
** <s>Call them up and see why a 50% rise in price; maybe cancel. Probably cancel.</s>
* Library books
** not due til 24/03, but all read now.
* Co-op Bank
** Look into / setup new security requirements
** 2 invoices to Riverside to pay; see Accounts below.
* Accounts
** <s>2 invoices to put into Sage</s>
** <s>Both invoices need paying; See Co-op Bank above</s>
** Company accounts for last year to sign and return
** Bring bank transactions up to date
*** Maybe write a little program to convert co-op CSV to sage CSV
* Edinburgh
** Look for somewhere to eat on Sunday evening
** Maybe Sunday afternoon too
** Pick up tickets from station

== [[User:Stuart/Scratchpad|My Scratchpad]] ==
Which is primarily a work-in-progress pad on which I sketch out work in various states of not done.

== [[User:Stuart/Scratchpad II|My Second Scratchpad]] ==
For when the first scratchpad is in use / gets too full (like, er, now).

== [[:Category:Best Ofs|Best Ofs]] ==
A record of the tapes I made when I were a nipper, so I might recreate them and wallow in nostalgia and cringe at my appalling music taste.

== Global Bookmarks ==
* [[User:Stuart/Git Aliases]]
* [[User:Stuart/Public Keys]]
* [[User:Stuart/Leave Sheet]]
* [https://blog.habets.se/2011/07/OpenSSH-certificates.html OpenSSH Certificates]
* [[Waterdeep: Dragon Heist]]
* [[Jobs/FLAC Conversion]]
* [[Tech/Network]]
* ''DWP Stuff''
** [[Noctam/DWP/ACS Test Harness|ACS Test Harness]]

== Additional command line options for EAC ==
LAME:
-V0 --add-id3v2 --pad-id3v2 --ta "%artist%" --tt "%title%" --tg "%genre%" --tl "%albumtitle%" --ty "%year%" --tn "%tracknr%/%numtracks%" %source% %dest%
(not keen on the track number output, though; I may tweak that)

Looking into the LAME options, you kinda have to hand-craft most of the tags (partially limited LAME implementation; partially limited ID3 implementation).
[https://hydrogenaud.io/index.php?topic=95917.0 This topic on HydrogenAudio] explains how to about it.

I also installed [https://sourceforge.net/projects/taginspector/ Tag Inspector] to have a look at the tags on ''dream'' - specifically Ayreon tags for multi-disc albums.
There were quite a few {{c|TXXX: DISCNUMBER}} type things mentioned on, er, "a web page". Which unfortunately, I can't find, but it shouldn't be too hard to piece together.
----
FLAC:
-6 -V -T "ARTIST=%artist%" -T "TITLE=%title%" -T "ALBUM=%albumtitle%" -T "DATE=%year%" -T "TRACKNUMBER=%tracknr%" -T "GENRE=%genre%" -T "COMMENT=%comment%" -T "BAND=%albuminterpret%" -T "ALBUMARTIST=%artist%" -T "COMPOSER=%composer%" %haslyrics%--tag-from-file=LYRICS="%lyricsfile%"%haslyrics% -T "DISCNUMBER=%cdnumber%" -T "TOTALDISCS=%totalcds%" -T "TOTALTRACKS=%numtracks%" %hascover%--picture="%coverfile%"%hascover% %source% -o %dest%

User:Stuart

2022-03-18T13:03:34Z

Stuart: /* 18/03/2022 */

{{nav/stuart}}
My user page. Not much of anything on it at the moment... except...

== TODO ==
=== 18/03/2022 ===
* Dukes:
** Cancel standing order (joint account? yes, and not due til 14/11, so no great rush)
** Phone/call/go round and organise new friends payments
* <s>Homeserve:</s>
** <s>Call them up and see why a 50% rise in price; maybe cancel. Probably cancel.</s>
* Library books
** not due til 24/03, but all read now.
* Co-op Bank
** Look into / setup new security requirements
** 2 invoices to Riverside to pay; see Accounts below.
* Accounts
** <s>2 invoices to put into Sage</s>
** Both invoices need paying; See Co-op Bank above
** Company accounts for last year to sign and return
* Edinburgh
** Look for somewhere to eat on Sunday evening
** Maybe Sunday afternoon too
** Pick up tickets from station

== [[User:Stuart/Scratchpad|My Scratchpad]] ==
Which is primarily a work-in-progress pad on which I sketch out work in various states of not done.

== [[User:Stuart/Scratchpad II|My Second Scratchpad]] ==
For when the first scratchpad is in use / gets too full (like, er, now).

== [[:Category:Best Ofs|Best Ofs]] ==
A record of the tapes I made when I were a nipper, so I might recreate them and wallow in nostalgia and cringe at my appalling music taste.

== Global Bookmarks ==
* [[User:Stuart/Git Aliases]]
* [[User:Stuart/Public Keys]]
* [[User:Stuart/Leave Sheet]]
* [https://blog.habets.se/2011/07/OpenSSH-certificates.html OpenSSH Certificates]
* [[Waterdeep: Dragon Heist]]
* [[Jobs/FLAC Conversion]]
* [[Tech/Network]]
* ''DWP Stuff''
** [[Noctam/DWP/ACS Test Harness|ACS Test Harness]]

== Additional command line options for EAC ==
LAME:
-V0 --add-id3v2 --pad-id3v2 --ta "%artist%" --tt "%title%" --tg "%genre%" --tl "%albumtitle%" --ty "%year%" --tn "%tracknr%/%numtracks%" %source% %dest%
(not keen on the track number output, though; I may tweak that)

Looking into the LAME options, you kinda have to hand-craft most of the tags (partially limited LAME implementation; partially limited ID3 implementation).
[https://hydrogenaud.io/index.php?topic=95917.0 This topic on HydrogenAudio] explains how to about it.

I also installed [https://sourceforge.net/projects/taginspector/ Tag Inspector] to have a look at the tags on ''dream'' - specifically Ayreon tags for multi-disc albums.
There were quite a few {{c|TXXX: DISCNUMBER}} type things mentioned on, er, "a web page". Which unfortunately, I can't find, but it shouldn't be too hard to piece together.
----
FLAC:
-6 -V -T "ARTIST=%artist%" -T "TITLE=%title%" -T "ALBUM=%albumtitle%" -T "DATE=%year%" -T "TRACKNUMBER=%tracknr%" -T "GENRE=%genre%" -T "COMMENT=%comment%" -T "BAND=%albuminterpret%" -T "ALBUMARTIST=%artist%" -T "COMPOSER=%composer%" %haslyrics%--tag-from-file=LYRICS="%lyricsfile%"%haslyrics% -T "DISCNUMBER=%cdnumber%" -T "TOTALDISCS=%totalcds%" -T "TOTALTRACKS=%numtracks%" %hascover%--picture="%coverfile%"%hascover% %source% -o %dest%

User:Stuart

2022-03-18T12:09:02Z

Stuart: /* 18/03/2022 */ Homeserve done

{{nav/stuart}}
My user page. Not much of anything on it at the moment... except...

== TODO ==
=== 18/03/2022 ===
* Dukes:
** Cancel standing order (joint account? yes, and not due til 14/11, so no great rush)
** Phone/call/go round and organise new friends payments
* <s>Homeserve:</s>
** <s>Call them up and see why a 50% rise in price; maybe cancel. Probably cancel.</s>
* Library books
** not due til 24/03, but all read now.
* Co-op Bank
** Look into / setup new security requirements
** 2 invoices to Riverside to pay; see Accounts below.
* Accounts
** 2 invoices to put into Sage
** Both invoices need paying; See Co-op Bank above
** Company accounts for last year to sign and return
* Edinburgh
** Look for somewhere to eat on Sunday evening
** Maybe Sunday afternoon too
** Pick up tickets from station

== [[User:Stuart/Scratchpad|My Scratchpad]] ==
Which is primarily a work-in-progress pad on which I sketch out work in various states of not done.

== [[User:Stuart/Scratchpad II|My Second Scratchpad]] ==
For when the first scratchpad is in use / gets too full (like, er, now).

== [[:Category:Best Ofs|Best Ofs]] ==
A record of the tapes I made when I were a nipper, so I might recreate them and wallow in nostalgia and cringe at my appalling music taste.

== Global Bookmarks ==
* [[User:Stuart/Git Aliases]]
* [[User:Stuart/Public Keys]]
* [[User:Stuart/Leave Sheet]]
* [https://blog.habets.se/2011/07/OpenSSH-certificates.html OpenSSH Certificates]
* [[Waterdeep: Dragon Heist]]
* [[Jobs/FLAC Conversion]]
* [[Tech/Network]]
* ''DWP Stuff''
** [[Noctam/DWP/ACS Test Harness|ACS Test Harness]]

== Additional command line options for EAC ==
LAME:
-V0 --add-id3v2 --pad-id3v2 --ta "%artist%" --tt "%title%" --tg "%genre%" --tl "%albumtitle%" --ty "%year%" --tn "%tracknr%/%numtracks%" %source% %dest%
(not keen on the track number output, though; I may tweak that)

Looking into the LAME options, you kinda have to hand-craft most of the tags (partially limited LAME implementation; partially limited ID3 implementation).
[https://hydrogenaud.io/index.php?topic=95917.0 This topic on HydrogenAudio] explains how to about it.

I also installed [https://sourceforge.net/projects/taginspector/ Tag Inspector] to have a look at the tags on ''dream'' - specifically Ayreon tags for multi-disc albums.
There were quite a few {{c|TXXX: DISCNUMBER}} type things mentioned on, er, "a web page". Which unfortunately, I can't find, but it shouldn't be too hard to piece together.
----
FLAC:
-6 -V -T "ARTIST=%artist%" -T "TITLE=%title%" -T "ALBUM=%albumtitle%" -T "DATE=%year%" -T "TRACKNUMBER=%tracknr%" -T "GENRE=%genre%" -T "COMMENT=%comment%" -T "BAND=%albuminterpret%" -T "ALBUMARTIST=%artist%" -T "COMPOSER=%composer%" %haslyrics%--tag-from-file=LYRICS="%lyricsfile%"%haslyrics% -T "DISCNUMBER=%cdnumber%" -T "TOTALDISCS=%totalcds%" -T "TOTALTRACKS=%numtracks%" %hascover%--picture="%coverfile%"%hascover% %source% -o %dest%

User:Stuart

2022-03-18T11:57:20Z

Stuart: /* 18/03/2022 */

{{nav/stuart}}
My user page. Not much of anything on it at the moment... except...

== TODO ==
=== 18/03/2022 ===
* Dukes:
** Cancel standing order (joint account? yes, and not due til 14/11, so no great rush)
** Phone/call/go round and organise new friends payments
* Homeserve:
** Call them up and see why a 50% rise in price; maybe cancel. Probably cancel.
* Library books
** not due til 24/03, but all read now.
* Co-op Bank
** Look into / setup new security requirements
** 2 invoices to Riverside to pay; see Accounts below.
* Accounts
** 2 invoices to put into Sage
** Both invoices need paying; See Co-op Bank above
** Company accounts for last year to sign and return
* Edinburgh
** Look for somewhere to eat on Sunday evening
** Maybe Sunday afternoon too
** Pick up tickets from station

== [[User:Stuart/Scratchpad|My Scratchpad]] ==
Which is primarily a work-in-progress pad on which I sketch out work in various states of not done.

== [[User:Stuart/Scratchpad II|My Second Scratchpad]] ==
For when the first scratchpad is in use / gets too full (like, er, now).

== [[:Category:Best Ofs|Best Ofs]] ==
A record of the tapes I made when I were a nipper, so I might recreate them and wallow in nostalgia and cringe at my appalling music taste.

== Global Bookmarks ==
* [[User:Stuart/Git Aliases]]
* [[User:Stuart/Public Keys]]
* [[User:Stuart/Leave Sheet]]
* [https://blog.habets.se/2011/07/OpenSSH-certificates.html OpenSSH Certificates]
* [[Waterdeep: Dragon Heist]]
* [[Jobs/FLAC Conversion]]
* [[Tech/Network]]
* ''DWP Stuff''
** [[Noctam/DWP/ACS Test Harness|ACS Test Harness]]

== Additional command line options for EAC ==
LAME:
-V0 --add-id3v2 --pad-id3v2 --ta "%artist%" --tt "%title%" --tg "%genre%" --tl "%albumtitle%" --ty "%year%" --tn "%tracknr%/%numtracks%" %source% %dest%
(not keen on the track number output, though; I may tweak that)

Looking into the LAME options, you kinda have to hand-craft most of the tags (partially limited LAME implementation; partially limited ID3 implementation).
[https://hydrogenaud.io/index.php?topic=95917.0 This topic on HydrogenAudio] explains how to about it.

I also installed [https://sourceforge.net/projects/taginspector/ Tag Inspector] to have a look at the tags on ''dream'' - specifically Ayreon tags for multi-disc albums.
There were quite a few {{c|TXXX: DISCNUMBER}} type things mentioned on, er, "a web page". Which unfortunately, I can't find, but it shouldn't be too hard to piece together.
----
FLAC:
-6 -V -T "ARTIST=%artist%" -T "TITLE=%title%" -T "ALBUM=%albumtitle%" -T "DATE=%year%" -T "TRACKNUMBER=%tracknr%" -T "GENRE=%genre%" -T "COMMENT=%comment%" -T "BAND=%albuminterpret%" -T "ALBUMARTIST=%artist%" -T "COMPOSER=%composer%" %haslyrics%--tag-from-file=LYRICS="%lyricsfile%"%haslyrics% -T "DISCNUMBER=%cdnumber%" -T "TOTALDISCS=%totalcds%" -T "TOTALTRACKS=%numtracks%" %hascover%--picture="%coverfile%"%hascover% %source% -o %dest%

User:Stuart

2022-03-18T11:56:03Z

Stuart: Added TODO to do

{{nav/stuart}}
My user page. Not much of anything on it at the moment... except...

== TODO ==
=== 18/03/2022 ===
* Dukes:
** Cancel standing order (joint account?)
** Phone/call/go round and organise new friends payments
* Homeserve:
** Call them up and see why a 50% rise in price; maybe cancel. Probably cancel.
* Library books
** not due til 24/03, but all read now.
* Co-op Bank
** Look into / setup new security requirements
** 2 invoices to Riverside to pay; see Accounts below.
* Accounts
** 2 invoices to put into Sage
** Both invoices need paying; See Co-op Bank above
** Company accounts for last year to sign and return
* Edinburgh
** Look for somewhere to eat on Sunday evening
** Maybe Sunday afternoon too
** Pick up tickets from station

== [[User:Stuart/Scratchpad|My Scratchpad]] ==
Which is primarily a work-in-progress pad on which I sketch out work in various states of not done.

== [[User:Stuart/Scratchpad II|My Second Scratchpad]] ==
For when the first scratchpad is in use / gets too full (like, er, now).

== [[:Category:Best Ofs|Best Ofs]] ==
A record of the tapes I made when I were a nipper, so I might recreate them and wallow in nostalgia and cringe at my appalling music taste.

== Global Bookmarks ==
* [[User:Stuart/Git Aliases]]
* [[User:Stuart/Public Keys]]
* [[User:Stuart/Leave Sheet]]
* [https://blog.habets.se/2011/07/OpenSSH-certificates.html OpenSSH Certificates]
* [[Waterdeep: Dragon Heist]]
* [[Jobs/FLAC Conversion]]
* [[Tech/Network]]
* ''DWP Stuff''
** [[Noctam/DWP/ACS Test Harness|ACS Test Harness]]

== Additional command line options for EAC ==
LAME:
-V0 --add-id3v2 --pad-id3v2 --ta "%artist%" --tt "%title%" --tg "%genre%" --tl "%albumtitle%" --ty "%year%" --tn "%tracknr%/%numtracks%" %source% %dest%
(not keen on the track number output, though; I may tweak that)

Looking into the LAME options, you kinda have to hand-craft most of the tags (partially limited LAME implementation; partially limited ID3 implementation).
[https://hydrogenaud.io/index.php?topic=95917.0 This topic on HydrogenAudio] explains how to about it.

I also installed [https://sourceforge.net/projects/taginspector/ Tag Inspector] to have a look at the tags on ''dream'' - specifically Ayreon tags for multi-disc albums.
There were quite a few {{c|TXXX: DISCNUMBER}} type things mentioned on, er, "a web page". Which unfortunately, I can't find, but it shouldn't be too hard to piece together.
----
FLAC:
-6 -V -T "ARTIST=%artist%" -T "TITLE=%title%" -T "ALBUM=%albumtitle%" -T "DATE=%year%" -T "TRACKNUMBER=%tracknr%" -T "GENRE=%genre%" -T "COMMENT=%comment%" -T "BAND=%albuminterpret%" -T "ALBUMARTIST=%artist%" -T "COMPOSER=%composer%" %haslyrics%--tag-from-file=LYRICS="%lyricsfile%"%haslyrics% -T "DISCNUMBER=%cdnumber%" -T "TOTALDISCS=%totalcds%" -T "TOTALTRACKS=%numtracks%" %hascover%--picture="%coverfile%"%hascover% %source% -o %dest%

Noctam/DWP/ACS Test Harness/Existing System/CISSIM/Command Line Tools/Confluence Version

2021-10-19T15:43:21Z

Stuart: Created page with "<noinclude>{{nav/ACS Test Harness}}</noinclude> There are many command line tools to do various things within the CISSIM / proxy / data management / testing stub / kitchen si..."

<noinclude>{{nav/ACS Test Harness}}</noinclude>
There are many command line tools to do various things within the CISSIM / proxy / data management / testing stub / kitchen sink application.

This page tries to exhaustively go through all of them. It fails. But it continues to try.
= File formats =
There are a few file formats used here.

== base64-ebcdic ==
EBCDIC data and binary fields encoded into base64.

This is the form for most PD calls - the content is a record whose definition is held elsewhere (in COBOL copybook-ish form)

Used as input and output to/from [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdutils pdutils] and [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdedit pdedit].

== base64-ascii ==
ASCII data and binary fields encoded into base64.

Just like [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#base64-ebcdic base64-ebcdic] except the text fields are encoded into ASCII rather than EBCDIC.

This can be used as input to [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdutils pdutils] when using the {{c|CONVERT2E}} option to convert it to [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#base64-ebcdic base64-ebcdic], and output from [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdutils pdutils] using the {{c|CONVERT2A}} option.

= Filename format =
Some of the following utilities expect the filename to be in one of a number of specific formats. They use this
format to embed information about the transaction that the file represents, later extracted by the programs to look up
related data and/or structures.

== pdconvert formats ==
The [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdconvert pdconvert], [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdconvertone pdconvertone] and [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdconvertall pdconvertall] programs expect
the files to be named in one of two dot-separated formats; one with 4 'parts', one with any other number of 'parts'
as long they number at least 3. The 4 part format is represented by the regex:

^(?P<dialognum>[^.]{0,6})\.[^.]*\.[^.]*\.(?P<direction>in|out)$

eg. "DCI908.NINO.STUB.out"

The 4 dot-separated parts indicate that this is an 'R' (read) mode transaction. A suffix of 'in' indicates a 'RQST' direction,
'out' indicates a 'RPLY' direction. The dialog is extracted as the first 6 chars of the first part, the mode and the direction
separated by underscores, so the above example would yield:
DCI908_R_RQST

The 'any number above 2, except 4' format (?) extracts more information from the filename:
^(?P<dialognum>[^.]*)\.[^.]{3}(?P<messageid>[^.]{4})(?P<txnmode>[^.]).*\.(?P<direction>in|out)$

eg. "PD375.CIS6084RCURRINT.153250.634934c5c8d6.in"

This builds the dialog and transaction mode from the filename. The direction is mapped to 'RQST' or 'RPLY' where the filename
has 'in' or 'out', and the dialog is built up as: {{c|<dialognum>_<messageid>_<txnmode>_<direction>}}. The above example
would end up with the dialog:
PD375_6084_R_RQST

= Programs =

== pdutils ==
Primarily a library file, used throughout various calls from the daemon programs as well as other utilities.
It can, however, also be called directly from the command line.

Usage: pdutils <DUMP/OUT/SAVE/CONVERT2E/CONVERT2A> <dialog> <RQST/RPLY> <requestfile/replyfile>

Note that SAVE requires redirected input from an ASCII text string, such as '< <datafile>'
and that CONVERT requires redirected input from B64 encoded ASCII data '< <datafile>'

=== DUMP ===
Dumps the structure of a request found in a base64-encoded EBCDIC file out to the console.

This puts ''everything'' out - ie. all the fields, the fillers and the groups. The values are wrapped into square brackets the appropriate size for capturing the data for the field. Binary values have leading zeroes trimmed; all char values are displayed as found.

It prefixes the field with the data structure (''eg'' B4 for binary 4 bytes; X16 for char 16 bytes; N2 for numeric char 2 bytes).

It suffixes the value with the hex value found for the field, separated into space-separated octets, wrapped in parantheses.

=== OUT ===
Dumps the structure of a request found in a base64-encoded EBCDIC file out to the console.

This only puts out the fields and fillers. The values are wrapped into square brackets the appropriate size for capturing the data for the field. Binary values have leading zeroes trimmed; all char values are displayed as found.

=== SAVE ===
'''Note:''' this doesn't work on Windows, because it uses [https://docs.python.org/3/library/select.html#select.select select.select()] to ensure that stdin is available, and that function only works on file descriptors on POSIX systems.

Uses a 'hidden' fifth argument, i.e. it expects the input file to be provided on stdin. The {{c|<requestfile/replyfile>}} argument is, in this case, an ''output'' file.

I have tweaked the code to work in Windows and... I don't really know what this does, i.e. I don't know what format the input file is expected to be in. It's not the same as the 'requestfile/replyfile' used for DUMP and OUT, because that fails with the exception message: ''invalid literal for int() with base 10: 'AAAAMMPJ4' ''

=== CONVERT2E ===
'''Note:''' this doesn't work on Windows, because it uses [https://docs.python.org/3/library/select.html#select.select select.select()] to ensure that stdin is available, and that function only works on file descriptors on POSIX systems.

Uses a 'hidden' fifth argument, i.e. it expects the input file to be provided on stdin. The {{c|<requestfile/replyfile>}} argument is, in this case, an ''output'' file.

This converts input from stdin, in base64-encoded ASCII record format to the output file, in base64-encoded EBCDIC record format. This is the exact mirror of {{c|CONVERT2A}}.

Note: This only works for PD data, not DCI or NPS (which are only ever required in ASCII-based encodings).

=== CONVERT2A ===
'''Note:''' this doesn't work on Windows, because it uses [https://docs.python.org/3/library/select.html#select.select select.select()] to ensure that stdin is available, and that function only works on file descriptors on POSIX systems.

Uses a 'hidden' fifth argument, i.e. it expects the input file to be provided on stdin. The {{c|<requestfile/replyfile>}} argument is, in this case, an ''output'' file.

This converts input from stdin, in base64-encoded EBCDIC record format to the output file, in base64-encoded ASCII record format. This is the exact mirror of {{c|CONVERT2A}}.

Note: This only works for PD data, not DCI or NPS (which are only ever required in ASCII-based encodings).

== pdedit ==
Edits the PD and DCI call data via a curses interface, using the COBOL data layouts for the calls.

Usage: pdedit <dialog> <RQST/RPLY> <sourcefile> <destfile>

The 'sourcefile' in this case is the same as the 'requestfile/replyfile' provided in pdutils, that is, a file containing base64-encoded EBCDIC data. The 'destfile' is in the same format with the changes applied (assuming that you save inside pdedit).

Intriguingly, it appears to ignore the 'RQST/RPLY' in the dialog and effectively overwrites it with the RQST/RPLY argument given to the program.
Not really sure why... that dialog is a bit of a hack, really, I suspect just to avoid multiple keys or too much structure in the config.

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.

== pddb ==
Creates a database entry which effectively maps a response file onto a request.

Usage: pddb <dialog> <sourcefile> <destfile> <EBCDIC/ASCII>

The output is in the form:
<dialog>:<response-file>:<input-field-name=value[;...]>

So, for a PD350 1151 request, you might see something like:
$ python cissim/pddb.py PD350_1151_R_RQST requests/pd350-request-e messages/PD350.CIS1151RSTRTDIA.AASTUB.out EBCDIC
PD350_1151_R_RQST:PD350.CIS1151RSTRTDIA.AASTUB.out:H1151-NINO=ST000001;H1151-NINO-SFX-TX=A;H1151-RQST-DSS-DAYS=20190213;H1151-RQST-DIA-ID=PD350 ;H1151-RQST-USR-NS-LVL=0000;H1151-RQST-USR-LS-LVL=0000;H1151-RQST-USR-BUS-SYS-NO=43;H1151-DEPT-ID-TP=1;H1151-OFF-LOC-NO=04710;H1151-RQST-SPCFC-BUS-TP=85;

These entries can be appended into a single file, with each entry on a separate line and work together to a form a readonly database of sorts, which the server can use to lookup the response to use based on the values of the inputs provided in the request.

== pdserve ==
This is what uses the given 'database' files from pddb to serve the data based on the requests.

Usage: pdserve <configfile> [<port>]

It takes a config file which is effectively made up of paths to the 'databases' built up using pddb along with an (optional) SSL flag. Each pddb line in the config is something like:
<path-to-db-file>:<folder>

So, for example:

configfile.ja030
SSL=N
pdbase/JA030_01.CIS.txt:pdbase
pdbase/JA030_02.CIS.txt:pdbase
pdbase/JA030_99.CIS.txt:pdbase

pdserve will expect to find the response files with the names defined in the 'database' within the folder specified in the config, so you could have multiple entries here pointing to different databases.

The 'port' here is the port it will listen on. This is analogous to a 'swimlane' (''<sigh>'') and, indeed, the terms are used interchangeably in some places. The default port value used is ''9127''.

The recommended way of running this is using {{c|nohup}} so that you can exit the shell and it will continue to run... something like:
nohup python pdserve.py configfile.ja030 9130 >ja030.log &

... and of course, the only way to kill it after doing that is by identifying the process that's running and using the {{c|kill}} command.

Final thing. Quite important. 
The version I have doesn't work.

In Python 2:
$ python2 ../cissim/pdserve.py pdserve.test.config 9927
File "../cissim/pdserve.py", line 68
print(s.server_version, end=' ')
^
SyntaxError: invalid syntax

In Python 3:
$ python ../cissim/pdserve.py pdserve.test.config 9927
Traceback (most recent call last):
File "../cissim/pdserve.py", line 316, in <module>
status = main()
File "../cissim/pdserve.py", line 260, in main
if '#' in line:
TypeError: a bytes-like object is required, not 'str'

It looks like it's been half-heartedly converted from 2 to 3, but untested. I'm assuming that either nobody uses it, or it's been fixed in place wherever it is used and the changes haven't been reflected back to the source.

== pdcall ==
(Incidentally, this was a bit messy to get working due to using pycurl, I had to {{c|apt install libcurl4-openssl-dev libssl-dev}} and {{c|pip install pycurl}} in order to get this to work on my Ubuntu machine - no idea what this will require on Mac, but be prepared for pain, given how little access we have.)

This can be used to call the server and test that it's working correctly.

Usage: pdcall <swimlane> <dialog> <requestfile> <replyfile>

The '<swimlane>' here is the port that the server is listening on.

This opens the request file and displays it using [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdedit pdedit]. After editing and saving, it posts the updated request to the server, captures the response and then opens ''that'' in pdedit too so that you can see (and, indeed, edit) the response, before saving to the output file.

At least, I think that's what it does - because I couldn't get [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#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 ==
Calls a running ACS instance with an edited request, storing the response into the required output file.

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

This pops up a {{c|pdedit}} window to edit the request (actually saving the resultant file to the given location), then creates the
request by prepending the ACS input header, with the uppercased {{c|service}} embedded in it, to the input file contents.

The ACS input header is fixed (service aside) and has the following content:
<pre>
0ed1249b558f||True|101307| |DCP26PD350 |null|<service>|11606730|null|DWDDE662|2|1548331293|0|500|0|false|P|60|468|
</pre>

The full input is saved to a file in the current directory called {{c|<requestfile>.acs}}. The response from ACS is saved into the
provided {{c|replyfile}}.

== pdconvertall ==
Converts *.in files and corresponding *.out files from a source folder into a destination folder.

Usage: pdconvertall.py <sourcefolder> <targetfolder>

Note that the filename format is significant for this program and, natch, undocumented.
See [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdconvert formats pdconvert formats] for more details.

This scans the {{c|sourcefolder}} for all files matching {{c|*.in}} which ''do not'' start with the characters {{c|NPS}} and
have corresponding {{c|*.out}} files and 'converts' them to a text-based format for use with [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdserved pdserved].

The conversion of the input file is almost identical to the processing done by calling [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdutils pdutils] with the
dialog and direction specified explicitly, though this program picks up that information from the embedded data in the filename.

The directory structure it creates is:
<outputfolder>
|- <dialog>
|- <rundate-yyyyMMdd>
|- <nino>.DATA

The format is text-based in the style of the [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdutils pdutils] format. The [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdserved pdserved] server then reads
from the directory when it is processing the requests and determining the responses to return. The files can be modified in
place, or new files can be placed there. The server will pick up any external changes made to these files.

== pdconvertone ==
This is a thin wrapper around [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdconvertall pdconvertall] which works for a single input and output file. That is, it
still expects a {{c|*.in}} and corresponding {{c|*.out}} file to convert, and it emits the output into the directory
structure described in [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdconvertall pdconvertall].
Usage: pdconvertone.py <sourcespec> <targetfolder>

This calls {{c|pdconvertall}} with the single file identified by {{c|sourcespec}}. Note that if the file begins with the
characters {{c|NPS}} or there is no corresponding {{c|*.out}} file, it will be skipped

== pdconvert ==
Converts a single file into its text-based format, emitting the output to stdout.

Usage: pdconvert.py <pdfile>

This does not have the same restrictions as [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdconvertall pdconvertall] and [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdconvertone pdconvertone] - i.e.
it does not require corresponding {{c|*.in}} and {{c|*.out}} files, though the given file's filename must be one of those.
It will still not work for NPS files (though, unlike the above programs, it will try and probably crash and burn in the
attempt).

== pddata ==
''Library file.''

This has a load of functions in it, only some of which I understand.
The main one appears to be {{c|getninodata}} which, typical cissim style, takes 10 arguments (interrobang?!) and has...
well, ''some'' documentation which concentrates on one or two arguments and expects a fairly solid understanding of
what it's doing before you start reading.

I'm going to have to come back to this to try and grasp it.

'''Note:''' This technically can be executed, but it looks like the stuff in the main call is just development stuff - testing
other functions and such like.

== pddump ==
This dumps the data from the given (base64-encoded EBCDIC) file to the console in text form with square brackets to enclose
the data values. Note: This uses the [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdconvert formats pdconvert formats] for the filename.

Usage: pddump.py <pdfile>

This is a call to [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#DUMP DUMP] which takes the dialog / direction arguments from the filename
format rather than requiring them to be stated explicitly.

== pdout ==
This dumps the data from the given (base64-encoded EBCDIC) file to the console in text form with square brackets to enclose
the data values. Note: This uses the [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdconvert formats pdconvert formats] for the filename.

Usage: pdout.py <pdfile>

This is a call to [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#OUT OUT] which takes the dialog / direction arguments from the filename

== pdparams ==
''Library file.''

Contains a single function: {{c|processparams}}. This function also exists in [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdutils pdutils], and it looks like that
one is used but this one is not. I presume it's obsolete, though there's no indication of that in the code.

'''Deprecated?'''

== pdproxy ==
A very straightforward proxy which writes the request and response of any CIS calls made to it to files in the current
directory.

Usage: pdproxy <swimlane> <configfile> <folder> [<port>]

The swimlane determines whether the 'real' CIS is called or whether the 'SIM' is called. Basically, if the {{c|swimlane}}
argument is in the ranges: 14-15 or 17-28 (both inclusive), onward calls from the proxy will go to CIS proper. Any other
value is treated as the port that the simulator is listening on and it will be connected to using that port number.

== pdreadall ==
Reads all registered dialogs and calls them for the specified NINo and optional surname.

Usage: pdreadall <swimlane> <paramfile> <folder> <nino> [<surname>]

== pdreadoneedit ==
Calls a specified dialog in CIS (or a CIS simulator) for a given NINo and optional surname. This allows the editing of
the record to be sent in the request before the call is made. The input and output files are created (I ''think'') in
the current directory with the appropriate filename format.

Usage: pdreadoneedit <swimlane> <paramfile> <dialog> <nino> [<surname>]

== pdreadone ==
Calls a specified dialog in CIS (or a CIS simulator) for a given NINo and optional surname. This does not allow the
editing of the record to be sent in the request before the call is made. The input and output files are created (I
''think'') in the current directory with the appropriate filename format.

Usage: pdreadone <swimlane> <paramfile> <dialog> <nino> [<surname>]

== pdscreen ==
''Library file.''

This file contains a single class '{{c|Textbox}}' which provides the editing widget used in [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdedit pdedit] to
edit a value in a record file.

== pdserved ==
An upgraded version of [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#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 [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#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.

== pdservedt ==
[https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdserved pdserved] with a {{c|process_wait()}} function, which loads the timing data from the hardcoded location
at {{c|../serve/transtimes.py}}. Not ideal - it requires running the program from a specific directory, and, of course,
this is undocumented (as far as I can see anyway).

The timing data is a map of timings against dialog; the example in the code is:
<pre>
# timings are a list, first tuple is times to cycle through, rest are exceptional count/time pairs
# 'CP650_1151_R_RPLY': [(0.15, 0.25, 0.21, 0.17, 0.20, 0.16), (20, 2.3), (100, 28)],
</pre>
Basically, it will cycle through the first tuple of timings, except when the count for a given dialog reaches the
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.

'''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 [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#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 ==
This is [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdserve pdserve] with more NPS handling (and fixed for Python3).

The NPS changes in here appear to be included in [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdserved pdserved] too, so this and [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdserve pdserve], at
first glance, would seem to be obsolete.

== pdshow ==
Shows and edits a base64-encoded file, extracting the dialog and direction from the filename.

Usage: pdshow.py <pdfile>

This is a wrapper around a call to [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdedit pdedit] which extracts the dialog and direction from the filename,
rather than needing it specified explicitly.

== 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 ==
This is [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdstub pdstub] with a {{c|process_wait()}} function, which works exactly like the same function in
[https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdservedt pdservedt].

== pdstubtt ==
This is [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdstubt pdstubt] with a multi-threaded HTTP server. It's a fairly trivial change to the code; I haven't
looked through it to see if there are any thread localisation issues in there - I'm assuming not, because this is
being used as is at the moment, and that would probably have been noticed by now.

This seems to me to be the most mature of the pdstub implementations - multithreading the server is a no-brainer,
in my humble, and the timings can be ignored. It still has the problem of a hardcoded timing config, but that
shouldn't be too hard to fix in a less fragile manner.

== pdtux ==
A Tuxedo server which advertises a few tux operations, namely:
* ping
* DCI913
* DCI923
* VMERCIS
* RESETCOUNTER

This extracts the data out of the request packet and gets the data using [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pddata pddata],
returning the resultant data (the whole thing for DCI calls, separated CIS header and W90 header for PDD calls).

There are no arguments to this program, but it does require the installation of the 'tuxedo' python module.

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

== certs ==
''Library file''

Holds the paths to the various certificates used within cissim. 2 groups of cert and cacert files for connecting to
DCI and PD; 2 groups of cert and private key files for serving.

Used in [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdcall pdcall], [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdserve pdserve] and [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdstub pdstub] programs, and in some test functions
in [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#sslutils sslutils].

== checkport ==
''Redundant''

Checks if it's possible to connect to {{c|localhost:9127}}. That's it really.

Basically, a python version of:
netstat -nap | grep ':9127.*LISTEN'

== dci9n3rec ==
''Library file''

Technically, this can be called from the command line, but it seems a bit pointless. It appears to read in a file
called 'in' in the current directory and, uh, loads it into a DCI9n3 record structure and prints it. I guess it's
for testing purposes.

Anyway, this contains the definition of a DCI913 or DCI923 record, packed to byte alignment for the fields, with
the 12 fields and their sizes defined as fixed length byte arrays.

It's only used in [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdtux pdtux] for extracting the data from an incoming DCI struct. The equivalent for a PD
record is [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#w80construct w80construct]

== extractodis ==
''Executable''

Usage: extractodis.py <log_filename> [<PID>] [<starttime>] [<endtime>]

This is completely out there. So. It takes the filename and creates 3 shell scripts with names based on it, which
perform some function on the payload (base64-encoded ASCII). These scripts are:
* {{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 [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#CONVERT2E CONVERT2E])
* {{c|<filename>.db.sh}}: to write the transaction to the 'database' for serving (calling [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pddb pddb])

Aside from some very ropey python issues (mix of tabs and spaces in leading whitespace - very verboten in python),
it's just a very odd way of doing things.

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 [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdserved pdserved] and beyond; the pddb output is used in the original
[https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdserve pdserve] program too. It's still valid for the 'write.sh', I guess, but I suspect that's all.

== fpcapprec ==
''Library file''

{{obsolete}}

This was used in [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdtux pdtux], but is no longer used. The using has been deleted, so I can't see the context.

== getfieldoffset ==
''Test file''

{{obsolete}}

I'm pretty sure this is just testing that the [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdlayouts.pd pdlayouts.pd] method is working
correctly.

== key ==
''Library file''

This provides a few constants for keycodes, used in [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdedit pdedit] and [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdscreen pdscreen].

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
deserve its own file; any home-grown key values could go in the [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdscreen pdscreen] file.

== loadninos ==
''Library File'' and ''Executable''

Usage: loadninos.py <office-file>

Used in [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdstub pdstub] and its variants.

Loads NINOs from a CSV file (actually looks like a 'Whitespace-separated variables' style file, though it has a
name of {{c|csvfile}} within the code). This looks for input in the form:
<pre>
SVC Office
JSOV 109809
JSRZ 107476
JSFP 107038
JSLH 103401
JSKR 103838
JSLF 102636
JSGR 102805
JSRT 100598
</pre>
The above example is half-inched from the code. The code is ferociously simplistic, but I guess it does the job.

Anyway, it takes the 'Office' from the lines in the 'CSV' file, strips the leading digit from it, then looks for
another 'csv' file with that office number as a filename, in the same directory as the provided CSV file, so the
above will look for '09809.csv', '07476.csv' etc. It will load that file, taking the first 8 chars of each line
as a NINo and then maps the office to that NINo, such that each NINo has the office number of the file that it
was loaded from mapped against it.

This is used in [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdstub pdstub] to get the office for a particular NINo, which is then used as part of the
response in a DCI913 call. The stub loads the NINos using this function passing the {{c|OFFICECSVFILE}} config
parameter value to load them from. It doesn't handle errors well, but I guess once it's running, you don't
change it that much.

== logextract ==
''Executable''

Usage: logextract.py <logfile>

Extracts a {{c|DCI913CopyRecord}} from a logfile. It's a bit hacky - in the middle of it, it does some strange
stuff with the string '127.0.0.1'; I presume the logfile isn't really designed for extracting records from and
so this has to hardcode some messing around into it. It's very fragile - logfiles aren't typically structured
output (or, at least, not structured in this way).

== npsload ==
''Executable'' - this is an executable only; no part of it is called by other programs / libraries.

Usage: npsload <folder> <csvfile> <listfile>

This loads the {{c|csvfile}} from {{c|folder}} (i.e. the file is just the filename, not the {{c|/path/to/file}}),
and writes all output, including the {{c|listfile}} in the same folder.

The CSV file is defined as:
Entry/ies Description
1 NINo
2 Surname
3 Office
4 LOP 25x Past
5-20 NUBS2 record x 4
21-36 LOP record x 4
37 Data not found flag
38 BFM Return Code
39 RDS Code

Each NUBS2 record and LOP record is made up of 4 comma-separated entries, with the fields:
Entry Description
1 Year
2 x25
3 x50
4 Priority

This program loops through all the NINo entries, and writes an XML file for each one, calling it {{c|NPSrply.<nino>.xml}},
adding an entry into the {{c|listfile}} for each file it created. It adds a final 'NINO not found' entry to the listfile
and exits.

== paths ==
''Library file''

Contains the paths used for calls to PD, DCI and NPS, as well as a few functions which operate on and around those paths.

This is used liberally throughout the rest of the CISSim suite.

== 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 ==
''Executable''

I have no idea what this is trying to do. It's messing around with servers and message queues, but I'm a bit lost.

== sslutils ==
''Library file''

Contains functions to call servers using SSL certificates. Used in [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdacs pdacs], [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdcall pdcall], [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdproxy pdproxy]
and [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#teststub teststub]

== temp ==
{{obsolete}}

Seems to be a copy of [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdserved pdserved] with some testing code in there.

== teststub ==
{{obsolete}}

Tests connecting to the CIS Sim using curl and a socket. Prints things. Not particularly useful.

== utils ==
''Library file''

{{obsolete}}

A variety of utility functions; apparently not used anywhere.

== vmeutils ==
''Library file'' and ''Executable''

Usage: vmeutils <D/B> <date>

Some VME date functions and a small utility executable to convert a date into a VME date ({{c|'B'}}, obviously) or
a VME date into a date ({{c|'D'}}). A 'VME date' in this context is the number of days since 29/02/1852.

== w80construct ==
''Library file''

Like [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#dci9n3rec dci9n3rec], this can be called from the command line, but it also seems a bit pointless.
I guess it's for testing purposes.

Anyway, this contains the definition of a W80 record, packed to byte alignment for the fields, with the various fields
and their sizes defined mostly as fixed length byte arrays, though there are a few integer and long integer fields
defined too - these will be compiler-dependent, so I guess that's how the tux that it's interfacing with/mocking
works too?

It's only used in [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#pdtux pdtux] for extracting the data from an incoming DCI struct. The equivalent for a DCI
record is [https://dwpdigital.atlassian.net/wiki/spaces/BO/pages/132486857398/CIS+Simulator+Python+System#dci9n3rec dci9n3rec]

= Files in pdlayouts =

== pdlayouts/PDM ==
The 'PD Map' contains the fields used in the CIS header and the W80 PD header, including their name, data type and length and
an optional 'style' type argument which provides metadata for the field, ''eg.'' {{c|nino8}} indicates the first 8 chars of
a NINo, {{c|runtime8}} indicates that it contains a time in the format {{c|%H%M%S%f}}, {{c|vmedate}} indicates that the field
contains a 'VME date', ie. the number of days since 29/02/1852.

These 'style' arguments are used in {{c|pdutils.makerequestfile}} to autopopulate various fields for input based on the static
'RUNDATE' parameter value.

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

2021-10-19T08:28:16Z

Stuart: Removed extraneous .py's

<noinclude>{{nav/ACS Test Harness}}</noinclude>
There are many command line tools to do various things within the CISSIM / proxy / data management / testing stub / kitchen sink application.

This page tries to exhaustively go through all of them. It fails. But it continues to try.
= File formats =
There are a few file formats used here.

== base64-ebcdic ==
EBCDIC data and binary fields encoded into base64.

This is the form for most PD calls - the content is a record whose definition is held elsewhere (in COBOL copybook-ish form)

Used as input and output to/from [[#pdutils|pdutils]] and [[#pdedit|pdedit]].

== base64-ascii ==
ASCII data and binary fields encoded into base64.

Just like [[#base64-ebcdic|base64-ebcdic]] except the text fields are encoded into ASCII rather than EBCDIC.

This can be used as input to [[#pdutils|pdutils]] when using the {{c|CONVERT2E}} option to convert it to [[#base64-ebcdic|base64-ebcdic]], and output from [[#pdutils|pdutils]] using the {{c|CONVERT2A}} option.

= Filename format =
Some of the following utilities expect the filename to be in one of a number of specific formats. They use this
format to embed information about the transaction that the file represents, later extracted by the programs to look up
related data and/or structures.

== pdconvert formats ==
The [[#pdconvert|pdconvert]], [[#pdconvertone|pdconvertone]] and [[#pdconvertall|pdconvertall]] programs expect
the files to be named in one of two dot-separated formats; one with 4 'parts', one with any other number of 'parts'
as long they number at least 3. The 4 part format is represented by the regex:

^(?P<dialognum>[^.]{0,6})\.[^.]*\.[^.]*\.(?P<direction>in|out)$

eg. "DCI908.NINO.STUB.out"

The 4 dot-separated parts indicate that this is an 'R' (read) mode transaction. A suffix of 'in' indicates a 'RQST' direction,
'out' indicates a 'RPLY' direction. The dialog is extracted as the first 6 chars of the first part, the mode and the direction
separated by underscores, so the above example would yield:
DCI908_R_RQST

The 'any number above 2, except 4' format (?) extracts more information from the filename:
^(?P<dialognum>[^.]*)\.[^.]{3}(?P<messageid>[^.]{4})(?P<txnmode>[^.]).*\.(?P<direction>in|out)$

eg. "PD375.CIS6084RCURRINT.153250.634934c5c8d6.in"

This builds the dialog and transaction mode from the filename. The direction is mapped to 'RQST' or 'RPLY' where the filename
has 'in' or 'out', and the dialog is built up as: {{c|<dialognum>_<messageid>_<txnmode>_<direction>}}. The above example
would end up with the dialog:
PD375_6084_R_RQST

= Programs =

== pdutils ==
Primarily a library file, used throughout various calls from the daemon programs as well as other utilities.
It can, however, also be called directly from the command line.

Usage: pdutils <DUMP/OUT/SAVE/CONVERT2E/CONVERT2A> <dialog> <RQST/RPLY> <requestfile/replyfile>

Note that SAVE requires redirected input from an ASCII text string, such as '< <datafile>'
and that CONVERT requires redirected input from B64 encoded ASCII data '< <datafile>'

=== DUMP ===
Dumps the structure of a request found in a base64-encoded EBCDIC file out to the console.

This puts ''everything'' out - ie. all the fields, the fillers and the groups. The values are wrapped into square brackets the appropriate size for capturing the data for the field. Binary values have leading zeroes trimmed; all char values are displayed as found.

It prefixes the field with the data structure (''eg'' B4 for binary 4 bytes; X16 for char 16 bytes; N2 for numeric char 2 bytes).

It suffixes the value with the hex value found for the field, separated into space-separated octets, wrapped in parantheses.

=== OUT ===
Dumps the structure of a request found in a base64-encoded EBCDIC file out to the console.

This only puts out the fields and fillers. The values are wrapped into square brackets the appropriate size for capturing the data for the field. Binary values have leading zeroes trimmed; all char values are displayed as found.

=== SAVE ===
'''Note:''' this doesn't work on Windows, because it uses [https://docs.python.org/3/library/select.html#select.select select.select()] to ensure that stdin is available, and that function only works on file descriptors on POSIX systems.

Uses a 'hidden' fifth argument, i.e. it expects the input file to be provided on stdin. The {{c|<requestfile/replyfile>}} argument is, in this case, an ''output'' file.

I have tweaked the code to work in Windows and... I don't really know what this does, i.e. I don't know what format the input file is expected to be in. It's not the same as the 'requestfile/replyfile' used for DUMP and OUT, because that fails with the exception message: ''invalid literal for int() with base 10: 'AAAAMMPJ4' ''

=== CONVERT2E ===
'''Note:''' this doesn't work on Windows, because it uses [https://docs.python.org/3/library/select.html#select.select select.select()] to ensure that stdin is available, and that function only works on file descriptors on POSIX systems.

Uses a 'hidden' fifth argument, i.e. it expects the input file to be provided on stdin. The {{c|<requestfile/replyfile>}} argument is, in this case, an ''output'' file.

This converts input from stdin, in base64-encoded ASCII record format to the output file, in base64-encoded EBCDIC record format. This is the exact mirror of {{c|CONVERT2A}}.

Note: This only works for PD data, not DCI or NPS (which are only ever required in ASCII-based encodings).

=== CONVERT2A ===
'''Note:''' this doesn't work on Windows, because it uses [https://docs.python.org/3/library/select.html#select.select select.select()] to ensure that stdin is available, and that function only works on file descriptors on POSIX systems.

Uses a 'hidden' fifth argument, i.e. it expects the input file to be provided on stdin. The {{c|<requestfile/replyfile>}} argument is, in this case, an ''output'' file.

This converts input from stdin, in base64-encoded EBCDIC record format to the output file, in base64-encoded ASCII record format. This is the exact mirror of {{c|CONVERT2A}}.

Note: This only works for PD data, not DCI or NPS (which are only ever required in ASCII-based encodings).

== pdedit ==
Edits the PD and DCI call data via a curses interface, using the COBOL data layouts for the calls.

Usage: pdedit <dialog> <RQST/RPLY> <sourcefile> <destfile>

The 'sourcefile' in this case is the same as the 'requestfile/replyfile' provided in pdutils, that is, a file containing base64-encoded EBCDIC data. The 'destfile' is in the same format with the changes applied (assuming that you save inside pdedit).

Intriguingly, it appears to ignore the 'RQST/RPLY' in the dialog and effectively overwrites it with the RQST/RPLY argument given to the program.
Not really sure why... that dialog is a bit of a hack, really, I suspect just to avoid multiple keys or too much structure in the config.

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.

== pddb ==
Creates a database entry which effectively maps a response file onto a request.

Usage: pddb <dialog> <sourcefile> <destfile> <EBCDIC/ASCII>

The output is in the form:
<dialog>:<response-file>:<input-field-name=value[;...]>

So, for a PD350 1151 request, you might see something like:
$ python cissim/pddb.py PD350_1151_R_RQST requests/pd350-request-e messages/PD350.CIS1151RSTRTDIA.AASTUB.out EBCDIC
PD350_1151_R_RQST:PD350.CIS1151RSTRTDIA.AASTUB.out:H1151-NINO=ST000001;H1151-NINO-SFX-TX=A;H1151-RQST-DSS-DAYS=20190213;H1151-RQST-DIA-ID=PD350 ;H1151-RQST-USR-NS-LVL=0000;H1151-RQST-USR-LS-LVL=0000;H1151-RQST-USR-BUS-SYS-NO=43;H1151-DEPT-ID-TP=1;H1151-OFF-LOC-NO=04710;H1151-RQST-SPCFC-BUS-TP=85;

These entries can be appended into a single file, with each entry on a separate line and work together to a form a readonly database of sorts, which the server can use to lookup the response to use based on the values of the inputs provided in the request.

== pdserve ==
This is what uses the given 'database' files from pddb to serve the data based on the requests.

Usage: pdserve <configfile> [<port>]

It takes a config file which is effectively made up of paths to the 'databases' built up using pddb along with an (optional) SSL flag. Each pddb line in the config is something like:
<path-to-db-file>:<folder>

So, for example:

configfile.ja030
SSL=N
pdbase/JA030_01.CIS.txt:pdbase
pdbase/JA030_02.CIS.txt:pdbase
pdbase/JA030_99.CIS.txt:pdbase

pdserve will expect to find the response files with the names defined in the 'database' within the folder specified in the config, so you could have multiple entries here pointing to different databases.

The 'port' here is the port it will listen on. This is analogous to a 'swimlane' (''<sigh>'') and, indeed, the terms are used interchangeably in some places. The default port value used is ''9127''.

The recommended way of running this is using {{c|nohup}} so that you can exit the shell and it will continue to run... something like:
nohup python pdserve.py configfile.ja030 9130 >ja030.log &

... and of course, the only way to kill it after doing that is by identifying the process that's running and using the {{c|kill}} command.

Final thing. Quite important. 
The version I have doesn't work.

In Python 2:
$ python2 ../cissim/pdserve.py pdserve.test.config 9927
File "../cissim/pdserve.py", line 68
print(s.server_version, end=' ')
^
SyntaxError: invalid syntax

In Python 3:
$ python ../cissim/pdserve.py pdserve.test.config 9927
Traceback (most recent call last):
File "../cissim/pdserve.py", line 316, in <module>
status = main()
File "../cissim/pdserve.py", line 260, in main
if '#' in line:
TypeError: a bytes-like object is required, not 'str'

It looks like it's been half-heartedly converted from 2 to 3, but untested. I'm assuming that either nobody uses it, or it's been fixed in place wherever it is used and the changes haven't been reflected back to the source.

== pdcall ==
(Incidentally, this was a bit messy to get working due to using pycurl, I had to {{c|apt install libcurl4-openssl-dev libssl-dev}} and {{c|pip install pycurl}} in order to get this to work on my Ubuntu machine - no idea what this will require on Mac, but be prepared for pain, given how little access we have.)

This can be used to call the server and test that it's working correctly.

Usage: pdcall <swimlane> <dialog> <requestfile> <replyfile>

The '<swimlane>' here is the port that the server is listening on.

This opens the request file and displays it using [[#pdedit|pdedit]]. After editing and saving, it posts the updated request to the server, captures the response and then opens ''that'' in pdedit too so that you can see (and, indeed, edit) the response, before saving to the output file.

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 ==
Calls a running ACS instance with an edited request, storing the response into the required output file.

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

This pops up a {{c|pdedit}} window to edit the request (actually saving the resultant file to the given location), then creates the
request by prepending the ACS input header, with the uppercased {{c|service}} embedded in it, to the input file contents.

The ACS input header is fixed (service aside) and has the following content:
<pre>
0ed1249b558f||True|101307| |DCP26PD350 |null|<service>|11606730|null|DWDDE662|2|1548331293|0|500|0|false|P|60|468|
</pre>

The full input is saved to a file in the current directory called {{c|<requestfile>.acs}}. The response from ACS is saved into the
provided {{c|replyfile}}.

== pdconvertall ==
Converts *.in files and corresponding *.out files from a source folder into a destination folder.

Usage: pdconvertall.py <sourcefolder> <targetfolder>

Note that the filename format is significant for this program and, natch, undocumented.
See [[#pdconvert formats|pdconvert formats]] for more details.

This scans the {{c|sourcefolder}} for all files matching {{c|*.in}} which ''do not'' start with the characters {{c|NPS}} and
have corresponding {{c|*.out}} files and 'converts' them to a text-based format for use with [[#pdserved|pdserved]].

The conversion of the input file is almost identical to the processing done by calling [[#pdutils|pdutils OUT]] with the
dialog and direction specified explicitly, though this program picks up that information from the embedded data in the filename.

The directory structure it creates is:
<outputfolder>
|- <dialog>
|- <rundate-yyyyMMdd>
|- <nino>.DATA

The format is text-based in the style of the [[#pdutils|pdutils OUT]] format. The [[#pdserved|pdserved]] server then reads
from the directory when it is processing the requests and determining the responses to return. The files can be modified in
place, or new files can be placed there. The server will pick up any external changes made to these files.

== pdconvertone ==
This is a thin wrapper around [[#pdconvertall|pdconvertall]] which works for a single input and output file. That is, it
still expects a {{c|*.in}} and corresponding {{c|*.out}} file to convert, and it emits the output into the directory
structure described in [[#pdconvertall|pdconvertall]].
Usage: pdconvertone.py <sourcespec> <targetfolder>

This calls {{c|pdconvertall}} with the single file identified by {{c|sourcespec}}. Note that if the file begins with the
characters {{c|NPS}} or there is no corresponding {{c|*.out}} file, it will be skipped

== pdconvert ==
Converts a single file into its text-based format, emitting the output to stdout.

Usage: pdconvert.py <pdfile>

This does not have the same restrictions as [[#pdconvertall|pdconvertall]] and [[#pdconvertone|pdconvertone]] - i.e.
it does not require corresponding {{c|*.in}} and {{c|*.out}} files, though the given file's filename must be one of those.
It will still not work for NPS files (though, unlike the above programs, it will try and probably crash and burn in the
attempt).

== pddata ==
''Library file.''

This has a load of functions in it, only some of which I understand.
The main one appears to be {{c|getninodata}} which, typical cissim style, takes 10 arguments (interrobang?!) and has...
well, ''some'' documentation which concentrates on one or two arguments and expects a fairly solid understanding of
what it's doing before you start reading.

I'm going to have to come back to this to try and grasp it.

'''Note:''' This technically can be executed, but it looks like the stuff in the main call is just development stuff - testing
other functions and such like.

== pddump ==
This dumps the data from the given (base64-encoded EBCDIC) file to the console in text form with square brackets to enclose
the data values. Note: This uses the [[#pdconvert formats|pdconvert format]] for the filename.

Usage: pddump.py <pdfile>

This is a call to [[#DUMP|pdutils DUMP]] which takes the dialog / direction arguments from the filename
format rather than requiring them to be stated explicitly.

== pdout ==
This dumps the data from the given (base64-encoded EBCDIC) file to the console in text form with square brackets to enclose
the data values. Note: This uses the [[#pdconvert formats|pdconvert format]] for the filename.

Usage: pdout.py <pdfile>

This is a call to [[#OUT|pdutils OUT]] which takes the dialog / direction arguments from the filename

== pdparams ==
''Library file.''

Contains a single function: {{c|processparams}}. This function also exists in [[#pdutils|pdutils]], and it looks like that
one is used but this one is not. I presume it's obsolete, though there's no indication of that in the code.

'''Deprecated?'''

== pdproxy ==
A very straightforward proxy which writes the request and response of any CIS calls made to it to files in the current
directory.

Usage: pdproxy <swimlane> <configfile> <folder> [<port>]

The swimlane determines whether the 'real' CIS is called or whether the 'SIM' is called. Basically, if the {{c|swimlane}}
argument is in the ranges: 14-15 or 17-28 (both inclusive), onward calls from the proxy will go to CIS proper. Any other
value is treated as the port that the simulator is listening on and it will be connected to using that port number.

== pdreadall ==
Reads all registered dialogs and calls them for the specified NINo and optional surname.

Usage: pdreadall <swimlane> <paramfile> <folder> <nino> [<surname>]

== pdreadoneedit ==
Calls a specified dialog in CIS (or a CIS simulator) for a given NINo and optional surname. This allows the editing of
the record to be sent in the request before the call is made. The input and output files are created (I ''think'') in
the current directory with the appropriate filename format.

Usage: pdreadoneedit <swimlane> <paramfile> <dialog> <nino> [<surname>]

== pdreadone ==
Calls a specified dialog in CIS (or a CIS simulator) for a given NINo and optional surname. This does not allow the
editing of the record to be sent in the request before the call is made. The input and output files are created (I
''think'') in the current directory with the appropriate filename format.

Usage: pdreadone <swimlane> <paramfile> <dialog> <nino> [<surname>]

== pdscreen ==
''Library file.''

This file contains a single class '{{c|Textbox}}' which provides the editing widget used in [[#pdedit|pdedit]] to
edit a value in a record file.

== pdserved ==
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.

== pdservedt ==
[[#pdserved|pdserved]] with a {{c|process_wait()}} function, which loads the timing data from the hardcoded location
at {{c|../serve/transtimes.py}}. Not ideal - it requires running the program from a specific directory, and, of course,
this is undocumented (as far as I can see anyway).

The timing data is a map of timings against dialog; the example in the code is:
<pre>
# timings are a list, first tuple is times to cycle through, rest are exceptional count/time pairs
# 'CP650_1151_R_RPLY': [(0.15, 0.25, 0.21, 0.17, 0.20, 0.16), (20, 2.3), (100, 28)],
</pre>
Basically, it will cycle through the first tuple of timings, except when the count for a given dialog reaches the
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.

'''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 ==
This is [[#pdserve|pdserve]] with more NPS handling (and fixed for Python3).

The NPS changes in here appear to be included in [[#pdserved|pdserved]] too, so this and [[#pdserve|pdserve]], at
first glance, would seem to be obsolete.

== pdshow ==
Shows and edits a base64-encoded file, extracting the dialog and direction from the filename.

Usage: pdshow.py <pdfile>

This is a wrapper around a call to [[#pdedit|pdedit]] which extracts the dialog and direction from the filename,
rather than needing it specified explicitly.

== 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 ==
This is [[#pdstub|pdstub]] with a {{c|process_wait()}} function, which works exactly like the same function in
[[#pdservedt|pdservedt]].

== pdstubtt ==
This is [[#pdstubt|pdstubt]] with a multi-threaded HTTP server. It's a fairly trivial change to the code; I haven't
looked through it to see if there are any thread localisation issues in there - I'm assuming not, because this is
being used as is at the moment, and that would probably have been noticed by now.

This seems to me to be the most mature of the pdstub implementations - multithreading the server is a no-brainer,
in my humble, and the timings can be ignored. It still has the problem of a hardcoded timing config, but that
shouldn't be too hard to fix in a less fragile manner.

== pdtux ==
A Tuxedo server which advertises a few tux operations, namely:
* ping
* DCI913
* DCI923
* VMERCIS
* RESETCOUNTER

This extracts the data out of the request packet and gets the data using [[#pddata|pddata.getninodata()]],
returning the resultant data (the whole thing for DCI calls, separated CIS header and W90 header for PDD calls).

There are no arguments to this program, but it does require the installation of the 'tuxedo' python module.

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

== certs ==
''Library file''

Holds the paths to the various certificates used within cissim. 2 groups of cert and cacert files for connecting to
DCI and PD; 2 groups of cert and private key files for serving.

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

== checkport ==
''Redundant''

Checks if it's possible to connect to {{c|localhost:9127}}. That's it really.

Basically, a python version of:
netstat -nap | grep ':9127.*LISTEN'

== dci9n3rec ==
''Library file''

Technically, this can be called from the command line, but it seems a bit pointless. It appears to read in a file
called 'in' in the current directory and, uh, loads it into a DCI9n3 record structure and prints it. I guess it's
for testing purposes.

Anyway, this contains the definition of a DCI913 or DCI923 record, packed to byte alignment for the fields, with
the 12 fields and their sizes defined as fixed length byte arrays.

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

== extractodis ==
''Executable''

Usage: extractodis.py <log_filename> [<PID>] [<starttime>] [<endtime>]

This is completely out there. So. It takes the filename and creates 3 shell scripts with names based on it, which
perform some function on the payload (base64-encoded ASCII). These scripts are:
* {{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>.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),
it's just a very odd way of doing things.

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|pdserved]] and beyond; the pddb output is used in the original
[[#pdserve|pdserve]] program too. It's still valid for the 'write.sh', I guess, but I suspect that's all.

== fpcapprec ==
''Library file''

{{obsolete}}

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

== getfieldoffset ==
''Test file''

{{obsolete}}

I'm pretty sure this is just testing that the [[#pdlayouts.pd|pdlayouts.getdialogfieldoffset()]] method is working
correctly.

== key ==
''Library file''

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
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|pdscreen]] file.

== loadninos ==
''Library File'' and ''Executable''

Usage: loadninos.py <office-file>

Used in [[#pdstub|pdstub]] and its variants.

Loads NINOs from a CSV file (actually looks like a 'Whitespace-separated variables' style file, though it has a
name of {{c|csvfile}} within the code). This looks for input in the form:
<pre>
SVC Office
JSOV 109809
JSRZ 107476
JSFP 107038
JSLH 103401
JSKR 103838
JSLF 102636
JSGR 102805
JSRT 100598
</pre>
The above example is half-inched from the code. The code is ferociously simplistic, but I guess it does the job.

Anyway, it takes the 'Office' from the lines in the 'CSV' file, strips the leading digit from it, then looks for
another 'csv' file with that office number as a filename, in the same directory as the provided CSV file, so the
above will look for '09809.csv', '07476.csv' etc. It will load that file, taking the first 8 chars of each line
as a NINo and then maps the office to that NINo, such that each NINo has the office number of the file that it
was loaded from mapped against it.

This is used in [[#pdstub|pdstub]] to get the office for a particular NINo, which is then used as part of the
response in a DCI913 call. The stub loads the NINos using this function passing the {{c|OFFICECSVFILE}} config
parameter value to load them from. It doesn't handle errors well, but I guess once it's running, you don't
change it that much.

== logextract ==
''Executable''

Usage: logextract.py <logfile>

Extracts a {{c|DCI913CopyRecord}} from a logfile. It's a bit hacky - in the middle of it, it does some strange
stuff with the string '127.0.0.1'; I presume the logfile isn't really designed for extracting records from and
so this has to hardcode some messing around into it. It's very fragile - logfiles aren't typically structured
output (or, at least, not structured in this way).

== npsload ==
''Executable'' - this is an executable only; no part of it is called by other programs / libraries.

Usage: npsload <folder> <csvfile> <listfile>

This loads the {{c|csvfile}} from {{c|folder}} (i.e. the file is just the filename, not the {{c|/path/to/file}}),
and writes all output, including the {{c|listfile}} in the same folder.

The CSV file is defined as:
Entry/ies Description
1 NINo
2 Surname
3 Office
4 LOP 25x Past
5-20 NUBS2 record x 4
21-36 LOP record x 4
37 Data not found flag
38 BFM Return Code
39 RDS Code

Each NUBS2 record and LOP record is made up of 4 comma-separated entries, with the fields:
Entry Description
1 Year
2 x25
3 x50
4 Priority

This program loops through all the NINo entries, and writes an XML file for each one, calling it {{c|NPSrply.<nino>.xml}},
adding an entry into the {{c|listfile}} for each file it created. It adds a final 'NINO not found' entry to the listfile
and exits.

== paths ==
''Library file''

Contains the paths used for calls to PD, DCI and NPS, as well as a few functions which operate on and around those paths.

This is used liberally throughout the rest of the CISSim suite.

== 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 ==
''Executable''

I have no idea what this is trying to do. It's messing around with servers and message queues, but I'm a bit lost.

== sslutils ==
''Library file''

Contains functions to call servers using SSL certificates. Used in [[#pdacs|pdacs]], [[#pdcall|pdcall]], [[#pdproxy|pdproxy]]
and [[#teststub|teststub]]

== temp ==
{{obsolete}}

Seems to be a copy of [[#pdserved|pdserved]] with some testing code in there.

== teststub ==
{{obsolete}}

Tests connecting to the CIS Sim using curl and a socket. Prints things. Not particularly useful.

== utils ==
''Library file''

{{obsolete}}

A variety of utility functions; apparently not used anywhere.

== vmeutils ==
''Library file'' and ''Executable''

Usage: vmeutils <D/B> <date>

Some VME date functions and a small utility executable to convert a date into a VME date ({{c|'B'}}, obviously) or
a VME date into a date ({{c|'D'}}). A 'VME date' in this context is the number of days since 29/02/1852.

== w80construct ==
''Library file''

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.

Anyway, this contains the definition of a W80 record, packed to byte alignment for the fields, with the various fields
and their sizes defined mostly as fixed length byte arrays, though there are a few integer and long integer fields
defined too - these will be compiler-dependent, so I guess that's how the tux that it's interfacing with/mocking
works too?

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

= Files in pdlayouts =

== pdlayouts/PDM ==
The 'PD Map' contains the fields used in the CIS header and the W80 PD header, including their name, data type and length and
an optional 'style' type argument which provides metadata for the field, ''eg.'' {{c|nino8}} indicates the first 8 chars of
a NINo, {{c|runtime8}} indicates that it contains a time in the format {{c|%H%M%S%f}}, {{c|vmedate}} indicates that the field
contains a 'VME date', ie. the number of days since 29/02/1852.

These 'style' arguments are used in {{c|pdutils.makerequestfile}} to autopopulate various fields for input based on the static
'RUNDATE' parameter value.

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

2021-10-19T08:26:49Z

Stuart: Filled out pretty much everything.

<noinclude>{{nav/ACS Test Harness}}</noinclude>
There are many command line tools to do various things within the CISSIM / proxy / data management / testing stub / kitchen sink application.

This page tries to exhaustively go through all of them. It fails. But it continues to try.
= File formats =
There are a few file formats used here.

== base64-ebcdic ==
EBCDIC data and binary fields encoded into base64.

This is the form for most PD calls - the content is a record whose definition is held elsewhere (in COBOL copybook-ish form)

Used as input and output to/from [[#pdutils|pdutils]] and [[#pdedit|pdedit]].

== base64-ascii ==
ASCII data and binary fields encoded into base64.

Just like [[#base64-ebcdic|base64-ebcdic]] except the text fields are encoded into ASCII rather than EBCDIC.

This can be used as input to [[#pdutils|pdutils]] when using the {{c|CONVERT2E}} option to convert it to [[#base64-ebcdic|base64-ebcdic]], and output from [[#pdutils|pdutils]] using the {{c|CONVERT2A}} option.

= Filename format =
Some of the following utilities expect the filename to be in one of a number of specific formats. They use this
format to embed information about the transaction that the file represents, later extracted by the programs to look up
related data and/or structures.

== pdconvert formats ==
The [[#pdconvert|pdconvert]], [[#pdconvertone|pdconvertone]] and [[#pdconvertall|pdconvertall]] programs expect
the files to be named in one of two dot-separated formats; one with 4 'parts', one with any other number of 'parts'
as long they number at least 3. The 4 part format is represented by the regex:

^(?P<dialognum>[^.]{0,6})\.[^.]*\.[^.]*\.(?P<direction>in|out)$

eg. "DCI908.NINO.STUB.out"

The 4 dot-separated parts indicate that this is an 'R' (read) mode transaction. A suffix of 'in' indicates a 'RQST' direction,
'out' indicates a 'RPLY' direction. The dialog is extracted as the first 6 chars of the first part, the mode and the direction
separated by underscores, so the above example would yield:
DCI908_R_RQST

The 'any number above 2, except 4' format (?) extracts more information from the filename:
^(?P<dialognum>[^.]*)\.[^.]{3}(?P<messageid>[^.]{4})(?P<txnmode>[^.]).*\.(?P<direction>in|out)$

eg. "PD375.CIS6084RCURRINT.153250.634934c5c8d6.in"

This builds the dialog and transaction mode from the filename. The direction is mapped to 'RQST' or 'RPLY' where the filename
has 'in' or 'out', and the dialog is built up as: {{c|<dialognum>_<messageid>_<txnmode>_<direction>}}. The above example
would end up with the dialog:
PD375_6084_R_RQST

= Programs =

== pdutils ==
Primarily a library file, used throughout various calls from the daemon programs as well as other utilities.
It can, however, also be called directly from the command line.

Usage: pdutils <DUMP/OUT/SAVE/CONVERT2E/CONVERT2A> <dialog> <RQST/RPLY> <requestfile/replyfile>

Note that SAVE requires redirected input from an ASCII text string, such as '< <datafile>'
and that CONVERT requires redirected input from B64 encoded ASCII data '< <datafile>'

=== DUMP ===
Dumps the structure of a request found in a base64-encoded EBCDIC file out to the console.

This puts ''everything'' out - ie. all the fields, the fillers and the groups. The values are wrapped into square brackets the appropriate size for capturing the data for the field. Binary values have leading zeroes trimmed; all char values are displayed as found.

It prefixes the field with the data structure (''eg'' B4 for binary 4 bytes; X16 for char 16 bytes; N2 for numeric char 2 bytes).

It suffixes the value with the hex value found for the field, separated into space-separated octets, wrapped in parantheses.

=== OUT ===
Dumps the structure of a request found in a base64-encoded EBCDIC file out to the console.

This only puts out the fields and fillers. The values are wrapped into square brackets the appropriate size for capturing the data for the field. Binary values have leading zeroes trimmed; all char values are displayed as found.

=== SAVE ===
'''Note:''' this doesn't work on Windows, because it uses [https://docs.python.org/3/library/select.html#select.select select.select()] to ensure that stdin is available, and that function only works on file descriptors on POSIX systems.

Uses a 'hidden' fifth argument, i.e. it expects the input file to be provided on stdin. The {{c|<requestfile/replyfile>}} argument is, in this case, an ''output'' file.

I have tweaked the code to work in Windows and... I don't really know what this does, i.e. I don't know what format the input file is expected to be in. It's not the same as the 'requestfile/replyfile' used for DUMP and OUT, because that fails with the exception message: ''invalid literal for int() with base 10: 'AAAAMMPJ4' ''

=== CONVERT2E ===
'''Note:''' this doesn't work on Windows, because it uses [https://docs.python.org/3/library/select.html#select.select select.select()] to ensure that stdin is available, and that function only works on file descriptors on POSIX systems.

Uses a 'hidden' fifth argument, i.e. it expects the input file to be provided on stdin. The {{c|<requestfile/replyfile>}} argument is, in this case, an ''output'' file.

This converts input from stdin, in base64-encoded ASCII record format to the output file, in base64-encoded EBCDIC record format. This is the exact mirror of {{c|CONVERT2A}}.

Note: This only works for PD data, not DCI or NPS (which are only ever required in ASCII-based encodings).

=== CONVERT2A ===
'''Note:''' this doesn't work on Windows, because it uses [https://docs.python.org/3/library/select.html#select.select select.select()] to ensure that stdin is available, and that function only works on file descriptors on POSIX systems.

Uses a 'hidden' fifth argument, i.e. it expects the input file to be provided on stdin. The {{c|<requestfile/replyfile>}} argument is, in this case, an ''output'' file.

This converts input from stdin, in base64-encoded EBCDIC record format to the output file, in base64-encoded ASCII record format. This is the exact mirror of {{c|CONVERT2A}}.

Note: This only works for PD data, not DCI or NPS (which are only ever required in ASCII-based encodings).

== pdedit ==
Edits the PD and DCI call data via a curses interface, using the COBOL data layouts for the calls.

Usage: pdedit <dialog> <RQST/RPLY> <sourcefile> <destfile>

The 'sourcefile' in this case is the same as the 'requestfile/replyfile' provided in pdutils, that is, a file containing base64-encoded EBCDIC data. The 'destfile' is in the same format with the changes applied (assuming that you save inside pdedit).

Intriguingly, it appears to ignore the 'RQST/RPLY' in the dialog and effectively overwrites it with the RQST/RPLY argument given to the program.
Not really sure why... that dialog is a bit of a hack, really, I suspect just to avoid multiple keys or too much structure in the config.

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.

== pddb ==
Creates a database entry which effectively maps a response file onto a request.

Usage: pddb <dialog> <sourcefile> <destfile> <EBCDIC/ASCII>

The output is in the form:
<dialog>:<response-file>:<input-field-name=value[;...]>

So, for a PD350 1151 request, you might see something like:
$ python cissim/pddb.py PD350_1151_R_RQST requests/pd350-request-e messages/PD350.CIS1151RSTRTDIA.AASTUB.out EBCDIC
PD350_1151_R_RQST:PD350.CIS1151RSTRTDIA.AASTUB.out:H1151-NINO=ST000001;H1151-NINO-SFX-TX=A;H1151-RQST-DSS-DAYS=20190213;H1151-RQST-DIA-ID=PD350 ;H1151-RQST-USR-NS-LVL=0000;H1151-RQST-USR-LS-LVL=0000;H1151-RQST-USR-BUS-SYS-NO=43;H1151-DEPT-ID-TP=1;H1151-OFF-LOC-NO=04710;H1151-RQST-SPCFC-BUS-TP=85;

These entries can be appended into a single file, with each entry on a separate line and work together to a form a readonly database of sorts, which the server can use to lookup the response to use based on the values of the inputs provided in the request.

== pdserve ==
This is what uses the given 'database' files from pddb to serve the data based on the requests.

Usage: pdserve <configfile> [<port>]

It takes a config file which is effectively made up of paths to the 'databases' built up using pddb along with an (optional) SSL flag. Each pddb line in the config is something like:
<path-to-db-file>:<folder>

So, for example:

configfile.ja030
SSL=N
pdbase/JA030_01.CIS.txt:pdbase
pdbase/JA030_02.CIS.txt:pdbase
pdbase/JA030_99.CIS.txt:pdbase

pdserve will expect to find the response files with the names defined in the 'database' within the folder specified in the config, so you could have multiple entries here pointing to different databases.

The 'port' here is the port it will listen on. This is analogous to a 'swimlane' (''<sigh>'') and, indeed, the terms are used interchangeably in some places. The default port value used is ''9127''.

The recommended way of running this is using {{c|nohup}} so that you can exit the shell and it will continue to run... something like:
nohup python pdserve.py configfile.ja030 9130 >ja030.log &

... and of course, the only way to kill it after doing that is by identifying the process that's running and using the {{c|kill}} command.

Final thing. Quite important. 
The version I have doesn't work.

In Python 2:
$ python2 ../cissim/pdserve.py pdserve.test.config 9927
File "../cissim/pdserve.py", line 68
print(s.server_version, end=' ')
^
SyntaxError: invalid syntax

In Python 3:
$ python ../cissim/pdserve.py pdserve.test.config 9927
Traceback (most recent call last):
File "../cissim/pdserve.py", line 316, in <module>
status = main()
File "../cissim/pdserve.py", line 260, in main
if '#' in line:
TypeError: a bytes-like object is required, not 'str'

It looks like it's been half-heartedly converted from 2 to 3, but untested. I'm assuming that either nobody uses it, or it's been fixed in place wherever it is used and the changes haven't been reflected back to the source.

== pdcall ==
(Incidentally, this was a bit messy to get working due to using pycurl, I had to {{c|apt install libcurl4-openssl-dev libssl-dev}} and {{c|pip install pycurl}} in order to get this to work on my Ubuntu machine - no idea what this will require on Mac, but be prepared for pain, given how little access we have.)

This can be used to call the server and test that it's working correctly.

Usage: pdcall <swimlane> <dialog> <requestfile> <replyfile>

The '<swimlane>' here is the port that the server is listening on.

This opens the request file and displays it using [[#pdedit|pdedit]]. After editing and saving, it posts the updated request to the server, captures the response and then opens ''that'' in pdedit too so that you can see (and, indeed, edit) the response, before saving to the output file.

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 ==
Calls a running ACS instance with an edited request, storing the response into the required output file.

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

This pops up a {{c|pdedit}} window to edit the request (actually saving the resultant file to the given location), then creates the
request by prepending the ACS input header, with the uppercased {{c|service}} embedded in it, to the input file contents.

The ACS input header is fixed (service aside) and has the following content:
<pre>
0ed1249b558f||True|101307| |DCP26PD350 |null|<service>|11606730|null|DWDDE662|2|1548331293|0|500|0|false|P|60|468|
</pre>

The full input is saved to a file in the current directory called {{c|<requestfile>.acs}}. The response from ACS is saved into the
provided {{c|replyfile}}.

== pdconvertall ==
Converts *.in files and corresponding *.out files from a source folder into a destination folder.

Usage: pdconvertall.py <sourcefolder> <targetfolder>

Note that the filename format is significant for this program and, natch, undocumented.
See [[#pdconvert formats|pdconvert formats]] for more details.

This scans the {{c|sourcefolder}} for all files matching {{c|*.in}} which ''do not'' start with the characters {{c|NPS}} and
have corresponding {{c|*.out}} files and 'converts' them to a text-based format for use with [[#pdserved|pdserved]].

The conversion of the input file is almost identical to the processing done by calling [[#pdutils|pdutils OUT]] with the
dialog and direction specified explicitly, though this program picks up that information from the embedded data in the filename.

The directory structure it creates is:
<outputfolder>
|- <dialog>
|- <rundate-yyyyMMdd>
|- <nino>.DATA

The format is text-based in the style of the [[#pdutils|pdutils OUT]] format. The [[#pdserved|pdserved]] server then reads
from the directory when it is processing the requests and determining the responses to return. The files can be modified in
place, or new files can be placed there. The server will pick up any external changes made to these files.

== pdconvertone ==
This is a thin wrapper around [[#pdconvertall|pdconvertall]] which works for a single input and output file. That is, it
still expects a {{c|*.in}} and corresponding {{c|*.out}} file to convert, and it emits the output into the directory
structure described in [[#pdconvertall|pdconvertall]].
Usage: pdconvertone.py <sourcespec> <targetfolder>

This calls {{c|pdconvertall}} with the single file identified by {{c|sourcespec}}. Note that if the file begins with the
characters {{c|NPS}} or there is no corresponding {{c|*.out}} file, it will be skipped

== pdconvert ==
Converts a single file into its text-based format, emitting the output to stdout.

Usage: pdconvert.py <pdfile>

This does not have the same restrictions as [[#pdconvertall|pdconvertall]] and [[#pdconvertone|pdconvertone]] - i.e.
it does not require corresponding {{c|*.in}} and {{c|*.out}} files, though the given file's filename must be one of those.
It will still not work for NPS files (though, unlike the above programs, it will try and probably crash and burn in the
attempt).

== pddata ==
''Library file.''

This has a load of functions in it, only some of which I understand.
The main one appears to be {{c|getninodata}} which, typical cissim style, takes 10 arguments (interrobang?!) and has...
well, ''some'' documentation which concentrates on one or two arguments and expects a fairly solid understanding of
what it's doing before you start reading.

I'm going to have to come back to this to try and grasp it.

'''Note:''' This technically can be executed, but it looks like the stuff in the main call is just development stuff - testing
other functions and such like.

== pddump ==
This dumps the data from the given (base64-encoded EBCDIC) file to the console in text form with square brackets to enclose
the data values. Note: This uses the [[#pdconvert formats|pdconvert format]] for the filename.

Usage: pddump.py <pdfile>

This is a call to [[#DUMP|pdutils DUMP]] which takes the dialog / direction arguments from the filename
format rather than requiring them to be stated explicitly.

== pdout ==
This dumps the data from the given (base64-encoded EBCDIC) file to the console in text form with square brackets to enclose
the data values. Note: This uses the [[#pdconvert formats|pdconvert format]] for the filename.

Usage: pdout.py <pdfile>

This is a call to [[#OUT|pdutils OUT]] which takes the dialog / direction arguments from the filename

== pdparams ==
''Library file.''

Contains a single function: {{c|processparams}}. This function also exists in [[#pdutils|pdutils]], and it looks like that
one is used but this one is not. I presume it's obsolete, though there's no indication of that in the code.

'''Deprecated?'''

== pdproxy ==
A very straightforward proxy which writes the request and response of any CIS calls made to it to files in the current
directory.

Usage: pdproxy <swimlane> <configfile> <folder> [<port>]

The swimlane determines whether the 'real' CIS is called or whether the 'SIM' is called. Basically, if the {{c|swimlane}}
argument is in the ranges: 14-15 or 17-28 (both inclusive), onward calls from the proxy will go to CIS proper. Any other
value is treated as the port that the simulator is listening on and it will be connected to using that port number.

== pdreadall ==
Reads all registered dialogs and calls them for the specified NINo and optional surname.

Usage: pdreadall <swimlane> <paramfile> <folder> <nino> [<surname>]

== pdreadoneedit ==
Calls a specified dialog in CIS (or a CIS simulator) for a given NINo and optional surname. This allows the editing of
the record to be sent in the request before the call is made. The input and output files are created (I ''think'') in
the current directory with the appropriate filename format.

Usage: pdreadoneedit <swimlane> <paramfile> <dialog> <nino> [<surname>]

== pdreadone ==
Calls a specified dialog in CIS (or a CIS simulator) for a given NINo and optional surname. This does not allow the
editing of the record to be sent in the request before the call is made. The input and output files are created (I
''think'') in the current directory with the appropriate filename format.

Usage: pdreadone <swimlane> <paramfile> <dialog> <nino> [<surname>]

== pdscreen ==
''Library file.''

This file contains a single class '{{c|Textbox}}' which provides the editing widget used in [[#pdedit|pdedit]] to
edit a value in a record file.

== pdserved ==
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.

== pdservedt ==
[[#pdserved|pdserved]] with a {{c|process_wait()}} function, which loads the timing data from the hardcoded location
at {{c|../serve/transtimes.py}}. Not ideal - it requires running the program from a specific directory, and, of course,
this is undocumented (as far as I can see anyway).

The timing data is a map of timings against dialog; the example in the code is:
<pre>
# timings are a list, first tuple is times to cycle through, rest are exceptional count/time pairs
# 'CP650_1151_R_RPLY': [(0.15, 0.25, 0.21, 0.17, 0.20, 0.16), (20, 2.3), (100, 28)],
</pre>
Basically, it will cycle through the first tuple of timings, except when the count for a given dialog reaches the
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.

'''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 ==
This is [[#pdserve|pdserve]] with more NPS handling (and fixed for Python3).

The NPS changes in here appear to be included in [[#pdserved|pdserved]] too, so this and [[#pdserve|pdserve]], at
first glance, would seem to be obsolete.

== pdshow ==
Shows and edits a base64-encoded file, extracting the dialog and direction from the filename.

Usage: pdshow.py <pdfile>

This is a wrapper around a call to [[#pdedit|pdedit]] which extracts the dialog and direction from the filename,
rather than needing it specified explicitly.

== 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 ==
This is [[#pdstub|pdstub]] with a {{c|process_wait()}} function, which works exactly like the same function in
[[#pdservedt|pdservedt]].

== pdstubtt ==
This is [[#pdstubt|pdstubt]] with a multi-threaded HTTP server. It's a fairly trivial change to the code; I haven't
looked through it to see if there are any thread localisation issues in there - I'm assuming not, because this is
being used as is at the moment, and that would probably have been noticed by now.

This seems to me to be the most mature of the pdstub implementations - multithreading the server is a no-brainer,
in my humble, and the timings can be ignored. It still has the problem of a hardcoded timing config, but that
shouldn't be too hard to fix in a less fragile manner.

== pdtux ==
A Tuxedo server which advertises a few tux operations, namely:
* ping
* DCI913
* DCI923
* VMERCIS
* RESETCOUNTER

This extracts the data out of the request packet and gets the data using [[#pddata|pddata.getninodata()]],
returning the resultant data (the whole thing for DCI calls, separated CIS header and W90 header for PDD calls).

There are no arguments to this program, but it does require the installation of the 'tuxedo' python module.

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

== certs ==
''Library file''

Holds the paths to the various certificates used within cissim. 2 groups of cert and cacert files for connecting to
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
in [[#sslutils.py|sslutils]].

== checkport ==
''Redundant''

Checks if it's possible to connect to {{c|localhost:9127}}. That's it really.

Basically, a python version of:
netstat -nap | grep ':9127.*LISTEN'

== dci9n3rec ==
''Library file''

Technically, this can be called from the command line, but it seems a bit pointless. It appears to read in a file
called 'in' in the current directory and, uh, loads it into a DCI9n3 record structure and prints it. I guess it's
for testing purposes.

Anyway, this contains the definition of a DCI913 or DCI923 record, packed to byte alignment for the fields, with
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
record is [[#w80construct.py|w80construct]]

== extractodis ==
''Executable''

Usage: extractodis.py <log_filename> [<PID>] [<starttime>] [<endtime>]

This is completely out there. So. It takes the filename and creates 3 shell scripts with names based on it, which
perform some function on the payload (base64-encoded ASCII). These scripts are:
* {{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>.db.sh}}: to write the transaction to the 'database' for serving (calling [[#pddb.py|pddb.py]])

Aside from some very ropey python issues (mix of tabs and spaces in leading whitespace - very verboten in python),
it's just a very odd way of doing things.

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
[[#pdserve.py|pdserve]] program too. It's still valid for the 'write.sh', I guess, but I suspect that's all.

== fpcapprec ==
''Library file''

{{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.

== getfieldoffset ==
''Test file''

{{obsolete}}

I'm pretty sure this is just testing that the [[#pdlayouts.pd|pdlayouts.getdialogfieldoffset()]] method is working
correctly.

== key ==
''Library file''

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

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
deserve its own file; any home-grown key values could go in the [[#pdscreen.py|pdscreen]] file.

== loadninos ==
''Library File'' and ''Executable''

Usage: loadninos.py <office-file>

Used in [[#pdstub|pdstub]] and its variants.

Loads NINOs from a CSV file (actually looks like a 'Whitespace-separated variables' style file, though it has a
name of {{c|csvfile}} within the code). This looks for input in the form:
<pre>
SVC Office
JSOV 109809
JSRZ 107476
JSFP 107038
JSLH 103401
JSKR 103838
JSLF 102636
JSGR 102805
JSRT 100598
</pre>
The above example is half-inched from the code. The code is ferociously simplistic, but I guess it does the job.

Anyway, it takes the 'Office' from the lines in the 'CSV' file, strips the leading digit from it, then looks for
another 'csv' file with that office number as a filename, in the same directory as the provided CSV file, so the
above will look for '09809.csv', '07476.csv' etc. It will load that file, taking the first 8 chars of each line
as a NINo and then maps the office to that NINo, such that each NINo has the office number of the file that it
was loaded from mapped against it.

This is used in [[#pdstub|pdstub]] to get the office for a particular NINo, which is then used as part of the
response in a DCI913 call. The stub loads the NINos using this function passing the {{c|OFFICECSVFILE}} config
parameter value to load them from. It doesn't handle errors well, but I guess once it's running, you don't
change it that much.

== logextract ==
''Executable''

Usage: logextract.py <logfile>

Extracts a {{c|DCI913CopyRecord}} from a logfile. It's a bit hacky - in the middle of it, it does some strange
stuff with the string '127.0.0.1'; I presume the logfile isn't really designed for extracting records from and
so this has to hardcode some messing around into it. It's very fragile - logfiles aren't typically structured
output (or, at least, not structured in this way).

== npsload ==
''Executable'' - this is an executable only; no part of it is called by other programs / libraries.

Usage: npsload <folder> <csvfile> <listfile>

This loads the {{c|csvfile}} from {{c|folder}} (i.e. the file is just the filename, not the {{c|/path/to/file}}),
and writes all output, including the {{c|listfile}} in the same folder.

The CSV file is defined as:
Entry/ies Description
1 NINo
2 Surname
3 Office
4 LOP 25x Past
5-20 NUBS2 record x 4
21-36 LOP record x 4
37 Data not found flag
38 BFM Return Code
39 RDS Code

Each NUBS2 record and LOP record is made up of 4 comma-separated entries, with the fields:
Entry Description
1 Year
2 x25
3 x50
4 Priority

This program loops through all the NINo entries, and writes an XML file for each one, calling it {{c|NPSrply.<nino>.xml}},
adding an entry into the {{c|listfile}} for each file it created. It adds a final 'NINO not found' entry to the listfile
and exits.

== paths ==
''Library file''

Contains the paths used for calls to PD, DCI and NPS, as well as a few functions which operate on and around those paths.

This is used liberally throughout the rest of the CISSim suite.

== 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 ==
''Executable''

I have no idea what this is trying to do. It's messing around with servers and message queues, but I'm a bit lost.

== sslutils ==
''Library file''

Contains functions to call servers using SSL certificates. Used in [[#pdacs|pdacs]], [[#pdcall|pdcall]], [[#pdproxy|pdproxy]]
and [[#teststub|teststub]]

== temp ==
{{obsolete}}

Seems to be a copy of [[#pdserved|pdserved]] with some testing code in there.

== teststub ==
{{obsolete}}

Tests connecting to the CIS Sim using curl and a socket. Prints things. Not particularly useful.

== utils ==
''Library file''

{{obsolete}}

A variety of utility functions; apparently not used anywhere.

== vmeutils ==
''Library file'' and ''Executable''

Usage: vmeutils <D/B> <date>

Some VME date functions and a small utility executable to convert a date into a VME date ({{c|'B'}}, obviously) or
a VME date into a date ({{c|'D'}}). A 'VME date' in this context is the number of days since 29/02/1852.

== w80construct ==
''Library file''

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

Anyway, this contains the definition of a W80 record, packed to byte alignment for the fields, with the various fields
and their sizes defined mostly as fixed length byte arrays, though there are a few integer and long integer fields
defined too - these will be compiler-dependent, so I guess that's how the tux that it's interfacing with/mocking
works too?

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

= Files in pdlayouts =

== pdlayouts/PDM ==
The 'PD Map' contains the fields used in the CIS header and the W80 PD header, including their name, data type and length and
an optional 'style' type argument which provides metadata for the field, ''eg.'' {{c|nino8}} indicates the first 8 chars of
a NINo, {{c|runtime8}} indicates that it contains a time in the format {{c|%H%M%S%f}}, {{c|vmedate}} indicates that the field
contains a 'VME date', ie. the number of days since 29/02/1852.

These 'style' arguments are used in {{c|pdutils.makerequestfile}} to autopopulate various fields for input based on the static
'RUNDATE' parameter value.

Template:Obsolete

2021-10-18T14:49:14Z

Stuart: First draft of the obsolete template.

<includeonly>Obsolete</includeonly><noinclude>
== Description ==
Template to flag something as obsolete with an optional explanation.

== Usage ==
Just including this template will write a highlighted 'Obsolete' label out in the current context.
It writes it out inline, so if you want it in its own paragraph in the context of the page, you must
create the paragraph for it to be in.

<nowiki>{{obsolete}}</nowiki>
will output
<div class="mw-code">
{{obsolete}}
</div>

<nowiki>This class is now {{obsolete}}</nowiki>
will output
<div class="mw-code">
This class is now {{obsolete}}
</div>

An optional parameter will add a 'title' to the word which can provide some contextual information
about the obsolescence of the target.
<nowiki>{{obsolete|Deprecated on 26/04/2019 because of reasons}}</nowiki>
will output
<div class="mw-code">
{{obsolete|Deprecated on 26/04/2019 because of reasons}}
</div>
(Hover over it to see the title text)

</noinclude>

Template:Strike

2021-10-18T14:43:17Z

Stuart: Usage -> Description

<includeonly><div style="display:inline; color:#777; cursor:default; text-decoration:line-through;" title="{{{2|}}}">{{{1}}}</div></includeonly><noinclude>
== Description ==
Template for striking out some text with an optional explanation

== Examples ==
The following examples will show how to use this template.

=== Basic Usage ===
The first parameter is the markup to show struck out.

<nowiki>{{strike|Task 1: Write usage notes for ''Strike'' template}}</nowiki>

will result in:

<div class="mw-code">
{{strike|Task 1: Write usage notes for ''Strike'' template}}
</div>

=== Tooltip Parameter ===
A second parameter gives a 'tooltip' active on the struck out content.

<nowiki>{{strike|Task 2: Explain how to use the 'hover' parameter|The second parameter will give a 'hover' tool tip on the text}}</nowiki>

would display:

<div class="mw-code">
{{strike|Task 2: Explain how to use the 'hover' parameter|The second parameter will give a 'hover' tool tip on the text}}
</div>

Hover over it to see the explanatory tooltip.

=== Complex Markup ===
You can put any wiki markup into the text to display, eg.

<nowiki>{{strike|
* This is a list
* of a number of
* elements, including
*# A numbered sublist
*# with only two elements|
List is now obsolete - actually wasn't much use in the first place}}</nowiki>

will display:

<div class="mw-code">
{{strike|
* This is a list
* of a number of
* elements, including
*# A numbered sublist
*# with only two elements|
List is now obsolete - actually wasn't much use in the first place}}
</div>

</noinclude>

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

2021-10-18T09:30:59Z

Stuart: Expanded on pdserved and pdstub

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

2021-10-15T12:32:53Z

Stuart: Updated with initial pdserve/pdstub findings

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

2021-10-14T20:52:08Z

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

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

2021-10-12T00:13:55Z

Stuart:

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

2021-10-11T15:48:20Z

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

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

2021-10-11T15:38:30Z

Stuart: /* pdserve */ Spacing

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

2021-10-11T15:38:08Z

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