I’m sure that all theses details would be pretty tedious to anyone else. But again this isn’t really a blog meant to hold other peoples interest…it’s a log for me.
As I said in this post “I’ve technically finished the MTM course but as long as I still have access to z/OS I would still like to work on the final challenge using the zowe extensions in the VS Code editor”. To be honest I’m not even sure I really understood the goal of that project. So I set my own goals. Since there is no right answer, I’ll just have to satisfy myself.
To summarize some of the things said about the final challenge…
Good Luck! Remember, Part 3 is not a race. You have until December 31.
Your ch15(get) will be executed to view the various reports.
The final challenge has no correct or incorrect answer.
Quality can win over quantity
The system utility uses REXX and the SDSF interfaces to generate reports. Consider all SDSF Menu selections as the SDSF interfaces. [Below is the SDSF Menu]
System Information Utility
Information requested:
- Report specific message identifier found in SYSLOG
- Report from System Information, SYS
- Report string found in SYSLOG
- Report TSO logons
- Report specific ID successful TSO logon
- Report display command executions
- Report test Enter report number
Reports can be from any of the SDSF interfaces. [Note: “can be from any” NOT…do them all]
At least 1 report you write must demonstrate ability to parse SYSLOG records. [Confusing: are they implying I should do more than 1 report?]
Familiarity with z/OS Message Format is needed to demonstrate you ability to parse SYSLOG records and create a report. A review of Chapter 1. Introduction in the z/OS Messages and Codes professional manual is a description of the z/OS Message Format and the records found in the SYSLOG.
You have the freedom to do what you want. The judges are looking for technical acumen applied to z/OS. Impress the judges with your best reports that show your acquired z/OS knowledge.
I assume part of the challenge involved understanding it. And while the instructions may have seemed perfectly clear to them they might not be to everyone.
Or perhaps parts were purposely left ambiguous to see how a student might react and interpret the problem.
In any job I have had there are ALWAYS times I may need to talk to a boss to clarify unclear instructions, to me.
So basically the way I attacked the challenge was to display “undefined” to menu items 4-6.
The 1st three had some code behind them, #7 was left open…hence my added “test”
The Main thing I wanted out of the challenge was…
1) to be able to paste a large amount of code, generated by Python, into The REXX code.
I figured out how to paste one screen full, but that’s too tedious for 400+ lines. So my plan to use the ZOWE extension in VS Code worked very well. I had a few responses in the Slack group that implied I could paste, which like I said I already found I could, however I doubt that you could paste more than a screen full of data into the ISPF editor, because Linux’s clipboard mechanism isn’t the same as ISPF’s.
I got my program to do maybe 80% of what I wanted, the finishing touches is just basic coding/debugging. Which I know I could do but why bother with the last 20% for a project that I’ve already received credit for and no one will review? IMHO the final challenge was meant mostly for the original intent of the course…for younger students to finish off 2019.
For me it was a good learning experience using VS Code and the superior, at least for me, development tools on Linux, augmented with something I was more familiar with…Python.