Re: Macro compound symbols

You didn't set or define variable P1. Message ASMA300E tells you that variable P1 is not set (notice the TESTM/P1) Regards, Jon. From: Hardee, Chuck chuck.har...@thermofisher.com To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Sent: Sun, April 1, 2012 10:07:23 AM Subject:

Re: curiosity: In AR mode, why doesn't BALR/BASR/BRAS/BRASL set the value of the corresponding AR register ?

(e.g. LA is used alot so adding AR copy adds to it's time). Regards, Jon Perryman. From: John McKown joa...@swbell.net To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Sent: Wed, April 11, 2012 2:32:59 AM Subject: Re: curiosity: In AR mode, why doesn't BALR/BASR

Re: A Curiosity Question

your question. Regards, Jon Perryman. From: esst...@juno.com esst...@juno.com To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Sent: Sat, May 19, 2012 7:53:26 AM Subject: A Curiosity Question I have a PARMLIB Memebr set up as SUBSYS SUBNAME(MYSS) INITRTN(INITRTN1) Now

Re: MVC with 2nd operand length

. If IBM were to implement an MVC:2, then you would never have receiver too short because it should check the length. I personally don't need this instruction because I have a single program that builds messages and formats lines but I can see how others might want it. Regards, Jon Perryman

Re: MVC with 2nd operand length

MVCL is an instruction begging for a macro. Besides loading registers and destroying the contents of 4 registers upon completion, it is also interruptible so you have to ensure the move is complete. From: Tony Harminc t...@harminc.com You know, for the vast

Re: MVC with 2nd operand length

: Re: MVC with 2nd operand length On May 23, 2012, at 22:27, Jon Perryman wrote: MVCL is an instruction begging for a macro. Besides loading registers and destroying the contents of 4 registers upon completion, it is also interruptible so you have to ensure the move is complete. Ensuring the move

Re: MVC with 2nd operand length

A literal in the literal pool should never be modified and the assembler is enforcing that rule where possible. The problem is that multiple =C'WOMBAT' in your program would only generate a single entry in the literal pool. Can each occurrence handle this modification of the value? The assembler

Re: MVC with 2nd operand length

I think that John is asking for an example where the existing BIF's do not satisfy your situation and what length would expect it to return. Regards, Jon. From: Paul Gilmartin paulgboul...@aim.com On May 26, 2012, at 18:28, John Ehrman wrote: Now, I'm truly

Re: MVC with 2nd operand length

There is hidden functionality in this macro. 1. I believe that john said that LA will resolve a label reference in the assembler. I'm not sure of the situations it fixes. 2. Coding the (0) on the LA causes an error message when the destination is a literal or has a length specified. This

Re: MIPS calculation for a particular Job

'SYS1.SAMPLIB(IEEACTRT)' contains a sample IEFACTRT exit that displays some step/job termination messages which should give you some numbers to do a comparison. Hope it still works. I haven't seen it run in years. Technically it's not mips but it's clear jake meant cpu time. Regards, Jon.

Re: Base registers

. .** .* Desc: Execute instruction .* .* Copyright: 2010-2012 Jon Perryman .* .* Function: .* Makes the length relative to 0 and executes the .* specified instruction using the specified length. .* The register is restored back to a length relative

Re: ** ASMA030E Invalid literal usage - =CL8'MARTINWH'

I don't see LPP in the POP manual. Is it an instruction or a macro? If it's a macro, then maybe there is an option to get around this error message. Jon Perryman. From: Martin Truebner mar...@pi-sysprog.de When I compile this LPP =CL8'MARTINWH

Re: ASM tag problem

table is searched instead of looking in the maclib for the definition. You should open an ETR to see if this is a bug or if it works as designed. Regards, Jon Perryman. From: Robert Ngan rn...@csc.com To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Sent: Wed, September 12, 2012

Re: Immediate value range on [arithmetic] COMPARE and JUMP

and allowing 3 operands. . Regards, Jon Perryman. From: Robert Ngan rn...@csc.com To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Sent: Tue, September 25, 2012 5:38:02 PM Subject: Immediate value range on [arithmetic] COMPARE and JUMP I am playing with the COMPARE AND JUMP

Re: IHAXMD IHAIETB

would have use the LTE's (for global too) to find each PC entry. It's easier to use a dump to find the PC numbers.. Regards, Jon Perryman. From: esst...@juno.com esst...@juno.com Im trying to re-create a program I wrote 20 years ago. It displayed all the Program

Re: IEANTCR

the value. Each address space will have it's own unique value for the same name. Regards, Jon Perryman. From: Scott Ford scott_j_f...@yahoo.com I have seen several discussions in my 'google' searches on IEANTCR. I need clarification. We have a program that issues

Re: Weird Metal C problem

--+--+--)- '-:--++--+---+-' '-output-' '-:--+---+--+-+-' '-input-' '-:--+--+-' '-clobbers-' Regards, Jon Perryman. From: Johnny Luo johnny.xingkui@gmail.com To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Sent: Sat, October 27, 2012

Re: Weird Metal C problem

Good point. Other C compilers accept a single underscore, so I assumed IBM C did too. If it doesn't, then Johnny will need to look for a function or macro that is coded for the _ASM(). Regards, Jon Perryman. From: Edward Jaffe edja...@phoenixsoftware.com On 10

Re: Curosity Question

see the clustering at http://www.ask.com/wiki/Letter_frequency if you scroll down to the graphs. Clustering changes depending upon the situation. E.g. how often a letter occurs in words which is another graph on that web page which you can compare. MVS messages cluster even more. Regards, Jon

Re: Impossible - generic macro prototype

)-EQ) 5. AREAD could be used to read statements following the macro. This could be helpful in some situations. Regards, Jon Perryman From: McKown, John john.mck...@healthmarkets.com I would like to write a macro which does not specify any parameters, but can

Re: Impossible - generic macro prototype

IBM's workaround for not having a macro functions is to declare a global variable and set it. The classic example is IBM's SYSSTATE macro. While this is not the best solution, it does work and it's only an extra line..Maybe a third line if you want to save the value. Even though it's not a good

Re: Impossible - generic macro prototype

LOOP1 with PARMS SETC 'SYSLIST(1)'(2,K'SYSLIST(1)-2) Regards, Jon Perryman. From: Jon Perryman jperr...@pacbell.net 3. Keyword parms not defined in the macro prototype get error message ASMA017W which can be suppressed by *PROCESS SUPRWARN(17). I'm not a fan

Re: STORAGE OBTAIN with ALET

your code will be thankful. Thanks, Jon Perryman. From: Chris Craddock crash...@hotmail.com a cross memory server address space, there are circumstances where that program might want to obtain storage in another address space - typically that would be in your

Re: macro coding question

, Regards, Jon Perryman. From: paul schuster pgs4ibmm...@pacbell.net How can I enforce the requirement that the AREA=parameter is coded the same in both invocations of the macro?

Re: OPSYN self execution

. Regards, Jon Perryman. From: Bodoh John Robert [Contractor] john.robert.bo...@irs.gov To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Sent: Thu, February 7, 2013 2:46:23 PM Subject: Re: OPSYN self execution Sorry it has taken so long to get back to this but I haven't had

Re: ESTAI IKJEfT1B 04C

processor) and your program would strip it's program name from the command and call IKJEFTSR to issue the original command. As I said before, it won't capture every abend but it will allow the MVS return code to be set where as IKJEFT01 won't give you the return code. Regards, Jon Perryman

Re: ESTAI IKJEfT1B 04C

by PARMLIB(IKJTSOxx). Jon Perryman. - Original Message From: Walt Farrell walt.farr...@gmail.com On Sun, 7 Apr 2013 15:58:35 -0400, Phil phil_sid...@hotmail.com wrote: Clearly this is another case of RTFM. I missed JSTCB=YES on my ATTACH. The manual does say 'one and only' jobstep task

Re: ESTAI IKJEfT1B 04C

and commands continued to run. As for authorized commands and the parallel TMP, I've never specifically looked at how it works or what get's delayed. Where can I find information about this? Jon Perryman - Original Message From: Binyamin Dissen bdis...@dissensoftware.com TSO also changes

Re: Baseless problem

database? 3. How are IPCS diagnostic exec's affected? 4. Diagnostic documentation, FAQ's, problem database and other online material might have something that is affected. Are there any drawbacks to placing data first in a module? I only see possible drawbacks when it is not first. Regards, Jon

Re: Length question

ORG , You'll need to create a #TRT macro to allow TRT with a larger size than 256 bytes. #EX is a macro that adjusts the length relative to 0 and issues the EX instruction against the instruction passed in SYSLIST(2). Jon Perryman - Original Message From: Scott Ford

Happy Gilmore (was Length question)

either know the situation or are not interested. I say we let him get his final word in and just let it go at that. Send us your last response and make yourself Happy Gilmore. This Email contains shampoo because regular poo would not do. Thanks, Jon Perryman.

Re: Happy Gilmore (was Length question)

use? Why wouldn't he simply say the TRTE instruction should have been used. He always chooses his wording carefully and hides the malice. Everyone interpreted my Email as a personal attack but did it actually contain anything more direct than in his response? Thanks Jon Perryman. From: John

Re: Happy Gilmore (was Length question)

with an intent to antagonize or with malice. Jon Perryman. - Original Message From: DASDBILL2 dasdbi...@comcast.net To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Sent: Mon, April 15, 2013 9:59:40 AM Subject: Re: Happy Gilmore (was Length question) We should not necessarily associate malice

Re: Translate Table

Assembler codeset translation calls are documented in Unicode Services. Since Scott has mentioned his product is calling assembler routines from an LE environment, I'm guessing it's written in C. If that is the case, ICONV will do the conversions. Jon Perryman. - Original Message

Re: Calling SUPERC from an assembler program

Batch calls need 2 byte length followed by parm. LA R1,=A(PARM) LINK EP=ISRSUPC PARM DC AL2(L'PARMDATA) PARMDATA DC C'DELTAL,LINECMP,UPDSEQ0' Jon Perryman. - Original Message From: Paul Gilmartin paulgboul...@aim.com On 2013-04-23, at 16:02, David Eisenberg wrote

Re: Concatanate Bits Instruction?

to R14 after the move to point to the next field and forget about the SR. Jon Perryman From: Robert A. Rosenberg a...@rarpsl.com At 21:46 -0700 on 08/03/2013, Duffy Nightingale wrote about Concatanate Bits Instruction?: Hi All, Working on a project that requires

Re: Concatanate Bits Instruction?

field) XC1(3,R4),1(R4) Clear unwanted bits (could overlay next field) J NEXTMove next bit string Jon Perryman - Original Message - From: robin robi...@dodo.com.au Seems unduly and unnecessarily complicated to me. I'm a believer in the KISS principle

Re: Making an old macro baseless

pool, you could put the data inline (use BRAL R2,0 followed by the DC for the data without the =). Jon Perryman. From: John P. Hrtmann jphartm...@gmail.com CMS Pipelines ships the macro #LAL. One would write: #LAL 2,'a message' This expands to a LA 2,=c

Re: Storage Area Name using CSECT

to fill it in. As for understanding the storage area and modules, you would need to understand the programs involved. Source code and assembly listings are usually needed for this. Jon Perryman. From: Jake anderson justmainfra...@gmail.com I was trying

Re: Storage Area Name using CSECT

. There is probably more that could be easily reviewed by sysprogs but it really depends upon the problem symptoms.. Jon Perryman. From: Jake anderson justmainfra...@gmail.com Apology for my ignorance. Does it apply same for analysing Z/OS Standalone Dump ?

Re: Why is division by zero permitted?

What arithmetic expression allows divide by 0? Jon Perryman. From: Paul Gilmartin paulgboul...@aim.com OK. Pure HLASM. I've long wondered why division by zero is permitted in arithmetic expressions when otherwise overflows (even in division) are reported

Re: Why is division by zero permitted?

Paul Gilmartin said HLASM (not S360). The standard divide instructions get S0C9 when dividing by 0. Is it floating point that allows divide by 0? Is it the macro assembler SETA that allows it? Jon Perryman. - Original Message - From: Rob van der Heij rvdh...@gmail.com Ask someone

Re: Some Help with Conditional Assembly

for a fullword definition. You could also use L'L to determine it has a length of 4 (in case someone coded (A or XL4). If the length is greater than 4095, then you can't use LA. You will need to use another instruction to load the length (e.g. LHI, LAY, L with =A()). Jon Perryman

Re: Some Help with Conditional Assembly

a load otherwise assume it's an LHI Jon Perryman. From: esst...@juno.com esst...@juno.com To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Sent: Saturday, November 2, 2013 12:11 PM Subject: Re: Some Help with Conditional Assembly I obviously did not explain this wellm despite

Re: Relative Branches / IBM macros

to ask yourself when we've gone to far in making it easy for newbies to easily shoot themselves in the foot. Jon Perryman. From: Bob Raicer r...@raicer.com Here is an example of what I was trying to describe: ABLE    CSECT ,         EXTRN IEFBR14

Re: Moves and others

) ORG TRT_TAB+C'A'We want to find an A DC C'A' ORG , Obviously this is not complete (you need to check lengths and various other things but it will get you started. Jon Perryman. From: Rich Long xmann...@yahoo.com Issue I

Re: ASSIST Assembler and HLASM

instructions even though it's MVS 3.8. Jon Perryman. From: Paul Gilmartin paulgboul...@aim.com To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Sent: Wednesday, November 20, 2013 8:03 PM Subject: Re: ASSIST Assembler and HLASM On 2013-11-20, at 15:41, 408-463-3543 T/543- ehr

Re: Moves and others

of the instruction?  Jon Perryman. From: pw...@mweb.co.za pw...@mweb.co.za Second, the sequence used will execute the TRT once for 1 byte, then repeat the TRT for 6 bytes. The target of an EX instruction must NOT be inline.

Re: Base-less programming

in the program so that you can identify where your program is not correctly using relative offsets. Jon Perryman.  From: John McKown john.archie.mck...@gmail.com Well, I don't _usually_ use the *+some value. I normally use a label with the SYSNDX symbol embedded

Re: Base-less programming

If you don't want the extra statement then add the label directly to the statement and use it's length. JE*+L'LA1 LA1 LA R1,1(R1) JE LA2+L'LA2 LA2 LA R1,1(R1) Jon Perryman - Original Message - From: Phil Smith III li...@akphs.com T ony Harminc wrote: I

Re: getting length of macro symbol

Your counter doesn't have to start at 0. Start it at 1 and you will always have 5 digits or more. Just drop the first digit. CNT SETA 1 DATA SETC 'CNT'(2,*)  Jon Perryman. From: Tony Thigpen t...@vse2pdf.com and I need all the labels to have

Re: getting length of macro symbol

the size.  PADDED  SETC   '000C'(K'C,4)      pad left to 4 characters PADDED  SETC   'C.000'(1,4)           pad right to 4 characters Jon Perryman. From: John Gilmore jwgli...@gmail.com I do not see much difference in performance between my substringing

Re: HLASM continuation...

statements require the variable be defined prior to the SETA statement. When used on an instruction, the variable can be anywhere in your in your code. Jon Perryman. From: John Gilmore jwgli...@gmail.com txt      setc    'QVSIMGLOGICALPARTITIONNAME' txtk

Re: Rexx substr not retiring string

You forgot the period in the stem name EXECIO * DISKW OUTDS (FINIS STEM OUTVAR. Alternatively, ISPF edit has a line command to shift data (e.g. ((2 on the first line and (( on the last line to shift). Jon Perryman. From: Micheal Butz michealb

Re: PTF level in SYSPRINT

as the levelset Do you know if they follow the same methodology as ASM? Your group is lucky because they can simply tell us to bring the product current because that's what will happen anyways. This isn't how most products create PTF's. Thanks, Jon Perryman. From

Re: ASMA038S

Removing the SSCM DSECT.will stop the error but the correct specifications for these macro's would be       IEFJSSOB (xx,xx,...),CONTIG=NO   Where xx would be the SS extensions you want. In your case, you only want CM. CONTIG=NO will insert DSECT's.  Jon Perryman    On Sunday, May 11

Re: Program Call Vs SVC

On Tuesday, May 20, 2014 6:25 AM, John Gilmore jwgli...@gmail.com wrote: Rob Scott's summary of the current situation would be hard to improve upon. There are situations in which it is appropriate to maintain and even perhaps extend existing SVC routines.  They will not disappear anytime

Re: Program Call Vs SVC

may easily have multiple PC's for running multiple version of your product. Jon Perryman On , Jon Perryman jperr...@pacbell.net wrote: On Tuesday, May 20, 2014 6:25 AM, John Gilmore jwgli...@gmail.com wrote: Rob Scott's summary of the current situation would be hard to improve upon

Re: 50 year old assembler code still running.

Actually the assembler doesn't care what value you use as long as you match the LA matches the USING statement. Even then, it won't complain. On Saturday, March 11, 2017 6:17 AM, David Cole wrote: USINGs with multiple registers assume an interval  distance of 4096 not

Re: Question about CPUs

I believe the only true atomic instructions are CS and CSD. PLO is considered atomic when using the same lock. Concurrency is only guaranteed with some sort of lock which is to expensive to implement for every instruction and for storage being referenced / modified. The odds of a single

Re: Macro processor

Sorry for taking  so long to respond. A little too busy. >John Ehrman  wrote: I agree that PL/I's macro preprocessor is indeed powerful; >but it and > all other macro facilities I know of lack a key feature of >HLASM's  > conditional assembly and macro facility:   John is being modest by hugely

Re: Macro processor

mbler programmer. In all my years, the C code I worked with would have been just as good as the C version because of macro's. If C were to add the HLASM macro features, then I would definitely jump ship from HLASM. Thanks, Jon. On Thursday, December 14, 2017 9:45 PM, Jon Perryman <jper

Re: Any real need for sequence numbers in 73-80 any more?

ISPF edit's compare command has existed for many years and uses SUPERC under the covers. Forget taking source off platform and give it a try. One of the options is number of lines for syncing. If there is a problem with syncing after changed lines, then look at the options. It worked great for

Re: Any real need for sequence numbers in 73-80 any more?

Sadly, the absolute source line numbers become ambiguous when you add / delete lines. In maintenance mode, this was usually not a problem. In dev mode, it was only occasionally annoying. I personally prefer this area contains the PTF number. When diagnosing problems, it allowed us to easily

Re: Address of a Literal

If by "C's less powerful macro language", you actually mean abysmal pre-processor language then I totally agree. C programmers will use motivated reasoning to convince you that C is still the language of choice. The problem is that C hasn't really grown as a language to help programmers (C

Re: Dynalloc (was Macro processor)

<edja...@phoenixsoftware.com> wrote: On 12/23/2017 8:18 AM, Jon Perryman wrote: > People are clever and will find ways to abuse things if they are motivated. > Dynalloc can easily be exploited. It's not exploited because no one has been > motivated to exploit it. Security ris

Re: Dynalloc (was Macro processor)

arr...@gmail.com> wrote: On Fri, 22 Dec 2017 21:26:07 +0000, Jon Perryman <jperr...@pacbell.net> wrote: >Charles broke the cardinal rule in security ( never say never ). Viruses rely >on dynalloc. This vulnerability was used against Target where they >were >recently fined $18 m

Re: Dynalloc (was Macro processor)

t use it and it's not publicized. Jon. On Saturday, December 23, 2017 9:41 AM, Jeremy Nicoll <jn.ls.mfrm...@letterboxes.org> wrote: On Sat, 23 Dec 2017, at 16:18, Jon Perryman wrote: > Most security breaches need multiple exploits on MVS. Often, eliminating > a single explo

Re: AW: Dynalloc (was Macro processor)

I'm not saying that it comes down to dynalloc. Security never comes down to a single exploitation. Think about alcatraz which despite all the extreme security measures still had an escape. I'm sayiing that dynalloc is not controlled by security admins and there are simple scenario's to exploit

Re: Dynalloc (was Macro processor)

fail to convince me of the existence of any actual vulnerabilities in z/OS itself.Keven On Sat, 23 Dec 2017, at 18:40, Jon Perryman wrote: > I only wanted to know why dynalloc is no longer considered an exposure.

Re: Dynalloc (was Macro processor)

ents fail to convince me of the existence of any actual vulnerabilities in z/OS itself.Keven On Sat, 23 Dec 2017, at 18:40, Jon Perryman wrote: > I only wanted to know why dynalloc is no longer considered an exposure.   This message and any attachments are intended only for the use

Re: Dynalloc (was Macro processor)

23 Dec 2017, at 19:42, Jon Perryman wrote: > Naming conventions only go so far in securing departmental data because > of exceptions. For instance, there is departmental overlap such as > payroll and general ledger. But if there's proper separation between production ids (which run t

Re: Dynalloc (was Macro processor)

Think like a security admin instead of programmer. You are right that dynalloc is not a problem but to a security admin, it is an exposure. Exposures combine to become a problem.  Here are some examples (UNRELATED to dynalloc) that may help to clarify. 1. Don't you have customers that refuse to

Re: Dynalloc (was Macro processor)

This started as me being surprised that Cobol and PL/I now support Dynalloc because of the security risks. I satisfied that it exists and for whatever reason, it is no longer considered a security exposure. My apologies for allowing this to drag into a discussion about security theory in this

Fair comparison C vs HLASM

I find it amazing how C programmers believe in the superiority despite overwhelming evidence to the contrary. Surprisingly, the psychological term for this is "motivated reasoning" and I never believed it until now. Below actually transpired yet they still believe that C is superior (even with

Re: Fair comparison C vs HLASM

I can't say for sure how much is written in PL/X but I suspect a good portion. But there is a substantial portion written in HLASM which would not be written in PL/X. Writing those in PL/X would have make MVS unmaintainalble. You are correct in the comparison with Metal C. Sorry if I came

Re: Fair comparison C vs HLASM

>> I wrote: Writing those in PL/X would have make MVS unmaintainable. > Peter Relson wrote: The second sentence is untrue, Peter, it would be interesting to see how PL/X has solved abstract coding techniques. I know DCB is not written in PL/X. Could you show us a short snippet of how you would

Re: Fair comparison C vs HLASM

>Paul Gilmartin wrote: Is "full functionality of DCB" useful > for any OS other than for z/OS? For z/OS, > allocate with BPXWDYN or JCL DD statement and open by fopen("//DDN:..." ). BPXWDYN is dynamic allocation and does not provide every feature in DCB. FOPEN allows some DCB parms to be

Re: Fair comparison C vs HLASM

> Dave Wade wrote: > https://www.theregister.co.uk/2018/01/23/serverless_exhilarating_terrifying_ridiculous_name/ > > shows the futility of this discussion. This is too funny. You may recognize "serverless" by it's common name "The Cloud". Read the wiki for "cloud computing" and you will

Re: Fair comparison C vs HLASM

On Friday, January 26, 2018 7:05 PM, Paul Gilmartin <0014e0e4a59b-dmarc-requ...@listserv.uga.edu> wrote: > Paul wrote: Does DCB provide functionality not available via DYNALLOC? DCB is all about the program. There are multiple access methods that can be used (e.g. bsam, qsam). Each may

Re: Fair comparison C vs HLASM

>> Jon Perryman wrote: >> For this topic, it doesn't matter whether it's C or Metal C. > Peter relson wrote: > Sure it does. Because Metal C gives you access to assembler and to the >IBM-provided assembler executable macros. And that is what is being talked >abou

Re: Fair comparison C vs HLASM

> Tom Marchant wrote: > I am not a fan of C, but I don't believe > that any of the shortcomings> of Unix are properly attributed to the C > language. I'm not opposed to C. It's just another language to me except it made computers accessible and promoted "free". I use several languages and

Re: Fair comparison C vs HLASM

On Tuesday, January 30, 2018 8:05 AM, Paul Gilmartin <0014e0e4a59b-dmarc-requ...@listserv.uga.edu> wrote: > Gil wrote: > Which of the two is to blame for null-terminated strings?  > > (Or was it BCPL?) Exactly my point. I suspect that the C group considered Null-terminated

Re: Fair comparison C vs HLASM

> Dave wrote > B used null terminated strings... Isn't this another language developed around RISC processors? Byte processing is the standard for that hardware. Regards, Jon.

Re: Fair comparison C vs HLASM

> Tom Marchant wrote: > Well, ok, null-terminated strings are a booby-trap > included in the C language. But it was poor programming that caused the > problems. I'm not sure how strings could be attributed to poor programming. Unix & C were designed and implemented around RISC processors.

Re: Fair comparison C vs HLASM - Thank you Kirk Wolf

> Dave Cole wrote: > Thank you Kirk for reposting by "The Pointlessness of handwriting > 'efficient' code" article! Sometimes I put these things out there and > am deafened by the silence. It's nice to know that someone is listening. Sorry about the silence but your posts are most definitely

Re: Fair comparison C vs HLASM

> Kirk wrote: > C has always had support for fixed length strings (aka char[]). Sorry if I was insulting. It was not intentional. I'm not sure how implied this wasn't possible. > Kirk wrote: > XLC/C++ compiler will inline MVC, MOVS, etc inplace of memcpy() and > strcpy(). And it knows how

Re: Fair comparison C vs HLASM

>> Jon wrote: >> I suspect that the C group considered >> Null-terminated strings cost exactly the same as fixed length fields. > Robin Vowels wrote > But if you just want the length, a fixed-length string wins. Length of a fixed length string is calculated by the compiler. I was specifically

Re: Fair comparison C vs HLASM

> Robin Vowels wrote: > And I understand that RISC processors came long after C. C was developed on a PDP-11. I believe that the PDP-11 was a RISC machine. Even so, I think it had byte instructions. Regards, Jon.

Re: Device Independence

> Steve Thompson wrote:> It causes me to wonder, why DSORG causes a problem > with a path or  > a file. After all, unless you know something special about the > file, aren't all files DSORG=PS -- Physical Sequential in EXT, > EXT2, btrfs, hfs, zfs, etc.?  Ok, in hfs and zfs they are >

Re: Device Independence

>> Jon wrote: >> Programs do not access Unix files. Specifying path >> causes a Unix address space to handle the file. >> It communicates with the program thru the subsystem file> Paul wrote: > Isn't the same true for JES files? Yes > Paul wrote: > Spitefully, I tried a concatenation of a

Re: Fair comparison C vs HLASM

> Robin Vowels wrote: > And I understand that RISC processors came long after C. The word RISC was coined long after C. The actual architecture existed long before C. Regards, Jon.

Re: Fair comparison C vs HLASM

> Kirk wrote: > I'm not sure what "fair" means the context of > comparing HLASM and C/C++. (IMO, all C programmers should be > using C++ if possible, even if you choose to restrict > yourself to a small subset like we do). Google doesn't agree with C and C++ because they encourage application

Re: Fair comparison C vs HLASM

On Wednesday, January 31, 2018 1:00 AM, Robin Vowels wrote: From: "Keith Moe" Sent: Tuesday, January 30, 2018 11:08 AM >> Keith Moe wrote: >> One of the downsides to such great optimization >> is the added difficulty in debugging. > Robin Vowels

Re: Fair comparison C vs HLASM

> Ze'ev wrote: > You basically say "System System on the wall, > please bring me my file" and automagically, your > file appears! (even if it was stored on a third > level storage). You basically cannot implement that in Unix. This is totally possible and easy to create using a virtual file

Re: Fair comparison C vs HLASM

> Paul Raulerson wrote: > This is a funny area to compare though, since on most platforms, > C file > access is always a binary stream. The application pretty > much defines the > way the file is treated - byte by byte, > record by record, block by block, > buffer size by buffer > size, etc.

Re: Fair comparison C vs HLASM

>>> Eric Chavalier wrote: Going even further, many platforms allow a file to be >>> mapped into an >>>application's address space. I work with an unmanaged C++ Windows >>>application that does CreateFile() to open a file, >> Binyamin Dissen wrote: You are referring to a LDS. > Paul Raulerson

Re: Fair comparison C vs HLASM

> Paul Raulerson wrote: I think it can be argued that the > c library provides a complete, and easily extended or > modified equivalent of HLASM macro processing. Sorry but I've shown time and again this is not possible for C. In a previous post, I showed XML parse use in pseudo C logic and

Re: Fair comparison C vs HLASM

>> Jon Perryman wrote: >> For large complicated problems, assembler is the language of choice. > Martin Ward wrote: > For large complicated problems a domain-specific language, > targeted at the problem domain, is the language of choice. IBM assembler is the only langu

Re: Fair comparison C vs HLASM

> Martin Ward wrote: >> On 29/01/18 22:54, Jon Perryman wrote: >> Is there a PL/X or C feature that could not be implemented in HLASM? > I have already mentioned the automated application of > loop optimisations such as strength reduction, code motion, > Also, loc

  1   2   3   >