December 10, 2014
Recently, I’ve visited a Southern state of the US for a business trip. Among other topics, I’ve focused on the Test Lab management capabilities of RQM.
I remember that, during my initial grasp of this part of RQM, the information provided in various places (see the References section below) helped me a lot. Nonetheless I consider that it was not quick enough.
Maybe because I missed a synthetic view of the following aspects in a one-stop-table. Such document would aim at providing you both with a rapid comprehension of the features and a convenient communication medium around:
- The Test Lab Management assets
- Their associated definition
- From which artefact they could be created (*)
- What artifacts they could serve at creating (*)
- Whether they could serve (or not) as a basis for creating a Request or a Reservation
- Whether a view showing all the Reservations is available (or not)
As a consequence, I ended up creating the following table / cheat sheet:
CLICK to ENLARGE the table
This table revealed useful during discussions with customer. I hope this content could also help you:
- At speeding up your understanding of the currently available capabilities in RQM, and
- At facilitating the decision of the mapping between your own testing shop terminology with the RQM one.
(*): from the RQM GUI only here. REST APIs and other importer tools are excluded of the scope of this blog post.
(**): image borrowed from article: [devWorks] “Use RQM to manage lab assets in shared lab” (Nov 2013)
November 17, 2013
When digging further (or simply jumping) into Mainframe and z/OS world, one faces new terminology, concepts and tooling. Literature is pretty vast in the area and one could spend some time figuring out the right resource to consider…
As far as terminology is concerned, if you just need to understand a term, the “Glossary of z/OS terms and abbreviations” is certainly indicated. For a mainframe concept, you can check this InfoCenter entry and for a z/OS concept, this other Info Center entry
If you need a broader understanding (e.g. how the pieces articulate with each others, etc.) then the Redbooks/Redpapers targeting Mainframe and z/OS are good starting points.
In my personal experience during the last couple of months, I found the following content very useful. In the following tables, you’ll be one click away from the right material (in PDF format). While I’ve never taken time to read all of this content (at least not yet), I’ve referred to it in an “on demand” way, with a pre-established topic in mind for which I was interested by getting a clearer idea on.
Adding that “a picture is worth a thousand words“, so they say, I personally found the summary slides and architectural diagrams (generally located at the beginning of sections) particularly handy and enlightening. Enjoy !
[Redbooks] “ABCs of z/OS Systems Programming”
||Intro to z/OS and Storage concepts, TSO/E, ISPF, JCL
||z/OS Implementation and Maintenance
||Intro to DFSMS and Storage Management
||Communication Server, TCP/IP, and VTAM
||Base and Parallel Sysplex, Logger, GRS, Operations, ARM
||RACF, PKI, LDAP, Crypto, Kerberos and Firewall
||InfoPrint Server, LE, and SMP/E
||z/OS Problem Diagnosis
||z/OS, UNIX System Services
||Intro to Z, LPAR, and HCD
||Capacity planning, performance management, RMF, and SMF
May 6, 2013
As part of Jumpstart team, I found myself answering customer questions about the reporting capabilities in CLM. As a result of this, last year, I’ve consolidated and shared information/guidance on the subject through a MindMap (see blog post: “Get things clear about the CLM 2012 reporting capabilities“). Some of our customers provided me with great feedback (which is still welcome BTW !).
As an assiduous reader of Jazz.net forum, I see that questions like the following are common:
“I want to create a RTC/RRC/RTC/CLM report with this information plus this other information…. how should I proceed ?“.
Say 90% of the time, a pragmatical 1st answer advise users to check the existing/OOTB reports available in CLM. Then, say in half of the cases, directions for creating custom reports are provided. Just like if it was a pattern…
It’s important to note that pretty much ALL the information exists ALREADY (in the CLM InfoCenter, the Jazz.net/DevWorks articles and wikis, etc.). The kind of gap this blog post aims at filling is a landing page providing a useful answer to the pattern described above. It shall present key information for both:
with the following characteristics:
- Content shall indifferently cover release versions: CLM 2012, CLM 2011.
- Format may be not a (Mind)Map. As some users revealed to me they could be reluctant to this format. Not to change my mind on this… Just adopting people’s preferred communication channels. I’ve chosen a table format this time.
Let’s go for now…
1) List the Out-of-the-box reports
||[Wiki] OOTB Reports (also incl. BIRT/RRDG-based reports)
|Reports by domain
(*): see “Table 2” in the referenced page.
2) Author your own reports
||[Wiki] CLM Framework Manager Data Model Details
|Data warehouse metrics
| “How To”s
|[CLM 4.0 InfoCenter]
|[Jazz.net forum / Article]
|Dozens of useful videos in “RRDI Playlist” by Rational User Education. Covers installation aspects, new features, introductions, building reports, etc.
What if some complementary information is required ?
- For “hands-on”-oriented guidance, I’d advise to read and complete the Reporting Workshop.
- For a selection of key resources on a broader scope (e.g. reporting for CLM in general including document generation (RRDG, RPE), installation procedures, troubleshooting tips, etc.), have a read at this blog post (and MindMap) “Get things clear about the CLM 2012 reporting capabilities” (note: it’s updated on a regularly basis – last update as for today: May 1st, 2013).
Last updated: July 18th, 2013 (added links to Jazz.net “in progress” InfoCenter)