OK, so, given the example in the LE Programming Guide:
:facid.XMP
:msgno.10
:msgsubid.0001
:msgname.EXMPLMSG
:msgclass.I
:msg.This is an example of an insert,
:tab.+1
:ins 1.a simple insert
:msg., within a message.
:xpl.This is a simple example of how to put an insert into a message.
:presp.No programmer response required.
:sysact.No system action is taken.
Does the data for the last three keywords appear anywhere other than here? I
guess I assumed that CEEBLDTX would, somewhere, create a separate "message
SCRIPT file" that would include these. Is MVS/QuickRef able to use the above
to create a lookup for our own messages?
Anyway, other than that I've got this working. Seems like it could be pretty
useful. Anyone else use "LE messages"; what do you (in general) use them for?
I've looked at them on and off for about ten years but never got around to
experimenting with them until now.
Thanks,
Frank
--
Frank Swarbrick
Applications Architect - Mainframe Applications Development
FirstBank Data Corporation - Lakewood, CO USA
P: 303-235-1403
>>>On 12/2/2010 at 12:03 PM, in message
<a6b9336cdb62bb46b9f8708e686a7ea005d5e05...@nrhmms8p02.uicnrh.dom>, "McKown,
John" <john.mck...@healthmarkets.com> wrote:
> Oh. Yes. They are the same thing. "The names were changed to protect the
> innocent."
>
> John McKown
>
> Systems Engineer IV
>
> IT
>
>
>
> Administrative Services Group
>
>
>
> HealthMarkets(r)
>
>
>
> 9151 Boulevard 26 * N. Richland Hills * TX 76010
>
> (817) 255-3225 phone *
>
> john.mck...@healthmarkets.com * www.HealthMarkets.com
>
>
>
> Confidentiality Notice: This e-mail message may contain confidential or
> proprietary information. If you are not the intended recipient, please
> contact the sender by reply e-mail and destroy all copies of the original
> message. HealthMarkets(r) is the brand name for products underwritten and
> issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake
> Life Insurance Company(r), Mid-West National Life Insurance Company of
> TennesseeSM and The MEGA Life and Health Insurance Company.SM
>
>
>
>> -----Original Message-----
>> From: IBM Mainframe Discussion List
>> [mailto:ibm-m...@bama.ua.edu] On Behalf Of Frank Swarbrick
>> Sent: Thursday, December 02, 2010 12:57 PM
>> To: IBM-MAIN@bama.ua.edu
>> Subject: Re: LE "message script file"
>>
>> Err...yes... That tells me how to create a message source
>> file, which I
>> have done. I am interested in the "message SCRIPT file", as in:
>>
>> ":xpl. This tag is optional. The :xpl. tag indicates text used to
>> explain the condition.
>> It is not printed as part of the message, but is included if the
>> message
>> SCRIPT file is formatted and printed."
>>
>> Are the SCRIPT file and the source file the same thing, just
>> confusingly with two different names?
>>
>> Frank
>> --
>>
>> Frank Swarbrick
>> Applications Architect - Mainframe Applications Development
>> FirstBank Data Corporation - Lakewood, CO USA
>> P: 303-235-1403
>>
>>
>> On 12/2/2010 at 11:15 AM, in message
>> <32535885.1291313715063.javamail.r...@elwamui-rubis.atl.sa.ear
>> thlink.net>,
>> Lizette Koehler <stars...@mindspring.com> wrote:
>> > Have you checked out this manual?
>> >
>> > Creating a Message Source File
>> >
>> > z/OS V1R9.0 Language Environment Programming Guide
>> > SA22-7561-08
>> >
>> > The message source file contains the message text and information
>> associated
>> > with each message. Standard tags and format are used for
>> message text
>> and
>> > different types of message information. The tags and format of the
>> message
>> > source files are used by the CEEBLDTX utility to transform
>> the source
>> file
>> > into a loadable TEXT file.
>> >
>> > Under TSO/E, if you specify a partially qualified name, TSO/E adds
>> the
>> > current prefix (usually userid) as the leftmost qualifier
>> and TEXT as
>> the
>> > rightmost qualifier. The message source file should have a fixed
>> record
>> > format with a record length of 80.
>> >
>> > When creating a message file, make sure your sequential numbering
>> attribute
>> > is turned off in the editor so that trailing sequence
>> numbers are not
>>
>> > generated. Trailing blanks in columns 1-72 are ignored. At least
>> one message
>> > data set (TSO/E) is required for each national language version of
>> your
>> > messages.
>> >
>> > All tags used to create the source file begin with a colon(:),
>> followed by a
>> > keyword and a period(.). All tags must begin in column 1, except
>> where noted.
>> > Comments in the message source file must begin with a
>> period asterisk
>> (.*) in
>> > the leftmost position of the input line.
>> >
>> > Figure 108 shows an example of a message source file with a facility
>> ID of
>> > XMP.
>> >
>> >
>> >
>> > Lizette
>> >
>> >
>> > -----Original Message-----
>> >>From: Frank Swarbrick <frank.swarbr...@efirstbank.com>
>> >>Sent: Dec 2, 2010 12:51 PM
>> >>To: IBM-MAIN@bama.ua.edu
>> >>Subject: LE "message script file"
>> >>
>> >>Section "Creating a Message Source File" of the LE Programming Guide
>> has
>> > references to a "message SCRIPT file", but I cannot find any more
>> details on
>> > this file. Anyone have any pointers to further documentation?
>> >>
>> >>Thanks,
>> >>Frank
>> >>
>> >>
>> >>
>> >>--
>> >>
>> >>Frank Swarbrick
>> >>Applications Architect - Mainframe Applications Development
>> >>FirstBank Data Corporation - Lakewood, CO USA
>> >>P: 303-235-1403
>> >>
>> >>
>> >
>> >
>> ----------------------------------------------------------------------
>> > For IBM-MAIN subscribe / signoff / archive access instructions,
>> > send email to lists...@bama.ua.edu with the message: GET IBM-MAIN
>> INFO
>> > Search the archives at http://bama.ua.edu/archives/ibm-main.html
>>
>> >>>
>>
>> The information contained in this electronic communication and any
>> document attached hereto or transmitted herewith is confidential and
>> intended for the exclusive use of the individual or entity
>> named above.
>> If the reader of this message is not the intended recipient or the
>> employee or agent responsible for delivering it to the intended
>> recipient, you are hereby notified that any examination, use,
>> dissemination, distribution or copying of this communication
>> or any part
>> thereof is strictly prohibited. If you have received this
>> communication
>> in error, please immediately notify the sender by reply e-mail and
>> destroy this communication. Thank you.
>>
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
>> Search the archives at http://bama.ua.edu/archives/ibm-main.html
>>
>>
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
> Search the archives at http://bama.ua.edu/archives/ibm-main.html
>>>
The information contained in this electronic communication and any document
attached hereto or transmitted herewith is confidential and intended for the
exclusive use of the individual or entity named above. If the reader of this
message is not the intended recipient or the employee or agent responsible for
delivering it to the intended recipient, you are hereby notified that any
examination, use, dissemination, distribution or copying of this communication
or any part thereof is strictly prohibited. If you have received this
communication in error, please immediately notify the sender by reply e-mail
and destroy this communication. Thank you.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
