On Wed, 15 Apr 2020 16:05:59 +0800, David Crayford wrote:
>
>For a brute force solution you could just create symlinks (shortcuts) to
>your *.java files with *.jav extensions. Trial to write a PowerShell
>script to do that.
>
There's some irony here:
Information for the MQSERIES listserv can be found here:
https://listserv.meduniwien.ac.at/archives/mqser-l.html
It’s an active mailing list.
Sent from my iPhone
> On Apr 14, 2020, at 6:03 PM, Seymour J Metz wrote:
>
> This is a correct list for your question. There may be a more
Thanks, I'll bear it in mind when I cross that bridge. Cheers.
On 15/04/2020 09:05, David Crayford wrote:
> Trouble is you will have to write your (non-trivial) annotation
> processor in Java so it's a chicken and the egg problem.
>
> For a brute force solution you could just create symlinks
I think the CHANGE command of the linkage editor will do what you want;
I remember to have used it when building a sort of "universal DB2
interface"
out of the IBM delivered environment specific interfaces called DSNALI,
DSNELI, DSNRLI etc.
They all provide an entry DSNHLI, which is normally
On 4/15/2020 3:06 PM, Roger Lowe wrote:
On Wed, 15 Apr 2020 07:15:16 -0700, Charles Mills wrote:
Given a COBOL-based load module, is there a way to tell what COBOL compiler
(including version) the main module was built with? Is there a "tag" in the
object code that says "this was compiled by
Thanks Peter; I had looked for an update, but not in the correct place. The new
version works much better!
B
-- Original Message --
From: "Farley, Peter x23353"
To: IBM-MAIN@listserv.ua.edu
Sent: 4/15/2020 4:49:15 PM
Subject: Re: How tell what verion of COBOL compiler produced load
Sorry. CHANGE. Looked right at it and typed RENAME.
I believe order of statements is that CHANGE applies to what has come before.
Ah. Read the fine manual. You want
CHANGE AX(AXMINUS)
Right *before* the include for the old AX module:
"Placement: In the job stream or input data set, the
Did you get the newer V1.52 from the CBT UPDATES page or the older version from
the main DL page?
Peter
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Billy Ashton
Sent: Wednesday, April 15, 2020 2:43 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How tell what
I think I'd be unlikely to get it right on the first try. I had never even
heard of the "RENAME" statement, but it exists, alongside the venerable
"CHANGE" statement. I don't presently have the time to sort that out. And
the required order of statements is sometimes surprising. Nevertheless,
Look at the binder CHANGE directive
On Wed, 15 Apr 2020 15:43:49 -0400 Phil Smith III wrote:
:>I have a use case that's reasonable enough that it might be supported, yet
odd enough that I'd be unsurprised if it isn't.
:>
:>
:>
:>Suppose we have a function called AX that we call. At times it
So every call to AX would instead call an entrypoint within a new module
(except for one call from within that new module, which would call the old
AX)?
Yes, I think binder RENAME can do that.
Code the new module to with a hard-coded entry of AX and an internal call to
AXMINUS. No point in
On Wed, 15 Apr 2020 15:43:49 -0400, Phil Smith III wrote:
>I have a use case that's reasonable enough that it might be supported, yet odd
>enough that I'd be unsurprised if it isn't.
>
>Suppose we have a function called AX that we call. At times it would be useful
>to be able to relink a
I have a use case that's reasonable enough that it might be supported, yet odd
enough that I'd be unsurprised if it isn't.
Suppose we have a function called AX that we call. At times it would be useful
to be able to relink a program that calls AX to add a "shim"-let's call it
Code Explanation
04 A LOAD macro was issued with conflicting options. One of the following
occurred:
v The EOM (delete module at end of memory) keyword, with the GLOBAL keyword
omitted. The EOM
keyword applies only if the module is loaded into CSA storage.
v The GLOBAL and ADDR keywords are both
On Wed, 15 Apr 2020 07:15:16 -0700, Charles Mills wrote:
>Given a COBOL-based load module, is there a way to tell what COBOL compiler
>(including version) the main module was built with? Is there a "tag" in the
>object code that says "this was compiled by (for example) Enterprise COBOL
>V6R3M0?"
I just tried to assemble and run the COBANALZ program, but got S206-04
on multiple libraries...not sure what to do with that, as I haven't got
time to troubleshoot this.
Billy
-- Original Message --
From: "Farley, Peter x23353"
To: IBM-MAIN@listserv.ua.edu
Sent: 4/15/2020 2:30:10 PM
AMBLIST has
TRANSLATOR VER MOD DATETIME
CSECT:progname
5655EC6 060204/15/2020
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Enterprise COBOL "signature" now uses "CEE" not C1 or C2 (actually
X'01C3C5C5'). Need to find the LE PPA2 data block and from there find the
compiler timestamp, which is followed by the version / release / modlevel bytes
(e.g. 20190924143846050200, which says version 05, release 02, modlevel
Cobol has a signature, at least used to have, in the load module date&
time. C1 for os/vs Cobol, C2 for cobol 2. I believe ibm maintains same
signature for ent. Version.
ITschak
בתאריך יום ד׳, 15 באפר׳ 2020, 20:18, מאת Pommier, Rex <
rpomm...@sfgmembers.com>:
> Oops, I missed your "ignore my
Oops, I missed your "ignore my comment" before I responded to the last one.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Farley, Peter x23353
Sent: Wednesday, April 15, 2020 12:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [External] Re: How tell what verion of
Filemanager version 13.1 has option 3.10 as the loadlib option. Hasn't version
10 been out of service for several years?
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Farley, Peter x23353
Sent: Wednesday, April 15, 2020 12:11 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Sorry, ignore that comment. "FM" here is CA FileMaster, not IBM FileManager.
Apologies for my confusion.
Peter
-Original Message-
From: Farley, Peter x23353
Sent: Wednesday, April 15, 2020 1:11 PM
To: IBM Mainframe Discussion List
Subject: RE: How tell what verion of COBOL compiler
Don't know what version of FM you are using, but we have FM V10.0 here and FM
3.10 is their "COMPARE" utility, no sub-menus.
FM 3.13 is "LOADINFO", is that the feature you are talking about? I ran that
on a COBOL V6.2 program object and no COBOL compiler information was generated,
only binder
Got it. Thanks.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@listserv.ua..edu] On
Behalf Of Steve Smith
Sent: Wednesday, April 15, 2020 9:33 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How tell what verion of COBOL compiler produced load module?
First, Filemanager, then 3.10 (and then 1-View). It's not on the ISPF
Utilities menu. I've no way of knowing if or how to start Filemanager on
anything but my own systems. You might have to poke around, or ask the
Powers-That-Be. Or you may not have it, or of course, have sysadmins that
assume
My ISPF 3 goes straight from 9 to 11!
9 CommandsCreate/change an application command table
11 Format Format definition for formatted data Edit/Browse
But yes, thanks all on AMBLIST. Does the job.
Charles
-Original Message-
From: IBM Mainframe Discussion
AMBLIST is the easy & always-available way to LISTIDR. If you have
FileManager, option 3.10 lets you view them in ISPF. It also expands the
compiler IDs to readable text, and can also humanize the dates.
sas
Given a COBOL-based load module, is there a way to tell what COBOL compiler
>
I should have said "I think so"! Windows and Linux are used everywhere
including military systems. It may unsettle some peeps on this list but
Windows is used on warships
https://www.computerworld.com/article/2939435/us-navy-paid-millions-to-stay-on-windows-xp.html
On 2020-04-15 11:49 PM,
And they don't use Windows/Linux? I think not!
On 2020-04-15 11:45 PM, Farley, Peter x23353 wrote:
Not obsolete if you want / need to sell to the USA federal government or to
many of the state and local governments as well.
Peter
-Original Message-
From: IBM Mainframe Discussion List
Not obsolete if you want / need to sell to the USA federal government or to
many of the state and local governments as well.
Peter
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
David Crayford
Sent: Wednesday, April 15, 2020 10:47 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Timothy,
Very nice. Many of us old folks don’t remember. Wasn’t z/OS Unix System
Services based on Posix ? It’s seems I heard this sometime ago.
Regards,
Scott
On Wed, Apr 15, 2020 at 10:47 AM David Crayford wrote:
> Isn't this all obsolete now? Linux and Windows are used everywhere and I
>
Isn't this all obsolete now? Linux and Windows are used everywhere and I
doubt anybody cares about POSIX certification.
On 2020-04-15 10:01 PM, Charles Mills wrote:
Well, you've obviously researched it more than I care to.
I guess this is what I am thinking of: "The NT POSIX subsystem was
CBT file 321, COBANALZ does a pretty good job of extracting that information
(and more). DUMMY the SYSPRINT output (usually much more detail than you need
for this level of analysis) and use the SUMMARY DD to see the consolidated
results.
HTH
Peter
-Original Message-
From: IBM
Look at the IDR data.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Charles Mills [charl...@mcn.org]
Sent: Wednesday, April 15, 2020 10:15 AM
To:
Given a COBOL-based load module, is there a way to tell what COBOL compiler
(including version) the main module was built with? Is there a "tag" in the
object code that says "this was compiled by (for example) Enterprise COBOL
V6R3M0?"
Charles
Well, you've obviously researched it more than I care to.
I guess this is what I am thinking of: "The NT POSIX subsystem was included
with the first versions of Windows NT because of 1980s US federal government
requirements listed in Federal Information Processing Standard (FIPS)
151-2.[1]
On an individual user basis, the easiest method on a V2.3 system or higher is
to use the new JOBGROUP feature.
//JOBT JOBGROUP ERROR=(RC>4),ONERROR=FLUSH
//JOBA GJOB
//JOBB GJOB
// AFTER
The fun part is trying to explain to programmers where the messages go. They
think they don’t use dasd for some reason. My old company basically replaced a
CICS/VSAM batch process with a CICS/MQ/PAGESET batch process.
Sent from Yahoo Mail for iPhone
On Wednesday, April 15, 2020, 8:51 AM,
Yeah, that’s the danger of using queues (pagesets) as a data storage facility.
And partially why IBM says not to use them as such.
Sent from Yahoo Mail for iPhone
On Wednesday, April 15, 2020, 8:51 AM, Jantje. wrote:
On Wed, 15 Apr 2020 12:28:53 +, Bill Johnson wrote:
> Don't think
The OP's question was just curiosity. That question was answered. He
didn't ask *how* to schedule jobs to run in order.
Anyway, 2/3 of the ways listed do *not* guarantee execution order (in fact
they have no effect at all on a series of jobs with the same name). And
multiple systems can affect
JES job number is unique (guaranteed).
Absent son other priority mechanism, jobs are selected FIFO with job class.
Jobs are queued at the end of conversion. This is unique to (at least) 1 /100th
sec.
If there are multiple converters, each is dispatched uniquely and my finish a
few 1/00ths of a
Thanks again, Stuart.
After a couple issues convincing it to work I managed to get it cleared. 457K
records later the queue was empty. :-)
Rex
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Pommier, Rex
Sent: Tuesday, April 14, 2020 4:51 PM
To:
Hi Bill,
Short answer is because that pageset is in use by a bunch of queues and I
wanted to make sure I didn't clobber any data that might be in flight from a
different queue.
Thanks,
Rex
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Bill Johnson
Sent:
On Wed, 15 Apr 2020 12:28:53 +, Bill Johnson wrote:
> Don't think there is but the question I have is why are you afraid to delete
> and redefine the pageset?
Because lots of other stuff may be sitting in that pageset, besides that one
XMIT queue that can be very easily cleared with the
Here's some sample JCL if you need.
//**
//*
//* allocate the page set data sets//*
//DEFINE EXEC PGM=IDCAMS,REGION=4M
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEFINE CLUSTER -
As all of the responders have made clear, CSECT and ENTRY in the assembler
source are not directly relevant.
Only NAME and ALIAS (typically via binder control statements) are
relevant. CSECT and ENTRY are data that the binder uses to know to which
location the ALIAS is to apply. If the ALIAS
Don't think there is but the question I have is why are you afraid to delete
and redefine the pageset? (also needs formatted) It's a simple and fast
process. And, IBM always tells you, never use the pagesets as data storage
units. (for batch processing)
On Wednesday, April 15, 2020,
Trouble is you will have to write your (non-trivial) annotation
processor in Java so it's a chicken and the egg problem.
For a brute force solution you could just create symlinks (shortcuts) to
your *.java files with *.jav extensions. Trial to write a PowerShell
script to do that.
On
48 matches
Mail list logo
