| View previous topic :: View next topic |
| Author |
Message |
misi01
Advanced
Joined: 02 Dec 2002
Posts: 629
Topics: 176
Location: Stockholm, Sweden
|
 Posted: Thu Sep 29, 2022 2:40 am Post subject: ISPF panel messages |
 |
|
I've had this problem (theoretically) before, but it was never an issue until now.
Here is the doc from the IBM manual
| Quote: |
msgid
Required. Each message is referred to by a message identifier (ID). A message ID can be four to eight characters long. It is defined as follows:
Prefix: one to five alphabetic characters (A-Z, #, $, or @)
Number: three numeric characters (0-9)
Suffix (optional): one alphabetic character.
If the prefix is five characters long, the suffix must be omitted so that the total length does not exceed eight characters. Use the message ID suffix if more than 10 messages are to be included in one member.
|
What I'm having problem with is the prefix concept. If the prefix can be 1-5 characters, how does ISPF "know" how many characters are in the prefix?
I'm assuming that it's based on the actual ispmlib member name. So for example, if I want to issue a message SQL001, then ISPF looks for a PDS member allocated to ispmlib called SQL00, and in that member for a msgid called SQL001.
Here's my first problem. How does ISPF "decide" that the prefix is SQL00 and not SQL (after all, the prefix is 1-5 characters).
Here's an example of what I think should work based on the doc above.
Member is ispmlib is MSSQL. This contains a line
| Quote: |
MSSQL001 'Not valid yet' .TYPE=WARNING
'Not valid until you''ve selected a SQL system'
|
(prefix of 5 characters, followed by 3 numeric characters).
But when I try to use the message, I get the following error message
| Quote: |
Message MSSQL001
MSSQL001 message not found in 'ISPMLIB' library.
Current dialog statement:
DISPLAY PANEL(MSGESQL) MSG(MSSQL001) cursor(SYST)
|
Could someone please explain how it's supposed to work, and specifically what the messages should look like if "Use the message ID suffix if more than 10 messages are to be included in one member." (which is my situation here)
_________________
Michael |
|
| Back to top |
|
 |
kolusu
Site Admin
Joined: 26 Nov 2002
Posts: 12377
Topics: 75
Location: San Jose
|
|
| Back to top |
|
|
misi01
Advanced
Joined: 02 Dec 2002
Posts: 629
Topics: 176
Location: Stockholm, Sweden
|
| Posted: Fri Sep 30, 2022 4:55 am Post subject: |
|
|
Thank you, but you'll see that the first quote I included is actually from that page.
The example they include is
| Quote: |
ISPX001 'short message text'
|
Am I to take that as meaning that ISPX is the prefix, and 001 is the number.
Does the ISPMLIB librray member have to have som name that "ties" in with the ISPX prefix?
That automatically (?) leads me to think/believe that I can define a message in the same file as
| Quote: |
ISPX010 'Message number 10'
|
(or in my example, SQL001 works fine, SQL010 fails).
I tried changing the ispmlib member to SQL (rather than SQL00) and issuing message SQL001 but that now failed.
I tried changing the ISPMLIB member to SQLMS and the first message was called SQLMS001 which I tried to issue. That failed as well.
Basically, I think I'm asking ... if I want more than 9 messages in the individual message file, how should I define the ispmlib member, and what should message number 1 and number 10 look like in the file.
_________________
Michael |
|
| Back to top |
|
|
kolusu
Site Admin
Joined: 26 Nov 2002
Posts: 12377
Topics: 75
Location: San Jose
|
| Posted: Fri Sep 30, 2022 10:14 am Post subject: |
|
|
misi01,
ISPMLIB members are determined by truncating the number to 2 digits.
If message is ABC123A then ISPMLIB member is ABC12
Similarly ABCDE456 would be ABCDE45
SQL000 and SQL001 would both be truncated to SQL00.
So have a different numbering sequence and you should be able to display the messages.
_________________
Kolusu
www.linkedin.com/in/kolusu |
|
| Back to top |
|
|
misi01
Advanced
Joined: 02 Dec 2002
Posts: 629
Topics: 176
Location: Stockholm, Sweden
|
| Posted: Mon Oct 03, 2022 9:49 am Post subject: |
|
|
Okay - for anyone else having the same problem, this gave me the expected results. In ISPMLIB I had created a member called SQL00.
This contained the following (relevant) entries (relevant inasmuch as it was the concept of going beyond 9 messages that was causing me grief)
| Quote: |
SQL001 'Not valid yet' .TYPE=WARNING
'Not valid until you''ve selected a SQL system'
SQL001A 'Message number 10' .TYPE=WARNING
'Select one of the options from the SQL option''s action bar'
|
After that, I could set MSG(msgnum) on the display panel to either 'SQL001' or 'SQL001A' and get the message shown in the ISPMLIB entry.
Thank you for the help.
_________________
Michael |
|
| Back to top |
|
|
|
|
|
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
