OLE and ooRexx (Re: Using EHLLAPI from ooRexx

Sorry, my bad.  "autECLConnList" is probably an array so you may want to try either "str = autoECLConnList[1]~name" or "str = autoECLConnLista~t(1)~name" instead. ( VBA/OLE arrays may use indexes from 0 up to size-1, but could also - and sometimes do - arbitrarily define the lower bound index a

EHLLAPI and connInfo (Re: OLE and ooRexx (Re: Using EHLLAPI from ooRexx

On 01.07.2023 14:17, Rony G. Flatscher wrote: Sorry, my bad.  "autECLConnList" is probably an array so you may want to try either "str = autoECLConnList[1]~name" or "str = autoECLConnLista~t(1)~name" instead. Ah, just saw in the ooRexx support list that Erich was able to introspect it (so he pr

Re: z/OSMF

Brian W wrote: So is IBM definitely dropping support for the z13s BEFORE z/OS 3.1 is officially out? If not, then it should be supported by z/OS 3.1. . . The conclusion expressed after the "If not" is not warranted. Dropping of support for a machine is unrelated to what machine an operating

0C1 abend

How do I resolve a 0C1 abend. what is normally the cause? thanks Bill -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: 0C1 abend

What do the registers and PSW say? You could have branched into data or into the PSA. Branching into the PSA is often caused by a missing or xero address, for example you had weak externals that were not resolved or some vector/branch table that was not populated. Or you could have overwriten

Re: 0C1 abend

So this is for BMC Unload for Db2. A few changes, first z/OS upgrade to v2.5. Then applied DB2 RSU2305 maintenance, Then activated Db2 function Level 509. I am wondering if any of these are the cause On Sat, 1 Jul 2023 08:09:12 -0500, Stephen Donaldson wrote: >What do the registers and

Re: 0C1 abend

I wouldn't be able to rule out anything. Do you just want to identify the module or get some detail for IBM or BMC or is there some user code/exit that potentially needs remediation? I previously answered as though it were the latter.

Re: 0C1 abend

The "normal cause" is that an invalid opcode came up in the CPU's eternal quest for things to do. What led to this could be any of a myriad of things. You will need to find someone who knows the rudiments of debugging to start on a resolution. Any specific answer you see on this mailing list is

Re: A Discussion about RLSE on RAID Drives with Chat GPT-4

On Thu, 29 Jun 2023 18:10:06 -0500, Hobart Spitz wrote: >https://chat.openai.com/share/1718b445-7a89-47a3-ab23-b670aa8c2211 That URL gives a 404 error, for me. Perhaps you could have your conversation again, and quote the conversation here directly next time? -- Walt ---

Re: Is there a USS-file compatible equivalent to the SUPERC OVSUM compare yet?

Thanks, Sebastian! As far as I know (or could read at the links below), grep wouldn't do what I need (comparing the files), but I appreciate the proper git-hub link to the tools & toys! I thought I'd found that earlier, but if so, I must have come at in in a filtered manner. That wjsckmp rexx

Re: 0C1 abend

We just upgraded to z/OS 2.5 and no changes to DB2 or BMC DB2 Utilities (since we did not have a SME support and thought (incorrectly) that we do not need any manintence for DB2 or BMC). This was until a user run BMC Unload with Direct set to Yes/AUTO and received 0C1. They changed Direct to No

Re: 0C1 abend

On Sat, 1 Jul 2023 10:22:23 -0400, Steve Smith wrote: >The "normal cause" is that an invalid opcode came up in the CPU's eternal >quest for things to do. > "quest for things to do" sounds like speculative execution. What happens to a program check in speculative execution? Does it speculatively

Re: EHLLAPI and connInfo (Re: OLE and ooRexx (Re: Using EHLLAPI from ooRexx

Thanks Rony. Further exchanges with Erich on the ooRexx Help discussion have also given me the information I need to access the autECLFieldList results. There is a function "FieldInfo" that takes an integer argument to retrieve that member of the FieldList object array, from which you can use/

Where am I going wrong with XLC __TIMESTAMP__ ?

I am using XLC __TIMESTAMP__ for the first (!) time. The source file is in UNIX and definitely has a timestamp. Here is the code static const char versionMsg[] = "blah blah, Built " __DATE__ " " __TIME__ ", Source timestamp " __TIMESTAMP__ ; The message is displaying as blah blah, Built Jul

Re: 0C1 abend

Check any link edit for unresolved XTRN. One of a myriad of causers. On Sun, Jul 2, 2023 at 4:15 AM Paul Gilmartin < 042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote: > On Sat, 1 Jul 2023 10:22:23 -0400, Steve Smith wrote: > > >The "normal cause" is that an invalid opcode came up in the CPU

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

On Sat, 1 Jul 2023 16:52:20 -0500, Charles Mills wrote: >... >The message is displaying as > >blah blah, Built Jul 1 2023 14:12:35, Source timestamp Mon Jan 1 0:00:01 >1990 > >There is one i#include ahead of the char[] and it is also a UNIX file with a >timestamp. > Does "Mon Jan 1

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

Jan 1 1990 is POSIX epoch start in USS, so you are getting 0 for the time value somehow. On Sun, Jul 2, 2023 at 11:24 AM Paul Gilmartin < 042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote: > On Sat, 1 Jul 2023 16:52:20 -0500, Charles Mills wrote: > >... > >The message is displaying as >

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

On Sun, 2 Jul 2023 11:52:43 +1000, Attila Fogarasi wrote: >Jan 1 1990 is POSIX epoch start in USS, so you are getting 0 for the time >value somehow. > WTF?! -- gil ---

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

On Sat, 1 Jul 2023 21:00:34 -0500, Paul Gilmartin wrote: >On Sun, 2 Jul 2023 11:52:43 +1000, Attila Fogarasi wrote: > >>Jan 1 1990 is POSIX epoch start in USS, so you are getting 0 for the time >>value somehow. >> >WTF?! >

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

On Sat, 1 Jul 2023 20:24:04 -0500, Paul Gilmartin wrote: >Does "Mon Jan 1 0:00:01 1990 mean anything to you? I was in Paris for New Year's. It was fantastic. We drank champagne until it ran out, and then moved on to homemade grappa. We sang songs from West Side Story. I slept until noon. Se

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

Looks like a but with XL C++. I would open a case with IBM > xlC -o posts posts.cpp && ./posts blah blah, Built Jul 2 2023 10:51:48, Source timestamp Mon Jan 1 0:00:01 1990 > ibm-clang++64 -o posts posts.cpp && ./posts blah blah, Built Jul 2 2023 10:52:08, Source timestamp Sun Jul 2 10:49:

Re: Where am I going wrong with XLC __TIMESTAMP__ ?

On Sat, 1 Jul 2023 21:34:25 -0500, Charles Mills wrote: > >Seriously, the IBM doc lists it as the value returned if no timestamp is >available. > They should specify which timestamp: ISPF, UNIX, FAMS, ... and which dominates if they disagree. RCF. >>What is the timestamp of the "one i#include"?

Re: z/OSMF

Bummer, However, this is exactly the kind of thing I was looking for. It's better to know, than to guess (or hope). Do you know what the z14+ functions might be? Brian -- For IBM-MAIN subscribe / signoff / archive access inst