Re: Ray Mullins on Assembler demand.

2023-09-05 Thread M. Ray Mullins (Ray)
That’s the name in SAMPLIB, interestingly. The source is IEEACTRT, but it’s 
used to create IEFACTRT. Maybe it was written by console staff decades ago? 

Sent from my iPhone

> On Sep 5, 2023, at 11:08, David Spiegel 
> <0468385049d1-dmarc-requ...@listserv.ua.edu> wrote:
> 
> Hi Ray,
> You said: "... SAMPLIB(IEEACTRT) ..."
> Don't you mean SAMPLIB(SMFEXITS) //IEFACTRT?
> (IEEx is Console-related; IEFx is SMF-related)
> 
> Regards,
> David
> 
>> On 2023-09-05 13:23, M. Ray Mullins wrote:
>> There's a bit of context that is lost here. I purposely said "invisible 
>> hand", playing on the imagery. But just because that's what the owner of the 
>> "invisible hand" wants doesn't necessarily mean that's happening.
>> 
>> Metal C in a JES2 environment is extremely difficult to implement, which is 
>> why you're now seeing the JES2 policy direction. IMHO if IBM had provided 
>> Metal C PROLOG/EPILOG for JES2 and z/OS exits, as well as APIs covering the 
>> common macros*, I think would have seen more Metal C take-up. I presented a 
>> few times at SHARE about converting SAMPLIB(IEEACTRT) to Metal C. I 
>> originally envisioned it as a "how-to", but it became instead a user 
>> experience, as my experience was mixed.
>> 
>>> On 2023-09-05 09:39, Bill Johnson wrote:
>>> Metal C, exactly what Mullins said is replacing assembler. In the end, my 
>>> contention in the beginning is proving truer by the day. And you’re right, 
>>> assembler isn’t that hard to learn and not hard to replace,
>>> 
>>> 
>>> Sent from Yahoo Mail for iPhone
>>> 
>>> 
 On Tuesday, September 5, 2023, 12:36 PM, Matt Hogstrom  
 wrote:
>>> 
>>> My take is that Assembler is just a language and honestly I don’t think its
>>> all that hard to learn.  What it does require is more understanding of the
>>> OS and the ability to setup for calls to other services.
>>> 
>>> The higher languages simply obscure, or encapsulate, those low level
>>> services.
>>> 
>>> I use Metal C for new code as it is more easily understood by developers.
>>> That said, there are times for pure assembler code and I enjoy it.  I
>>> started out as a batch assembler programmer but I was drawn to understand
>>> the OS and its structure.  Assembler was the way to interface and now there
>>> are other options.
>>> 
>>> As an ISV we want Assembler programmers.  In a business, I’d focus on the
>>> languages that the market understands.  The important thing is to not be
>>> religious about a language.  Its just a tool.
>>> 
 On Tue, Sep 5, 2023 at 08:22 David Elliot  wrote:
>>> 
 Very little from what I see. What little
there is is stupid stuff like reverse engineering code so that the 
 client
 can rewrite it in JAVA or whatever the language of the day is.
 
>>> 
>> 
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: "National" characters

2023-07-11 Thread M. Ray Mullins (Ray)
I think the term “national characters” has its origins in the COBOL standard. 

The “special” characters can produce some interesting output. I once had to 
deal with a Turkish customer who used Top Secret. User resources classes should 
begin with X’5B’, which in CP 1026 (Latin-5/Turkish) is İ. We would get screen 
shots and printouts that caused us to double take until we got used to it. 

Sent from my iPhone

> On Jul 11, 2023, at 06:00, Bob Bridges  wrote:
> 
> It was never clear to me why the term "national" was picked in the first
> place.  Although I worked for Volvo 14 years (jag Verkade på Volvo
> Lastvagnar fyrtio år) and on the Swedish side those keys produced characters
> in the Swedish alphabet - I don't remember which ones exactly, but probably
> something like Ä, Å and Ö.
> 
> ---
> Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313
> 
> /* Vegetables aren't food.  Vegetables are what food eats.  -from Shoe,
> 1999-10-08 */
> 
> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf Of
> Peter Relson
> Sent: Tuesday, July 11, 2023 08:05
> 
> The ID (now CDD) folks had years ago made us refer to @,$,# as "special
> characters" rather than as "national characters".
> 
> It is disappointing that they did not change the publications to be
> consistent with that directive. By all means point out the discrepancies
> that you spot.
> 
> I'll bet that any change would be from "national" to "special" (not the
> other way around).  I have no idea what term they will decide to use for the
> JCL characters that they currently call special.
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: Call by value, final

2023-04-08 Thread M. Ray Mullins (Ray)
PDSEs allow mixed case alias names up to 1023 bytes long. They can only be seen 
through DESERV, so a utility not named ISPF can look at them (I think PDS 8.6 
supports them). 

If you look at some of the CICS PDSE program object libraries, you can see them 
in the member list (again, not under ISPF, sounds like a good IBM Idea™). 

Cheers,
Ray

Sent from my iPhone

> On Apr 8, 2023, at 09:03, Jeremy Nicoll  wrote:
> 
> On Sat, 8 Apr 2023, at 15:54, Paul Gilmartin wrote:
>>> On Sat, 8 Apr 2023 04:27:04 +, Frank Swarbrick wrote:
>>> 
>>>   ...  The assembler seems OK with it, but the linker is converted to upper 
>>> case, even though I've specified CASE(MIXED).  
>>> 
>> I'm surprised.  In an experiment long ago I was able to create a member
>> in an (old-fashioned) PDS simply with CASE(MIXED); NAME lower.
> 
> I'm sure I recall that some of the SMP/E work PDSes had member names that
> not only were mixed case but also included characters that you'd not see in
> PDSs processed via standard ispf utilities.  I can't quite remember if they 
> used
> every single byte value in each of the 8 character positions, but I think 
> they 
> might have done, thus allowing 256 ** 8 different member names.
> 
> -- 
> Jeremy Nicoll - my opinions are my own.
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN