>My post did not come out as I expected. No flowing. I'm going to shut up.
I concur.
When I read the explanation regarding "leading or trailing" blanks, I thought I
finally understand. Then came your post, and I'm back to "I don't have a clue
why it sometimes does work, and sometimes it does n
On 7/2/2018 5:45 PM, Charles Mills wrote:
Thanks. Can I do it with a UNIX command without programming?
Absolutely! If you write sysout from z/OS UNIX you are creating that
kind of output.
--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
https://
Thanks. Can I do it with a UNIX command without programming?
(Not that I don't love to program ...)
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Ed Jaffe
Sent: Monday, July 2, 2018 4:33 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Sub
Didn’t know you can put in parens to force sequence of execution
> On Jul 2, 2018, at 4:31 PM, Binyamin Dissen
> wrote:
>
> If I understand you correctly and you repetitively want this to occur, you
> will need:
>
> AT +8 (AT +C (off +c;call ..;go);go)
>
> (assuming you want the CALL
On 7/2/2018 3:22 PM, Charles Mills wrote:
The SSI manual makes repeated references to "transaction job IDs" and
"transaction job names."
What is a "transaction job" in this sense?
APPC/MVS and z/OS UNIX transactions create output, but are never
assigned complete JES job structures. For APPC/M
A good deal for MicroFocus. They bought the whole dang thing of Attachmate for
$1.2B. They just sold one part of that for $2.5B.
Wish I was that smart.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Rob Schramm
Sent: Monda
https://itsfoss.com/suse-eqt-acquisition/
Can anyone spell "we need cash"?
Rob Schramm
--
Rob Schramm
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message:
My post did not come out as I expected. No flowing. I'm going to shut up.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com
-Original Message-
From: IBM Ma
Sort of an amalgamation from long ago posts. Just trying to dodge the lightning
bolts. Guess it could mean senior techy too.
In a message dated 7/2/2018 5:06:42 PM Central Standard Time,
edja...@phoenixsoftware.com writes:
Was this intended to be "Señor Jaffe?" Or was it a comment on my age
There you go using them dang Unicode characters again.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Ed Jaffe
Sent: Monday, July 2, 2018 3:06 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Formatting (was: JCL ERROR : IGD0102
The SSI manual makes repeated references to "transaction job IDs" and
"transaction job names."
What is a "transaction job" in this sense?
Charles
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
On 7/2/2018 11:55 AM, Edward Finnell wrote:
I looked at the archives and Senior Jaffe's post appears correctly formatted.
It has plain/text and proportional font.
Was this intended to be "Señor Jaffe?" Or was it a comment on my age
and/or experience? ;-)
--
Phoenix Software International
Ed
On Mon, 2 Jul 2018 14:41:44 -0400, Steve Smith wrote:
>There appears to be a visceral urge in some to force others to conform to
>their great vision of the new and better way (ergo DST). That isn't at all
>necessary ... Just do it. Yourself.
>
Force? Not in that case. Set your wrist watch
D'accord - and the next 'complaint' will be about that pesky machine
code and how to get rid of it. Those who find JCL challenging argue that
it is not needed. As Aesop's fox said, "the grape is sour." My ha'penny. CP
On 02/07/2018 19:41, Steve Smith wrote:
> There appears to be a visceral urge in
The documentation for the z/OS V2.2 Binder API in the manual "z/OS MVS Program
Management: Advanced Facilities" in "Appendix D. Binder API buffer formats",
page 279 (PDF page count 297) has a footnote #3 for field ESD_ELEM_OFFSET which
says:
3. Calculated on the ED and ER records, required inpu
On Mon, 2 Jul 2018 15:53:02 -0400, Joe Monk wrote:
>I think it is saying that the system picks the volume from the referenced
>dsn, which must be cataloged (i.e. can't be a temp data set).
>On Mon, Jul 2, 2018 at 3:49 PM, Paul Gilmartin wrote:
>> >
>> > https://www.ibm.com/support/knowledgecente
Either way as long as the breakpoint instruction
Gets executed
I’ll try it when I get home thanks
Joe Reichman
170-10 73 rd ave
Fresh meadows NY 11366
> On Jul 2, 2018, at 4:31 PM, Binyamin Dissen
> wrote:
>
> If I understand you correctly and you repetitively want this to occur, you
> wil
If I understand you correctly and you repetitively want this to occur, you
will need:
AT +8 (AT +C (off +c;call ..;go);go)
(assuming you want the CALL after the STM)
On Mon, 2 Jul 2018 16:07:38 -0400 Joseph Reichman
wrote:
:>Binyamin
:>
:>For example AT +8 (CALL PROGRAM PARM(parms) RET
Binyamin
For example AT +8 (CALL PROGRAM PARM(parms) RETRUN(+C))
If +8 contains a STM r0,r15,saveregs in this scenario the STM is never
executed and return to +C
If for example at +8 (call program PARAM(parms) Return(+8)) the program is
called repeatedly
I would like what is +8 to get executed
On Mon, 2 Jul 2018 15:37:34 -0400 Joseph Reichman
wrote:
:>I have a TSO TEST breakpoint with a call subcommand when I return to the
:>offset of the breakpoint the program loops over and over again. When I
:>return to the NSI the instruction where the breakpoint is doesn't get
:>executed
I do not
Definitely an admin question. The other interlocutor is the distribution server
that takes the listserv post and spews it out to the subscribers. It may be
munging for compression or just that's all it knows.
In a message dated 7/2/2018 2:28:25 PM Central Standard Time,
000433f07816-dmarc-
I think it is saying that the system picks the volume from the referenced
dsn, which must be cataloged (i.e. can't be a temp data set).
Joe
On Mon, Jul 2, 2018 at 3:49 PM, Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Mon, 2 Jul 2018 15:07:07 -0400, Joe Monk wrote:
On Mon, 2 Jul 2018 15:07:07 -0400, Joe Monk wrote:
>REF allows you to place a data set on the same volume as the referenced
>data set. It must be cataloged on the system where it is referenced.
>
>https://www.ibm.com/support/knowledgecenter/en/CD_PROC_LANG/com.ibm.help.cdprocstmtsparams.doc/cdproc
Hi
I have a TSO TEST breakpoint with a call subcommand when I return to the
offset of the breakpoint the program loops over and over again. When I
return to the NSI the instruction where the breakpoint is doesn't get
executed
Thanks
On Mon, 2 Jul 2018 14:55:33 -0400, Edward Finnell wrote:
>I looked at the archives and Senior Jaffe's post appears correctly formatted.
>It has plain/text and proportional font.
>
In that post of Senior Jaffe's as it was initially distributed to me by
LISTSERV,
all sequences of multiple blanks
Folks:
If it is documented (and I don't have time to pull down the
latest doc), it will get addressed as a problem and not an RFE.
The C:D change team and the dev guys know the internals of the
product very well.
Regards,
Steve Thompson
On 07/02/2018 02:26 PM, Dyck, Lionel B. (RavenTek)
REF allows you to place a data set on the same volume as the referenced
data set. It must be cataloged on the system where it is referenced.
https://www.ibm.com/support/knowledgecenter/en/CD_PROC_LANG/com.ibm.help.cdprocstmtsparams.doc/cdproc_stmt_zos_Process_Parameters.html
Joe
On Mon, Jul 2, 2
I looked at the archives and Senior Jaffe's post appears correctly formatted.
It has plain/text and proportional font.
AFAIK, I've never had an issue posting code fragments on any list. I'm
gonna experiment with one right now randomly taken from our lo
There appears to be a visceral urge in some to force others to conform to
their great vision of the new and better way (ergo DST). That isn't at all
necessary in this case (nor DST). Just do it. Yourself. Now, or whenever
you have the time.
The simultaneous enqueue issue seems to be the bigges
I like this up to a point - I would prefer to have an execution command and
then be able to do if/then/else and another step, etc.
Or just use standard TSO allocation and program call syntax, perhaps simplified
to be more JCL 'like'
--
How about something like this?
Use REXX syntax and a JCL host command with JCL-like semantics:
/* REXX */
arg String /* From SUBMIT or start task command. */
"jcl job myjob: (acct),'john smith',class=t,msgclass=h,notify="userid()
"jcl exec pgm=myprog,parm="date("s")
"jcl sysprint: dd sysout=*"
AFAIK, I have never used KOI8-R; I can't speak to what m$ outhouse may have
done behind my back. Maybe it copied the charset from the message I was
responding to?
Do you have human beings doing had encoding of messages? If not, then I'm
obviously talking about software.
Alas, while I know of v
I don't think I can accept an RFE on this one - the documentation clearly shows
it should work :-)
That and we need it to work
--
Lionel B. Dyck (Contractor) <
Mainframe Systems Programmer – RavenTek Solution Partners
-
On Mon, 2 Jul 2018 11:10:31 -0700, Charles Mills wrote:
>Oh my gosh, you would have to maintain JCL forever for that and a dozen other
>reasons.
>
>BUT! Conceivably ... conceivably ... you might stabilize it and do everything
>new in Rexx going forward.
>
If the replacement had a superset of JC
On Mon, 2 Jul 2018 17:26:00 +, Dyck, Lionel B. (RavenTek) wrote:
>The use of VOL=SER=xx works but that is only useful for the 1st data set
>being copied. I've tried variations of ,'s also without success.
>
>Time for a PMR :-)
>
What if they tell you that has to be an RFE? (I suppose th
(Yaay! You're no longer using koi8-r!)
On Mon, 2 Jul 2018 17:06:08 +, Seymour J Metz wrote:
>Implementing any new RFC is a big order. If the mail clients on both ends
>implement RFC 3676, then cut-and-paste works. If a brain dead application
>simply slaps in format=flowed without following
Oh my gosh, you would have to maintain JCL forever for that and a dozen other
reasons.
BUT! Conceivably ... conceivably ... you might stabilize it and do everything
new in Rexx going forward.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.E
JCL and Connect:Direct syntax, while similar are not the same :-)
--
Lionel B. Dyck (Contractor) <
Mainframe Systems Programmer – RavenTek Solution Partners
-Original Message-
From: IBM Mainframe Discussion List [m
Suggestion
Code the parms on a DD statement and once you have that working
transfer it to the CD COPY Statement
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Dyck, Lionel B. (RavenTek)
Sent: Monday, July 2, 2018 10:34 AM
To
Once upon a time a LONG time ago this was a GUIDE requirement. It was
voted down due to the amount of automated systems that generated JCL.
You'd have to keep JCL, probably forever, because of those systems.
--
This message (and reply) was read by Google and the NSA.
--
The use of VOL=SER=xx works but that is only useful for the 1st data set
being copied. I've tried variations of ,'s also without success.
Time for a PMR :-)
--
Lionel B. Dyck (Contractor) <
Mainframe Systems Programmer
On Mon, 2 Jul 2018 10:31:58 -0600, Roger Bolan wrote:
>The syntax you showed makes me think that preceding commas are required.
>
That's what it seems to say, but does it mean it? Is this JCL, or an attempt to
replicate JCL syntax?
I can produce from this either:
VOL = ( , , , SER = ( seri
Implementing any new RFC is a big order. If the mail clients on both ends
implement RFC 3676, then cut-and-paste works. If a brain dead application
simply slaps in format=flowed without following the specifications in the RFC,
then blame that application. Again, do you know of any problem when b
AOL. We don't need any ethnic slurs here.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Gord Tomlin
Sent: Sunday, July 1, 2018 3:59 PM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: Looking for IMS
Well, your first two line don't have leading spaces and they didn't get warped
(sic).
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of Ed
Jaffe
Sent: Sunday, July 1, 2018 7:02 PM
To: IBM-MAIN@li
On 7/2/2018 6:07 AM, Michael Babcock wrote:
I still don’t see St. Louis in the SHARE app. Is that available yet or
.?
July 9th is the currently scheduled mobile app launch date...
--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
https://www.p
> This code looks fine. My experience in posting to IBM-MAIN is that spaces at
> the beginning *or end*
> of a line allows the data to look fine. But truncating both leading and
> trailing spaces causes the
>List processor to flow lines up to the next 'break',
That sounds seriously b0rken. Can
Hi Michael,
Hope all is well.
SHARE St. Louis will not be present in the SHARE App until we are closer to the
conference. However, in the meantime, the desktop version is available either
from the menu of event.share.org under Agenda/Technical Agenda, or by using
this url: https://events.sha
The syntax you showed makes me think that preceding commas are required.
On Mon, Jul 2, 2018, 9:43 AM Dyck, Lionel B. (RavenTek)
wrote:
> Using C:D 5.2 and yes I had tried that :-)
>
> The 'error' message, if that is what you want to call it, claims invalid
> VOL=SER= usage.
>
> Banging head ag
Parker Solar Probe to be launched on or after 2018-07-31.
Do not be silly Engelbrecht, Capt Kirk and crew will have gone (note the
tense) far closer back in the 1960's. ; ^ )
--
For IBM-MAIN subscribe / signoff / archive access
Using C:D 5.2 and yes I had tried that :-)
The 'error' message, if that is what you want to call it, claims invalid
VOL=SER= usage.
Banging head against the wall removes the pain of trying to figure this out but
that is only temporary.
--
Dyck, Lionel B. (RavenTek) wrote:
>After pouring thru the connect:direct pubs and finding that REF= is support,
>I've not been able to find the correct syntax to do a VOL=REF=dsn within a
>Connect:Direct Proc on the TO parameters.
>Can anyone offer any suggestions/advice/direction?
>The docume
After pouring thru the connect:direct pubs and finding that REF= is support,
I've not been able to find the correct syntax to do a VOL=REF=dsn within a
Connect:Direct Proc on the TO parameters.
Can anyone offer any suggestions/advice/direction?
The documented syntax is:
VOL = ( [PRIVATE],[RETA
On Sun, Jul 1, 2018 at 12:12 PM Hobart Spitz wrote:
> )Why don't we just skip the JCL, and write our jobs in REXX? The two
>
> Here, here!! Actually, there is one thing that is critical to retiring
> JCL. It's a host command that allows a REXX program to list and wait for
> all it's datasets
I still don’t see St. Louis in the SHARE app. Is that available yet or
.?
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
On Sat, 30 Jun 2018 06:27:59 -0700, Charles Mills wrote:
>A search of Google for seven-digit jobs leads to headhunter sites.
>
I am sure you deserve a seven-digit salary -- but are not getting it :-(
Try adding
site:ibm.com
to your Googling.
Cheers,
Jantje.
-
Arnold,
Thank you very much for your help, I appreciate it.
When talking about performance I also thouth about key "life management"
like new key, key change, key delete. I don't expect it would be very
frequent operation, but even that in multi-milion (10-20M rather than
2-3M) key database ca
57 matches
Mail list logo