Re: Question for COBOL users

2018-02-10 Thread Robert Prins 

On 2018-02-10 00:30, Charles Mills wrote:

That is how the C/C++ compiler works. PARM='OPTF(DD:SYSOPTF)' or any other
valid DD name, or DSN, or zFS name. Only one name, though.


Enterprise PL/I allows multiple DD names, like:

//IBMZPLI EXEC PGM=IBMZPLI,
// REGION=0M,
// PARM=('+DD:PLISTD +DD:PLIDB2 +DD:PLCICS +DD:PLIUSER')

which allows a site to set up defaults, but still giving the user a chance to 
override things. Works like a charm!


=DD:PLISTD could be set up to point to the IBMXOnnn members now conveniently 
added to the hlq.SIBMZSAM dataset containing such members for all still 
supported versions of Enterprise PL/I, an RFE 
 
yours truly suggested and that was implemented with EPLI V5.1.0


And for what it's worth, a SuperC compare of the various members will also show 
all options that have been altered/added with every release of EPLI.


Robert
--
Robert AH Prins
robert.ah.prins(a)gmail.com
Some programming  @ 



-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Frank Swarbrick
Sent: Friday, February 9, 2018 3:23 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Question for COBOL users

Our shop currently uses OPTFILE in conjunction with the SQL compiler option
in order to supply particular SQL "compile" options to the SQL precompiler
for those COBOL program that have EXEC SQL statements.  This allows us to 1)
avoid having a separate "DB2 batch" and "DB2 CICS" procs.  We simply use our
"standard" batch and CICS compile procs, and the SQL preprocessor is invoked
if the source code has "PROCESS SQL OPTFILE" at the top.  Our "SYSOPTF" has
the following:
SQL('STDSQL(YES) SQL(ALL) VERSION(AUTO)')

So the change that you suggest would indeed "break" our environment.  Well,
perhaps not, because I don't think it would do any harm to supply SQL
options for programs that don't have any SQL statements, but...

My personal wish would be that OPTFILE have an option to specify one or more
DD names that it would open, rather than SYSOPTF being the only name.  If
that had been available we'd probably use OPTFILE(DB2OPTF) or some such
thing.  Of course that doesn't really solve your particular RFE.  Sounds
like you need a new compiler option that tells the compiler to use SYSOPTF
if present, but only if the new option is specified.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Apply error WAS product

2018-02-10 Thread Lizette Koehler 
This was from a WAS 8.5 install

Upgrade WASAS850, Subset HBBO850

http://www-01.ibm.com/support/docview.wss?uid=isg1_WASAS850_HBBO850

I used Google and search terms   IBM HBBO850



If your existing copy of the WebSphere Application Server
 Liberty profile includes the extprogmodels install feature
 (included by default) or any Liberty features (such as
 zosConnect-1.0), and your z/OS system does not have access
 to the Web-based Liberty Repository (at ibm.com), you will
 need to edit the imcl.ini file in

/eclipse/tools

 and add the following text (on a single line):

 -Dwas.install.local.asset.location=/usr/lpp/
 InstallationManagerRepository/HBBO850/
 WLP/fixpacks/8.5.5.4

 If the WebSphere Application Server for z/OS SBBOIMR data
 set is mounted at a different location, modify the text in
 imcl.ini accordingly.

 For more information, see the following technote:

 http://www-01.ibm.com/support/docview.wss?uid=swg21692627



> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Peter
> Sent: Saturday, February 10, 2018 8:01 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Apply error WAS product
> 
> This is a monoplex... The program directory of the product didn't mention
> about this mount points ... It sounded like a product bug...
> 
> 
> 
> On 10-Feb-2018 8:17 PM, "Lizette Koehler"  wrote:
> 
> > Some Questions
> >
> > Is the LPAR this is running on, where the mount files reside?
> >
> > For example, you only have one LPAR this can run on?  Or is this a
> > SYSPLEX and it can run on more than one system?
> >
> > If this is a sysplex, make sure the file mounted where the job runs.
> > To do this, logon that that system and in ISPF using 3.17 (my
> > favorite) enter the mount point.  If it shows up, then enter FS next
> > to any file/dir in that file. Ensure names and locations for the run are
> correct.
> >
> > Or you can go to SDSF and issue  D OMVS,F,N=   and the N= would be the
> > actual MVS data set name.  Look for where the file is mounted
> >
> > Or you could go into report from the SMP APPLY and review the DDDEF
> > section.  Make sure the mount point used by SMPE is the right mount
> > point
> >
> >
> > Note:  This list typically will not allow attachments.  So if you
> > attached anything it may not go through.
> >
> >
> > Lizette
> >
> >
> > > -Original Message-
> > > From: IBM Mainframe Discussion List
> > > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter
> > > Sent: Saturday, February 10, 2018 6:33 AM
> > > To: IBM-MAIN@LISTSERV.UA.EDU
> > > Subject: Apply error WAS product
> > >
> > > Hi
> > >
> > > While applying an FMID for the WAS V10 I received the below error
> > >
> > >  Error Message: BPXF140E RETURN CODE 0081, REASON CODE 0594003D.
> > > A
> > LINK
> > > FAILED FOR LINK NAME /usr/lpp/InstallationManagerRepository
> > /HBBO850/IBM/..
> > > /WLP/fixpac. Pls find the attached log .
> > >
> > > I see a similar issue reported to IBM but for a different product
> > >
> > > http://www-01.ibm.com/support/docview.wss?uid=swg21195928
> > >
> > > Has anyone faced this similar issue ?
> > >
> > > Peter
> > >
> >
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions, send
> > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> >
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Question for COBOL users

2018-02-10 Thread Larry K. Slaten 

Mr. Tom Ross,

Yes, we use the OPTFILE compiler option in the PARM= parameter 
exclusively.  Via JCL SET statements we establish the PDS and member 
name to use for the DD SYSOPTF file.  This allows us to point to 
different members for different COBOL compile types (i.e. batch, CICS, 
test compiles, production compiles, CA-Intertest, different ISP vendors, 
etc.). Plus you still have the PROCESS statement inside each source if 
it deviates from the norm.  It all seems to work quite well.  And, it is 
a lot easier to manage via PDS and member than on the PARM= parameter.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Apply error WAS product

2018-02-10 Thread Peter 
This is a monoplex... The program directory of the product didn't mention
about this mount points ... It sounded like a product bug...



On 10-Feb-2018 8:17 PM, "Lizette Koehler"  wrote:

> Some Questions
>
> Is the LPAR this is running on, where the mount files reside?
>
> For example, you only have one LPAR this can run on?  Or is this a SYSPLEX
> and it can run on more than one system?
>
> If this is a sysplex, make sure the file mounted where the job runs.  To
> do this, logon that that system and in ISPF using 3.17 (my favorite) enter
> the mount point.  If it shows up, then enter FS next to any file/dir in
> that file. Ensure names and locations for the run are correct.
>
> Or you can go to SDSF and issue  D OMVS,F,N=   and the N= would be the
> actual MVS data set name.  Look for where the file is mounted
>
> Or you could go into report from the SMP APPLY and review the DDDEF
> section.  Make sure the mount point used by SMPE is the right mount point
>
>
> Note:  This list typically will not allow attachments.  So if you attached
> anything it may not go through.
>
>
> Lizette
>
>
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> > Behalf Of Peter
> > Sent: Saturday, February 10, 2018 6:33 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Apply error WAS product
> >
> > Hi
> >
> > While applying an FMID for the WAS V10 I received the below error
> >
> >  Error Message: BPXF140E RETURN CODE 0081, REASON CODE 0594003D. A
> LINK
> > FAILED FOR LINK NAME /usr/lpp/InstallationManagerRepository
> /HBBO850/IBM/..
> > /WLP/fixpac. Pls find the attached log .
> >
> > I see a similar issue reported to IBM but for a different product
> >
> > http://www-01.ibm.com/support/docview.wss?uid=swg21195928
> >
> > Has anyone faced this similar issue ?
> >
> > Peter
> >
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Apply error WAS product

2018-02-10 Thread Lizette Koehler 
Some Questions

Is the LPAR this is running on, where the mount files reside?

For example, you only have one LPAR this can run on?  Or is this a SYSPLEX and 
it can run on more than one system?

If this is a sysplex, make sure the file mounted where the job runs.  To do 
this, logon that that system and in ISPF using 3.17 (my favorite) enter the 
mount point.  If it shows up, then enter FS next to any file/dir in that file. 
Ensure names and locations for the run are correct.

Or you can go to SDSF and issue  D OMVS,F,N=   and the N= would be the actual 
MVS data set name.  Look for where the file is mounted

Or you could go into report from the SMP APPLY and review the DDDEF section.  
Make sure the mount point used by SMPE is the right mount point


Note:  This list typically will not allow attachments.  So if you attached 
anything it may not go through.


Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Peter
> Sent: Saturday, February 10, 2018 6:33 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Apply error WAS product
> 
> Hi
> 
> While applying an FMID for the WAS V10 I received the below error
> 
>  Error Message: BPXF140E RETURN CODE 0081, REASON CODE 0594003D. A LINK
> FAILED FOR LINK NAME /usr/lpp/InstallationManagerRepository /HBBO850/IBM/..
> /WLP/fixpac. Pls find the attached log .
> 
> I see a similar issue reported to IBM but for a different product
> 
> http://www-01.ibm.com/support/docview.wss?uid=swg21195928
> 
> Has anyone faced this similar issue ?
> 
> Peter
> 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Apply error WAS product

2018-02-10 Thread Peter 
Hi

While applying an FMID for the WAS V10 I received the below error

 Error Message: BPXF140E RETURN CODE 0081, REASON CODE 0594003D. A LINK
FAILED FOR LINK NAME /usr/lpp/InstallationManagerRepository /HBBO850/IBM/..
/WLP/fixpac. Pls find the attached log .

I see a similar issue reported to IBM but for a different product

http://www-01.ibm.com/support/docview.wss?uid=swg21195928

Has anyone faced this similar issue ?

Peter

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Question about ABEND Macro and IARV64

2018-02-10 Thread Peter Relson 
>Will the Segment created by IARV64 be visable in a dump 
>when the program issues  ABEND ,DUMP,STEP 

A true z/OS answer: it depends.

For SYSABEND/SYSUDUMP: no.
For SYSMDUMP, I think, yes.

There is no support for 64-bit storage in the "formatted dump" variants.

Peter Relson
z/OS Core Technology Design


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN