Adventures in JCL: PROCs, symbols and instream data

2017-04-25 Thread Andrew Rowley
I am trying to create some JCL procedures using symbols in instream data, with the ability to override the symbol using standard procedure calling conventions. This almost works: //JOB1 JOB CLASS=A, // MSGCLASS=H, // NOTIFY= //* //TEST PROC MESSAGE='''Hello

IXGLOGR internal function

2017-04-25 Thread Nathan Astle
Hello, Is there any Documentation on how DB2 or any address space within z/OS are making use of IXGLOGR ? I Mean internally how are they making the use of IXGLOGR ? The question is just for the knowledge sake and wanted to understand how Logstream structures created are making use of IXGLOGR.

Re: Vendor Licensing Frustrations

2017-04-25 Thread Timothy Sipples
Edward Gould wrote: >I can’t talk for others but IBM can’t seem to handle the Internet. Apparently you missed the part where I explicitly described not relying solely on any one entity. And only within the context of extending a generous 90 day window. (If two entities are Internet unreachable

Re: Vendor Licensing Frustrations

2017-04-25 Thread Timothy Sipples
Lionel Dyck wrote: >I've been working on DR planning for one of our locations and out >of 15 non-IBM products, ONLY 3 will continue to operate without temp >codes, and of those 3, 1 expires after 2 days and the others after 7 >days. For the 12 vendor products I have to contact 7 different vendors

Re: program-name is unresolved/uncallable

2017-04-25 Thread Clark Morris
[Default] On 25 Apr 2017 09:24:18 -0700, in bit.listserv.ibm-main rpomm...@sfgmembers.com (Pommier, Rex) wrote: >Hello, > >I have what I am suspecting will be an easy question but I haven't found the >answer yet. We have jobs that, while running, they will display message >"program-name IS

Re: Vendor Licensing Frustrations

2017-04-25 Thread Edward Gould
> On Apr 25, 2017, at 6:19 PM, Farley, Peter x23353 > wrote: > > Not intending to raise a political/social issue, but I think it is apropos > the subject. What about the "bad actors" out there in places like Russia and > certain rogue parts of the Middle East and

Re: Vendor Licensing Frustrations

2017-04-25 Thread Edward Gould
> On Apr 25, 2017, at 5:49 PM, Phil Smith wrote: > > scott Ford wrote: >> What about theft of software products ? We all know it goes on ... >> How do you prevent it ? > > When I see someone assert that "We all know it goes on", I don't see it as a > meaningful statement.

Re: Vendor Licensing Frustrations

2017-04-25 Thread Farley, Peter x23353
Not intending to raise a political/social issue, but I think it is apropos the subject. What about the "bad actors" out there in places like Russia and certain rogue parts of the Middle East and Asia? Is software theft by those regions not also a licensing loss issue? I don't have any

Re: Can XLC printf() take "%D(*,*)"?

2017-04-25 Thread Charles Mills
Hmmm. Thanks. Link certainly seems relevant. (Interesting -- the page that opens is some weird VM-z/OS hybrid: z/VM z/VM 6.2.0 IBM XL C/C++ for z/VM z/OS: XL C/C++ Programming Guide Coding: Advanced Topics Using decimal data types in C Programming examples.) But I find the same example in the z/OS

Re: Vendor Licensing Frustrations

2017-04-25 Thread Phil Smith
scott Ford wrote: >What about theft of software products ? We all know it goes on ... >How do you prevent it ? When I see someone assert that "We all know it goes on", I don't see it as a meaningful statement. Spontaneous fission also occurs, but not enough for me to worry about it. There have

Re: Can XLC printf() take "%D(*,*)"?

2017-04-25 Thread David W Noon
On Tue, 25 Apr 2017 15:11:09 -0700, Charles Mills (charl...@mcn.org) wrote about "Can XLC printf() take "%D(*,*)"?" (in <0c3301d2be10$d87ed2b0$897c7810$@mcn.org>): > I'd like to format fixed point decimal (packed, in other words) numbers in a > common subroutine that would be passed the precision

CEE3551S DLL xxxxxxxx does not contain any C functions.

2017-04-25 Thread Bill Woodger
On Tuesday, 25 April 2017 21:15:57 UTC+2, Dan Kalmar wrote: > I am calling an LE assembler routine from Enterprise COBOL batch program and > receive the CEE3551S error message. > > The call made in cobol is the dynamic type. > > Not sure why LE thinks the target program is expected to contain

Can XLC printf() take "%D(*,*)"?

2017-04-25 Thread Charles Mills
I'd like to format fixed point decimal (packed, in other words) numbers in a common subroutine that would be passed the precision and scaling. Can printf() and friends take '*' and then a passed integer for its (n,p) values - analogous to the way printf() width and precision may be specified?

Re: IBM z/OS Systems Programmer Wanted -- Consultant / Contractor

2017-04-25 Thread Gilson, Lynn
Gabe, I've applied and am forwarding this back to you thru ListServ (didn't see your personal or biz email). Many thanks! Lynn Gilson -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Gabe Goldberg Sent: Tuesday, April 25, 2017 1:34

IBM z/OS Systems Programmer Wanted -- Consultant / Contractor

2017-04-25 Thread Gabe Goldberg
I'm forwarding for colleague -- respond as requested below, not to me (but OK to copy me so I see this worked). IBM z/OS Systems Programmer Wanted Consultant / Contractor Requires highly experienced systems programmer capable of performing all conceivable z/OS tasks such as maintaining IOCDS,

Re: FTP Failing with space issues

2017-04-25 Thread Ron Thomas
The criteria we are planning is the files which are more than 30 days old (Creation Date). Thanks! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message:

Re: SETRP with DUMP=YES

2017-04-25 Thread Binyamin Dissen
Because, sadly, I do not expect to live forever. On Tue, 25 Apr 2017 13:30:23 -0400 Steve Smith wrote: :>Sometimes, I just get enough fed up with badly designed/written* macros :>that I re-write them myself. Or in SETRP's case, why not just code your :>own flag settings?

Re: FTP Failing with space issues

2017-04-25 Thread John McKown
On Tue, Apr 25, 2017 at 2:18 PM, Ron Thomas wrote: > We finally decided to move the files to Z/OS unix , we plan to create a > monthly folder to which we push all the files from linux VM. Once the file > is there we will move back to GDG's . I have a query here , is there any

Re: program-name is unresolved/uncallable

2017-04-25 Thread David W Noon
On Tue, 25 Apr 2017 14:12:20 -0500, Tom Marchant (000a2a8c2020-dmarc-requ...@listserv.ua.edu) wrote about "Re: program-name is unresolved/uncallable" (in <7268174283864055.wa.m42tomibmmainyahoo@listserv.ua.edu>): > On Tue, 25 Apr 2017 14:08:06 -0400, Farley, Peter wrote: > >> IMHO that

Re: FTP Failing with space issues

2017-04-25 Thread Jousma, David
IBM provides a sample script called skulker. I use it to clean out /tmp on a daily basis for stuff older than a certain number of days old, and is scheduled in CRONTAB # Skulker # Remove files from (first argument) that

Re: FTP Failing with space issues

2017-04-25 Thread Ron Thomas
We finally decided to move the files to Z/OS unix , we plan to create a monthly folder to which we push all the files from linux VM. Once the file is there we will move back to GDG's . I have a query here , is there any job which i can use to clean up the files in the z/os unix folder . Please

Re: program-name is unresolved/uncallable

2017-04-25 Thread Tom Marchant
On Tue, 25 Apr 2017 14:08:06 -0400, Farley, Peter wrote: >IMHO that is just sloppy application coding that would not pass a peer >review by me. It is trivially easy to set and test a flag to remember you >already issued a given message already and bypass issuing it repeatedly, I'd go even

Re: program-name is unresolved/uncallable

2017-04-25 Thread Charles Mills
The lack of a message number would tend to indicate a "homegrown" message. I think nearly all IBM, and hopefully most 3rd-pary vendor, messages have a more-or-less standard sort of message id. "Local" programmers have a tendency I think to "just say something on the console/SYSPRINT." Charles

Re: program-name is unresolved/uncallable

2017-04-25 Thread Farley, Peter x23353
In that case I would contact the application group manager who owns that program and require them to schedule a change to the code to issue such a message only once (on first encountering the failure to locate that subroutine for execution) instead of blindly issuing the message every time.

Re: program-name is unresolved/uncallable

2017-04-25 Thread Cieri, Anthony
If you just want to remove the messages from the console, then I think MPF would work!! An entry like: CKDCISLC,SUP(YES) /* Suppress message from console */ The '+' sign should not be necessary! This won't remove the messages from the job

Re: program-name is unresolved/uncallable

2017-04-25 Thread John McKown
On Tue, Apr 25, 2017 at 12:26 PM, Pommier, Rex wrote: > Unfortunately that is the complete message text. > > 10.54.31 JOB00450 +CKDCISLC IS UNRESOLVED/UNCALLABLE > 10.54.31 JOB00450 +CKDCISLC IS UNRESOLVED/UNCALLABLE > > > After I posted the question, I did some more

Re: SETRP with DUMP=YES

2017-04-25 Thread Steve Smith
Sometimes, I just get enough fed up with badly designed/written* macros that I re-write them myself. Or in SETRP's case, why not just code your own flag settings? The SDWA is well-documented, and has a complete DSECT[s]. sas * SETRP hasn't caused *me* any problem. Many other IBM macros have,

Re: program-name is unresolved/uncallable

2017-04-25 Thread Pommier, Rex
Unfortunately that is the complete message text. 10.54.31 JOB00450 +CKDCISLC IS UNRESOLVED/UNCALLABLE 10.54.31 JOB00450 +CKDCISLC IS UNRESOLVED/UNCALLABLE After I posted the question, I did some more digging and found the message text embedded in the program being executed. It appears

Re: program-name is unresolved/uncallable

2017-04-25 Thread Charles Mills
Is there a message number? Any idea what specific component is outputting that message? Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Pommier, Rex Sent: Tuesday, April 25, 2017 9:25 AM To: IBM-MAIN@LISTSERV.UA.EDU

AT-TLS replace ICF processor ?

2017-04-25 Thread Nathan Astle
Hi Cross posted Not trying to.resolve anything. Recently had a discussion with a TCPIP/SNA person and he feels that most of the task offloaded to ICF processor can be handled by AT-TLS. I was not.able to make any sense out of it. Aren't ICF processor independent of AT-TLS ? Nathan

Re: program-name is unresolved/uncallable

2017-04-25 Thread Lizette Koehler
Could you provide the complete message and text? Easier to analyze that way. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Pommier, Rex > Sent: Tuesday, April 25, 2017 9:25 AM > To: IBM-MAIN@LISTSERV.UA.EDU >

program-name is unresolved/uncallable

2017-04-25 Thread Pommier, Rex
Hello, I have what I am suspecting will be an easy question but I haven't found the answer yet. We have jobs that, while running, they will display message "program-name IS UNRESOLVED/UNCALLABLE" multiple times on the console as well as in the programmer's job log. Is the elimination of

Re: Vendor Licensing Frustrations

2017-04-25 Thread Allan Staller
The "new tools" are neither as reliable, function, or available as their predecessors, let alone z/OS. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edward Gould Sent: Tuesday, April 25, 2017 10:15 AM To: IBM-MAIN@LISTSERV.UA.EDU

Re: SETRP with DUMP=YES

2017-04-25 Thread Charles Mills
And an IMREALLYTRULYPOSITIVEABOUTWHATIAMDOING=NO(default)/YES keyword for the really risky options. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Binyamin Dissen Sent: Tuesday, April 25, 2017 8:05 AM To:

Re: Vendor Licensing Frustrations

2017-04-25 Thread Edward Gould
> On Apr 23, 2017, at 8:40 PM, Timothy Sipples wrote: > > ——SNIP-- > Yet another way to handle keys (IF you must, and I don't recommend them) is > a "break glass in an emergency" way. You put the "emergency"

Re: SMS STORGRP question

2017-04-25 Thread Greg Shirey
Defining a storage group as OVERFLOW provides most of that function by default. I believe the difference is that QUINEW volumes are used as a "last resort" whereas OVERFLOW volumes are used when the high threshold will be exceeded. >From "defining storage group attributes" in the Knowledge

Re: FTP Failing with space issues

2017-04-25 Thread Paul Gilmartin
On Tue, 25 Apr 2017 05:39:18 -0500, Walt Farrell wrote: >On Mon, 24 Apr 2017 21:30:28 -0500, Paul Gilmartin >wrote: > >>... so I tried: >> >>548 $ sudo cat ~wombat/.ssh/rc >>/bin/id >>/bin/uname >>/bin/date >> >>... I see no evidence that the commands in ~wombat/.ssh/rc

Re: SETRP with DUMP=YES

2017-04-25 Thread Binyamin Dissen
On Tue, 25 Apr 2017 07:59:48 -0400 Peter Relson wrote: :> :>It would be nice if one could :> :> IF condition1 :> SETRP to return 64 :> if condition2 :> free local lock :> if condition3 :>

Re: SMS STORGRP question

2017-04-25 Thread Schroeder, Wayne
Hey Jesse, I have the same setup but I have my OVERFLOW volumes set as QUINEW so they are only used if the original SG can't hold all of the data. Hope this helps. Wayne Schroeder Mainframe Storage Administrator T 254.399.5070 M 254.644.8534 E wschroe...@txfb-ins.com 7420 Fish Pond Rd. Waco,

Re: KC Authentication failed

2017-04-25 Thread Susan Shumway
Hi Tom, I'm glad you're back up and running. Thanks for the feedback re: general IBM site 'walkabouts' and the z/OS Internet Library - I'll pass it along as usual. Yours truly, Sue Shumway On 04/24/17 10:25 PM, Tom Conley wrote: On 4/24/2017 3:43 PM, Susan Shumway wrote: Tom, are you

Re: SETRP with DUMP=YES

2017-04-25 Thread Peter Relson
It would be nice if one could IF condition1 SETRP to return 64 if condition2 free local lock if condition3 set retry addr1 IF condition4 set retry addr2

Re: FTP Failing with space issues

2017-04-25 Thread Walt Farrell
On Mon, 24 Apr 2017 21:30:28 -0500, Paul Gilmartin wrote: >... so I tried: > >548 $ sudo cat ~wombat/.ssh/rc >/bin/id >/bin/uname >/bin/date > >... I see no evidence that the commands in ~wombat/.ssh/rc were executed. >I can't tell exactly what happened. Nor does the man