Date/Time? Timezone? Offset from GMT? I don't know. Sys CCSID?

Ringer

Well, we've got roughly 76 characters to fill up.

The IBM stock price? Ha.

Total and available storage?

I have a command that shows the last IPL date and time.  Not sure if that would be useful for this command or not.

Cumulative PTF level?

I thought about the storage and the PTF level installed. The last IPL date/time might be useful to know, but is it really? Perhaps a configuration tool that lets people specify what they want to see on the DSPSYS command would be beneficial; that way we could "just add it to the list" and you see what you want to see. For me its always the system and release level since I'm hoping from one system to another. But also the critical storage conditions are often an issue for me on various systems.

Is it possible to use a msg subfile? Then you could use more than 76 characters.

Isn't that a message subfile anyway (it's for system messages normally and you can get more than one in some circumstances).  And I suppose you could put the important stuff on line one and other information on successive lines, where you don't need to roll unless you want to see that information.

Neil, are you suggesting that I send multiple message lines? If so, then you'd have to do F10 on Command Entry to see it (or look in the joblog). Just the final one would be visible naturally.

Well Ringer suggested it.  If you were to send multiple messages I'd be inclined to go with the System Name/OS Version message last.  And make the other requests preceed them.

A one row message subfile, where if you see the + sign, you move your cursor to the row and hit page down to see the other messages. Like we see for submitted compiles. But not sure that's possible for *STATUS message and so forth from just any command line.

Chris, I don't think you're getting it. These are only completion messages being sent. There is no interactive program that is launched with a DDS-based green screen. I retrieve the info, and do a SNDPGMMSG *INFO and it shows up on the bottom of your screen. As in my example in the original post.

So if I send multiple messages with lots of data, the would be info, info, info, comp, with the comp message being sent last with the base info (as Neil suggested).

I've updated the DSPSYS command but I'm a bit concerned about the number of CPU entries. here's what it looks like today:

COZ720 V7R1M0 DskUse:34.9870%  CPU(1/3/4) RAM(7616) lparName: 06-xxxxx

This includes:

• System Name
• IBM i release level
• Active CPUs
• Maximum CPUs
• Partition CPUs
• RAM in MB
• Partition Name

Wondering if CPU counts are all that important?

FYI, my buddy, Bruce Hoffman just told me about this API or "tool" as IBM calls it:

QLZARCAPI - Display Partition Information

Its a bit verbose with its labels but gives the same information as the DSPSYS command in COZTOOLS, except COZTOOLS includes Fish's request for current disk usage %

So I'm going to loo for other information to include in DSPSYS.

What about using the http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/apis/quilngtx.htm 

Api?  For the display?

If you're not using LPAR - primary only, I guess - does it still look OK?

And a thought - if you're short by a couple characters, you could round DskUse to .01 or even .1 precision.

Say - is this a message from a message file? You could put all the stuff that doesn't fit into the 2nd level message text.

No. I'm not interested in duplicating the capabilities of the QLZARCAPI API.

If you do a CALL QLZARCAPI on Command Entry you get your Partition information in verbose format, so there's not much need for me to duplicate that capability.

I am working on adding the PTF Level to DSPSYS, however. Sadly there's no direct "give me the current PTF info" you've got to dump it all to a user space and filter through the list looking for what you want.