Re: [EXTERNAL] Re: Automatic Variable Insertion

2023-04-18 Thread Tom Harper
Why not use ASASYMBF? https://www.ibm.com/docs/en/zos/2.2.0?topic=hsp-asasymbm-asasymbf-substitute-text-symbols Shared via the Google app Sent from my iPhone Sent from my iPhone > On Apr 18, 2023, at 4:02 PM, Swarbrick, Frank > <12f6dfd67d6a-dmarc-requ...@listserv.uga.edu> wrote: > > H

Re: [EXTERNAL] Re: Automatic Variable Insertion

2023-04-18 Thread Swarbrick, Frank
Here's a simple call to printf from LE-enabled assembler. ceedsa , ceecaa , prntit ceeentry main=YES call PRINTF,(fmtstr,3) ceeterm ppa ceeppa , fmtstr dcc'Test %d!',x'0' end prntit Output is: Test 3! -Original Message- From: I

Re: Automatic Variable Insertion

2023-04-18 Thread Paul Gilmartin
On 4/18/23 12:59:43, Charles Mills wrote: Correction: the form named sprintf(). Darned spell check. May I recommend "snprintf()" instead, for integrity reasons? -- gil

Re: Automatic Variable Insertion

2023-04-18 Thread Charles Mills
Correction: the form named sprintf(). Darned spell check. Charles -Original Message- From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On Behalf Of Charles Mills Sent: Tuesday, April 18, 2023 11:59 AM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Automatic

Re: Automatic Variable Insertion

2023-04-18 Thread Charles Mills
I know I have seen an example somewhere of calling printf() from assembler. Printf() does not really do a WTO, but the form of it named sprint() returns a string that you could WTO. The printf() family is super powerful -- more than you could hope to achieve in a reasonable amount of macro codi

Re: Automatic Variable Insertion

2023-04-18 Thread Gary Weinhold
We resolved this by creating using the TEXT= option with a register which allowed us to use a single WTO MF=L and a single WTO MF=E for all WTOs. The messages themselves are generated by a macro which has a LITERAL type (to generate the constants), a DSECT form (to name where the variables are

Re: Automatic Variable Insertion

2023-04-18 Thread Swarbrick, Frank
I'm actually working with LE messages right now. Not CEEMSG specifically, but a combination of: 1) Custom LE conditions and messages 2) CEECMI to add an "insert" to a message represented by a condition token 3) CEEMGET to retrieve the formatted message from a condition token Best place to start

Re: Automatic Variable Insertion

2023-04-18 Thread Peter Relson
I suggest, by the way, that you use the TEXT keyword of WTO. It can make things much more flexible for you, since the message line is then not part of the WTO expansion, rather just the address of it. Peter Relson z/OS Core Technology Design

Re: Automatic Variable Insertion

2023-04-18 Thread Farley, Peter
Requiring the entire TSO environment to use its message processing subroutine seems like overkill to me if the program that needs the variable message processing is not already using a TSO environment. I wonder if LE's CEEMSG can substitute fields in a message? I haven't investigated that serv

SV: Automatic Variable Insertion

2023-04-18 Thread Willy Jensen
STRING64 doc carries this warning: it will produce assembly errors in the following situations: a. STRING is used in more than one CSECT in the same assembly An alternative, which does not have this restriction, is found as the STRMAKE

Re: Automatic Variable Insertion

2023-04-18 Thread Breton Imhauser
Hey Paul! It may be a bit of a concept change from what you are asking, but have you looked at Gilbert Saint-Flour's "STRING" macro on the CBT? Quite useful for what you are looking at doing. Thanks! Breton Imhauser Senior Solution Delivery Architect | MF Implementations o: 501.585.4066 e: breto

Re: Automatic Variable Insertion

2023-04-18 Thread Seymour J Metz
Have you considerd using TSO service routinesm e.g., IKJEFF02? See From: IBM Mainframe Assembler List on behalf of esst...@juno.com Sent: Monday, Apr