date:20120410

Hi Kirk.
  Thanks, You have helped lots, But I must have added it wrong. Here is the way 
I specified using your entry in Configure.

*OS/390*,*xlc*:-O -DB_ENDIAN -DCHARSET_EBCDIC -DNO_SYS_PARAM_H * 
-WC,XPLINK* LANGLVL(LONGLONG) -D_ALL_SOURCE::*::-WL,XPLINK*:THIRTY_TWO_BIT 
DES_PTR DES_UNROLL MD2_CHAR RC4_INDEX RC4_CHAR BF_PTR:::,

Then when I do the config.

IsMK1MF=0
CC=*xlc*
CFLAG =-DOPENSSL_THREADS * -O -DB_ENDIAN -DCHARSET_EBCDIC -DNO_SYS_PARAM
_H *
-WC,XPLINK* LANGLVL(LONGLONG) -D_ALL_SOURCE 
EX_LIBS   =-WL,XPLINK*  
make: Makefile: line 64:  Error -- Expecting macro or rule defn, found neither 

Not sure how/what I did incorrectly?   

Thanks

Ms. Terri E. Shaffer 
terri.e.shaf...@jpmchase.com
Engineer
J.P.Morgan Chase  Co.
GTI DCT ECS Core Services zSoftware Group / Emerging Technologies 
Office: # 614-213-3467
Cell: # 412-519-2592 


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
Kirk Wolf
Sent: Monday, April 09, 2012 4:26 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: openssl make - z/OS UNIX question - Help

langlvl(longlong) would go on the OS/390 Configure line as a compiler (-Wc ) 
option.

If you change Configure, you need to rerun ./config



On Mon, Apr 9, 2012 at 2:27 PM, Shaffer, Terri E  
terri.e.shaf...@jpmchase.com wrote:

 Hi Kirk,
  I think I made it further now, but get an error about when I to the 
 actual gmake

 ERROR CCN3115 ../../include/openssl/sha.h:184   Duplicate type specifier
 long
 ignored.
 ERROR CCN3115 ../../include/openssl/sha.h:185   Duplicate type specifier
 long
 ignored.
 ERROR CCN3115 ../../include/openssl/sha.h:187   Duplicate type specifier
 long
 ignored.
 CCN0793(I) Compilation failed for file ./sha_dgst.c.  Object file not 
 created.
 FSUM3065 The COMPILE step ended with return code 12.
 EZZ0158I SELECTEX FAILED: errno=1038176216 errno2=3d623b50

 And think I need to pass the langlvl but can't figure out where it 
 goes after many attempts.

 Could you please tell me where I set that parm?

 Thanks

 Ms. Terri E. Shaffer
 terri.e.shaf...@jpmchase.com
 Engineer
 J.P.Morgan Chase  Co.
 GTI DCT ECS Core Services zSoftware Group / Emerging Technologies
 Office: # 614-213-3467
 Cell: # 412-519-2592


 -Original Message-
 From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On 
 Behalf Of Kirk Wolf
 Sent: Friday, April 06, 2012 4:04 PM
 To: IBM-MAIN@bama.ua.edu
 Subject: Re: openssl make - z/OS UNIX question - Help

 Sounds to me like config/Configure worked (and generated make files).

 Refer to my original response:

 -- configure and make
 ./config --prefix=/usr/local --openssldir=/usr/local/openssl export
 _C89_CCMODE=1 export MAKE=gmake $MAKE

 so, do the exports and then execute gmake ($MAKE)

 Kirk Wolf
 Dovetailed Technologies
 http://dovetail.com

 On Fri, Apr 6, 2012 at 1:05 PM, Shaffer, Terri E  
 terri.e.shaf...@jpmchase.com wrote:

  Thanks Kirk,
   Originally I opened this thread to the MVS-OE but got no response 
  which is why I enter to IBM-MAIN.
 
  Here are my results.  It looks much better after your suggested 
  changes, I think...
 
  I see
  RC4_CHUNK is undefined  Not sure if this is an issue or not and
  what it actually means to me.
 
  So after 10 or so screens worth of: for all the directories.
 
  gmakeÝ1¨: Entering directory `/u/w012108/temp/openssl-1.0.1/ssl'
  ssl.h = ../include/openssl/ssl.h
  ssl2.h = ../include/openssl/ssl2.h
  ssl3.h = ../include/openssl/ssl3.h
  ssl23.h = ../include/openssl/ssl23.h tls1.h = 
  ../include/openssl/tls1.h dtls1.h = ../include/openssl/dtls1.h 
  kssl.h = ../include/openssl/kssl.h srtp.h = 
  ../include/openssl/srtp.h ssltest.c = ../test/ssltest.c
  gmakeÝ1¨: Leaving directory `/u/w012108/temp/openssl-1.0.1/ssl'
 
  I finally get
  Configured for os/compiler.
 
  Now heres where my knowledge drops off even more.. If that possible 
  when it comes to this.
 
  What do I do now, How to I get a new openssl module built?
 
  Thanks
 
  Ms. Terri E. Shaffer
  terri.e.shaf...@jpmchase.com
  Engineer
  J.P.Morgan Chase  Co.
  GTI DCT ECS Core Services zSoftware Group / Emerging Technologies
  Office: # 614-213-3467
  Cell: # 412-519-2592
 
 
  -Original Message-
  From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On 
  Behalf Of Kirk Wolf
  Sent: Thursday, April 05, 2012 2:33 PM
  To: IBM-MAIN@bama.ua.edu
  Subject: Re: openssl make - z/OS UNIX question - Help
 
  Terri -
 
  try this running config in test mode.  This is what I get for 
  OpenSSL
  0.9.8q:
 
  ./config -t
  Operating system: 2094-whatever-OS/390 Configuring for OS/390 
  /usr/lpp/perl/bin/perl ./Configure OS/390
 
  So far so good.  I assume you will get something similar, except

Re: LE C calling HLASM

Jan MOEYERSONS quoted the doc, then asked:
Is this not true then?

I know this has been a protracted thread, so I'll summarize:
If I use LIST, I can't use LINKAGE(SYSTEM), so it doesn't set the high bit. If 
I use OMITTED, it passes a zero for that parameter, so I can't tell whether the 
parameter was omitted or really passed as zero.

Our API is flexible: if you don't specify an output buffer  length, it uses 
the input buffer  length. But that doesn't want to work in PL/I.

Ideas?
--
...phsiii

Phil Smith III
p...@voltage.commailto:p...@voltage.com
Voltage Security, Inc.
www.voltage.comhttp://www.voltage.com
(703) 476-4511 (home office)
(703) 568-6662 (cell)


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

Re: LE C calling HLASM


On 4/10/2012 5:58 AM, Phil Smith wrote:

Jan MOEYERSONS quoted the doc, then asked:

Is this not true then?


I know this has been a protracted thread, so I'll summarize: If I use LIST, I
can't use LINKAGE(SYSTEM), so it doesn't set the high bit. If

I use OMITTED, it passes a zero for that parameter, so I can't tell whether the
parameter was omitted or really passed as zero.


Our API is flexible: if you don't specify an output buffer length, it uses

the input buffer length. But that doesn't want to work in PL/I.




Ah, so that's what you want it for. But if the output buffer
length is zero, doesn't that tell you to use the input buffer?

And if an argument is omitted, it will appear as zero, right?
I mean, why else would you pass a buffer length of zero?


Ideas?
--
...phsiii

Phil Smith III
p...@voltage.commailto:p...@voltage.com
Voltage Security, Inc.
www.voltage.comhttp://www.voltage.com
(703) 476-4511 (home office)
(703) 568-6662 (cell)




--

Kind regards,

-Steve Comstock
The Trainer's Friend, Inc.

303-355-2752
http://www.trainersfriend.com

* To get a good Return on your Investment, first make an investment!
  + Training your people is an excellent investment

* Try our tool for calculating your Return On Investment
for training dollars at
  http://www.trainersfriend.com/ROI/roi.html

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

HSM z/OS 1.13

We had a problem on Monday morning which was a bit of a surprised. Over 
the weekend we installed z/OS 1.13 on all of our remaining systems. 

Thought i'd pass along as a 'heads up'. We didn't see much about this in 
any of the migration manuals or from SHARE we attended. We had on our 
sysplex systems HSM lock up during the CDS backup. We found out there is 
new functionality in 1.13. By rolling HSM we seem to get out of it without 
a problem but does scare you after rolling out z/OS to your systems. We 
didn't have this of course when the test systems were at 1.13 and the 
production systems were at 1.12. We noticed when the whole sysplex was at 
1.13. We will make adjustments to GRS this weekend but . would of been 
nice to know more about it ahead of time. 

Here is a snip from our ETR with IBM

The SYSZARC/CATTABLE is new to HSM in 1.13. In 1.13, functionality 
was added into HSM that was designed to reduce the chance of hangs 
occurring within HSM when CDS Backup kicks off. CDS Backup is the only 
HSM function that requires an EXCLUSIVE ENQ on ARCGPA/ARCCAT to process.
In order for CDS Backup to process, any task currently holding a SHARED 
ENQ needs to complete before CDS Backup can obtain the EXCLUSIVE ENQ. 
Prior to 1.13, these tasks holding any SHARED ENQs would only DEQ the 
ARCGPA/ARCCAT resource when HSM was finished processing the 
dataset/volume it was on. In 1.13, functionality was added 
to have these tasks put on hold in the middle of a dataset/volume when 
a CDS Backup request comes in and then resumed when the CDS Backup ends.
The SYSZARC/CATTABLE resource is involved in this new functionality. 


Thanks
Andy S. White

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

Re: HSM z/OS 1.13

2012-04-10 Thread Darth Keller

Andy - 

What adjustments to you plan to make to GRS for this?  Can you provide any
additional information about the 'lock up'?  From the information you 
provided from
your ETR, it seems that HSM wouldn't totally lock up, but that some 
functions 
would appear to be delayed or possibly 'locked' until the CDS Backup 
completes.  Am
I missing something?

thanks - ddk



We had a problem on Monday morning which was a bit of a surprised. 
Over 
the weekend we installed z/OS 1.13 on all of our remaining systems. 

Thought I'd pass along as a 'heads up'. We didn't see much about this in 
any of the migration manuals or from SHARE we attended. We had on our 
sysplex systems HSM lock up during the CDS backup. We found out there is 
new functionality in 1.13. By rolling HSM we seem to get out of it without 

a problem but does scare you after rolling out z/OS to your systems. We 
didn't have this of course when the test systems were at 1.13 and the 
production systems were at 1.12. We noticed when the whole sysplex was at 
1.13. We will make adjustments to GRS this weekend but . would of been 

nice to know more about it ahead of time. 

The SYSZARC/CATTABLE is new to HSM in 1.13. In 1.13, functionality 
was added into HSM that was designed to reduce the chance of hangs 
occurring within HSM when CDS Backup kicks off. CDS Backup is the only 
HSM function that requires an EXCLUSIVE ENQ on ARCGPA/ARCCAT to process.
In order for CDS Backup to process, any task currently holding a SHARED 
ENQ needs to complete before CDS Backup can obtain the EXCLUSIVE ENQ. 
Prior to 1.13, these tasks holding any SHARED ENQs would only DEQ the 
ARCGPA/ARCCAT resource when HSM was finished processing the 
dataset/volume it was on. In 1.13, functionality was added 
to have these tasks put on hold in the middle of a dataset/volume when 
a CDS Backup request comes in and then resumed when the CDS Backup ends.
The SYSZARC/CATTABLE resource is involved in this new functionality.











This e-mail message and all attachments transmitted with it may
contain legally privileged and/or confidential information intended
solely for the use of the addressee(s). If the reader of this
message is not the intended recipient, you are hereby notified that
any reading, dissemination, distribution, copying, forwarding or
other use of this message or its attachments is strictly
prohibited. If you have received this message in error, please
notify the sender immediately and delete this message and all
copies and backups thereof. Thank you.

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

Re: Coding IEASYMxx

How I would do it:

are you sharing the same master catalog?
   if no, then simply recatalog the datasets in the new master using either 
VOL(SYSR1) or VOL(**)

   if YES, you are sharing the same master catalog, then
  Make the two systems either use a different IEASYMnn member in PARMLIB. 
There are at least 3 methods:
  1) Create a system unique PARMLIB, specified in the LOADnn member,
  2) if you don't have a system unique PARMLIB, then select a different 
LOADnn member on 
  on the HMC IPL screen or,
  3) use the same LOADnn parm, but select a different set of parameters 
(especially a
  different IEASYMnn value) based on the LPARNAME. This only works if you 
have separate LPARs
  for each system and are consistent in IPLing each system in its own, 
unique, LPAR.

  In any case, in the IEASYMnn member used by the source SYSRES, set
  SYSRS2='SYSRS1(1:5).2'
  in the IEASYMnn member used by the target SYSRES, set
  SYSRS2='SYSRS1'

This makes the datasets catalogued to SYSRS2 use the correct volser. Yes, 
SYSRS1 and SYSRS2 can have the same value. It may be confusing to some, so 
clearly document why SYSRS2 is what it is. I would do that as a comment in the 
IEASYMnn member.

-- 
John McKown 
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)

9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone * 
john.mck...@healthmarkets.com * www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or 
proprietary information. If you are not the intended recipient, please contact 
the sender by reply e-mail and destroy all copies of the original message. 
HealthMarkets(r) is the brand name for products underwritten and issued by the 
insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance 
Company(r), Mid-West National Life Insurance Company of TennesseeSM and The 
MEGA Life and Health Insurance Company.SM

 

 -Original Message-
 From: IBM Mainframe Discussion List 
 [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Jake anderson
 Sent: Monday, April 09, 2012 10:40 PM
 To: IBM-MAIN@bama.ua.edu
 Subject: Re: Coding IEASYMxx
 
 Hi,
 
 Apology for not being precise. Here I am trying to understand 
 about SYSRES
 cloning, so I have referred the Currently Running SYSRES as 
 source SYSRES
 and Target Volume specifies as the Volume Which Would be used during
 DFSMSdss SYSRES cloning.
 
 This volumes are not SMS managed.
 
 On Tue, Apr 10, 2012 at 9:05 AM, retired mainframer 
 retired-mainfra...@q.com wrote:
 
  We need to get the terminology straight first.  What do you 
 mean by source
  SYSRES and target SYSRES?  Is source the IPL volumes and 
 target the volume
  holding the SMPE target datasets?  Or are you using 
 ServerPac terminology?
 
  BTW, are any of these volumes SMS managed?
 
  :: -Original Message-
  :: From: IBM Mainframe Discussion List 
 [mailto:IBM-MAIN@bama.ua.edu] On
  :: Behalf Of Jake anderson
  :: Sent: Monday, April 09, 2012 8:20 PM
  :: To: IBM-MAIN@bama.ua.edu
  :: Subject: Re: Coding IEASYMxx
  ::
  :: Hi,
  ::
  :: Seasons Greeting !!
  ::
  :: One curious question is that if the Two source SYSRES 
 volumes are in
  :: seperate MOD-3 volumes, but the Target SYSRES Volume is 
 initialized
  :: using
  :: MOD-9. In this scenario how do make use of the SYMBOLIC 
 parameter when
  :: two
  :: Source SYSRES volumes(MOD-3) are copied to Single 
 SYSRES volume(mod-9).
 
  
 --
  For IBM-MAIN subscribe / signoff / archive access instructions,
  send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
 
 
 --
 For IBM-MAIN subscribe / signoff / archive access instructions,
 send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
 
 

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

Re: HSM z/OS 1.13

Sorry here is what IBM recommended for us to change
 
ACTION TAKEN: Reviewed the dumps and found that the ARCGPA/ARCCAT 
resource was being propagated as a SYSTEMS ENQ. that this 
resource needs to remain a SYSTEM ENQ. Recommended that to remove the 
ARCGPA entry from the GRS INCLUDE RNL (which will allow the resource to 
be obtained as a SYSTEM ENQ instead of a SYSTEMS). 


Thanks

Andy S. White


 Andy - 
 
 What adjustments to you plan to make to GRS for this?  Can you provide 
any
 additional information about the 'lock up'?  From the information you 
 provided from
 your ETR, it seems that HSM wouldn't totally lock up, but that some 
 functions 
 would appear to be delayed or possibly 'locked' until the CDS Backup 
 completes.  Am
 I missing something?
 
 thanks - ddk

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

Re: LE C calling HLASM

Steve Comstock wrote:
Ah, so that's what you want it for. But if the output buffer
length is zero, doesn't that tell you to use the input buffer?

And if an argument is omitted, it will appear as zero, right?
I mean, why else would you pass a buffer length of zero?

Because users make mistakes? I mean, we could do that, but it doesn't really 
solve the problem. We don't want to force them to type OMITTED - at that point 
they might as well code:
   rc = THEFUNCTION(inbuffer, inlength, inbuffer, inlength);

What we want is to allow both:
   rc = THEFUNCTION(inbuffer, inlength, outbuffer, outlength);
and
   rc = THEFUNCTION(inbuffer, inlength); /* Works same as if inbuffer/inlength 
specified again as 3rd  4th parameters */

as we can in COBOL. Or even in C, for that matter. I still find it hard to 
believe that PL/I can't do this!

Remember that LIST seemed like the answer, except that the high bit never got 
set on the last parameter. And then LINKAGE(SYSTEM) seemed like the answer, 
except that you can't specify that on a function call.

...phsiii (will it go 'round in circles...?)

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

Re: Questions regarding SMS compacted dataset

2012-04-10 Thread Blaicher, Christopher Y.

Having never used ADRDSSU, I can't say for sure, but it would be a pretty bad 
utility if when it was done it did not leave a good readable copy of the data 
set.  It should either do it right or tell you why it can't.  If you are 
copying a file from a SMS to a non-SMS volume, then it should write the 
expanded file on the destination volume or tell you that it can't do that copy 
or move function.  Doing a move and leaving the data unreadable would be ample 
justification for opening an APAR.

IEBGENER and most other products that I know of use the BSAM or QSAM access 
methods when dealing with a compressed file.  The SAM access methods return 
expanded records to the application, or in the case of writing, compress the 
data on the way out.

Chris Blaicher
Senior Software Engineer, Software Services
Syncsort Incorporated
50 Tice Boulevard, Woodcliff Lake, NJ 07677
P: 201-930-8260  |  M: 512-627-3803    
E: cblaic...@syncsort.com

www.syncsort.com

Check out our Knowledge Base at www.syncsort.com/support

Syncsort aims for the best product and service experience. 
We welcome your feedback.


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
Victor Zhang
Sent: Monday, April 09, 2012 11:46 PM
To: MVS List Server 1
Subject: Re: Questions regarding SMS compacted dataset

Hi all,
Sorry, forgot to mention is if the program trying to read compressed extended 
physical sequential file is ADRDSSU, will only compressed data be  returned? 
How about IEBGEN program?

Regards
Victor

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

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

Re: openssl make - z/OS UNIX question - Help

2012-04-10 Thread Kirk Wolf

The langlvl(longlong) is a compiler option, so it must be specified
following a -Wc, like:

-Wc,xplink,langlvl(longlong)

Also, you seem to have some asterisks in your Configure line that don't
make sense to me.

For my port of 0.9.8q, I had (on one line):

OS/390,xlc:-O -DB_ENDIAN -DCHARSET_EBCDIC -DNO_SYS_PARAM_H  -Wc,xplink
-D_ALL_SOURCE-Wl,xplink:THIRTY_TWO_BIT DES_PTR DES_UNROLL MD2_CHAR
RC4_INDEX RC4_CHAR BF_PTR:::,

If you need langlvl(longlong) for 1.0.1, then perhaps use:

OS/390,xlc:-O -DB_ENDIAN -DCHARSET_EBCDIC -DNO_SYS_PARAM_H
 -Wc,xplink,langlvl(longlong) -D_ALL_SOURCE-Wl,xplink:THIRTY_TWO_BIT
DES_PTR DES_UNROLL MD2_CHAR RC4_INDEX RC4_CHAR BF_PTR:::,


Kirk Wolf
Dovetailed Technologies
http://dovetail.com

On Tue, Apr 10, 2012 at 6:53 AM, Shaffer, Terri E 
terri.e.shaf...@jpmchase.com wrote:

 Hi Kirk.
  Thanks, You have helped lots, But I must have added it wrong. Here is the
 way I specified using your entry in Configure.

 *OS/390*,*xlc*:-O -DB_ENDIAN -DCHARSET_EBCDIC -DNO_SYS_PARAM_H *
 -WC,XPLINK* LANGLVL(LONGLONG) -D_ALL_SOURCE::*::-WL,XPLINK*:THIRTY_TWO_BIT
 DES_PTR DES_UNROLL MD2_CHAR RC4_INDEX RC4_CHAR BF_PTR:::,

 Then when I do the config.

 IsMK1MF=0
 CC=*xlc*
 CFLAG =-DOPENSSL_THREADS * -O -DB_ENDIAN -DCHARSET_EBCDIC
 -DNO_SYS_PARAM
 _H *
 -WC,XPLINK* LANGLVL(LONGLONG) -D_ALL_SOURCE
 EX_LIBS   =-WL,XPLINK*
 make: Makefile: line 64:  Error -- Expecting macro or rule defn, found
 neither

 Not sure how/what I did incorrectly?

 Thanks

 Ms. Terri E. Shaffer
 terri.e.shaf...@jpmchase.com
 Engineer
 J.P.Morgan Chase  Co.
 GTI DCT ECS Core Services zSoftware Group / Emerging Technologies
 Office: # 614-213-3467
 Cell: # 412-519-2592


 -Original Message-
 From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
 Behalf Of Kirk Wolf
 Sent: Monday, April 09, 2012 4:26 PM
 To: IBM-MAIN@bama.ua.edu
 Subject: Re: openssl make - z/OS UNIX question - Help

 langlvl(longlong) would go on the OS/390 Configure line as a compiler
 (-Wc ) option.

 If you change Configure, you need to rerun ./config



 On Mon, Apr 9, 2012 at 2:27 PM, Shaffer, Terri E 
 terri.e.shaf...@jpmchase.com wrote:

  Hi Kirk,
   I think I made it further now, but get an error about when I to the
  actual gmake
 
  ERROR CCN3115 ../../include/openssl/sha.h:184   Duplicate type specifier
  long
  ignored.
  ERROR CCN3115 ../../include/openssl/sha.h:185   Duplicate type specifier
  long
  ignored.
  ERROR CCN3115 ../../include/openssl/sha.h:187   Duplicate type specifier
  long
  ignored.
  CCN0793(I) Compilation failed for file ./sha_dgst.c.  Object file not
  created.
  FSUM3065 The COMPILE step ended with return code 12.
  EZZ0158I SELECTEX FAILED: errno=1038176216 errno2=3d623b50
 
  And think I need to pass the langlvl but can't figure out where it
  goes after many attempts.
 
  Could you please tell me where I set that parm?
 
  Thanks
 
  Ms. Terri E. Shaffer
  terri.e.shaf...@jpmchase.com
  Engineer
  J.P.Morgan Chase  Co.
  GTI DCT ECS Core Services zSoftware Group / Emerging Technologies
  Office: # 614-213-3467
  Cell: # 412-519-2592
 
 
  -Original Message-
  From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
  Behalf Of Kirk Wolf
  Sent: Friday, April 06, 2012 4:04 PM
  To: IBM-MAIN@bama.ua.edu
  Subject: Re: openssl make - z/OS UNIX question - Help
 
  Sounds to me like config/Configure worked (and generated make files).
 
  Refer to my original response:
 
  -- configure and make
  ./config --prefix=/usr/local --openssldir=/usr/local/openssl export
  _C89_CCMODE=1 export MAKE=gmake $MAKE
 
  so, do the exports and then execute gmake ($MAKE)
 
  Kirk Wolf
  Dovetailed Technologies
  http://dovetail.com
 
  On Fri, Apr 6, 2012 at 1:05 PM, Shaffer, Terri E 
  terri.e.shaf...@jpmchase.com wrote:
 
   Thanks Kirk,
Originally I opened this thread to the MVS-OE but got no response
   which is why I enter to IBM-MAIN.
  
   Here are my results.  It looks much better after your suggested
   changes, I think...
  
   I see
   RC4_CHUNK is undefined  Not sure if this is an issue or not and
   what it actually means to me.
  
   So after 10 or so screens worth of: for all the directories.
  
   gmakeÝ1¨: Entering directory `/u/w012108/temp/openssl-1.0.1/ssl'
   ssl.h = ../include/openssl/ssl.h
   ssl2.h = ../include/openssl/ssl2.h
   ssl3.h = ../include/openssl/ssl3.h
   ssl23.h = ../include/openssl/ssl23.h tls1.h =
   ../include/openssl/tls1.h dtls1.h = ../include/openssl/dtls1.h
   kssl.h = ../include/openssl/kssl.h srtp.h =
   ../include/openssl/srtp.h ssltest.c = ../test/ssltest.c
   gmakeÝ1¨: Leaving directory `/u/w012108/temp/openssl-1.0.1/ssl'
  
   I finally get
   Configured for os/compiler.
  
   Now heres where my knowledge drops off even more.. If that possible
   when it comes to this.
  
   What do I do now, How to I get a new openssl module built?
  
   Thanks
  
   Ms. Terri E. Shaffer

Re: LE C calling HLASM


On 4/10/2012 7:00 AM, Phil Smith wrote:

Steve Comstock wrote:

Ah, so that's what you want it for. But if the output buffer
length is zero, doesn't that tell you to use the input buffer?



And if an argument is omitted, it will appear as zero, right?
I mean, why else would you pass a buffer length of zero?


Because users make mistakes? I mean, we could do that, but it doesn't really

solve the problem. We don't want to force them to type OMITTED - at that point
they might as well code:

rc = THEFUNCTION(inbuffer, inlength, inbuffer, inlength);

What we want is to allow both:
rc = THEFUNCTION(inbuffer, inlength, outbuffer, outlength);
and
rc = THEFUNCTION(inbuffer, inlength); /* Works same as if inbuffer/inlength 
specified again as 3rd  4th parameters */

as we can in COBOL. Or even in C, for that matter. I still find it hard to 
believe that PL/I can't do this!

Remember that LIST seemed like the answer, except that the high bit never got 
set on the last parameter. And then LINKAGE(SYSTEM) seemed like the answer, 
except that you can't specify that on a function call.

...phsiii (will it go 'round in circles...?)


I'm confused here, because the title of the thread
is 'C calling HLASM' and here we are talking about
PL/I.

So what's really going on here that is the mystery?

My guess is: you have a C function that you want to
call from, in this instance, a PL/I program. Right?


Can you show us the definition of the C function
(not the body, just the definition of parameters
along with any pragma statements you might have,
and compiler options relevant to calls / function
references)?


Can you show us how you invoke the function from
C, COBOL, and Assembler? That is, some sample calls
or function references that work successfully, both
with two arguments and four arguments (BTW: do you
allow the output buffer to be specified without the
last length argument? How about no output buffer
but with a length? In other words, must the user
specify exactly two or exactly four arguments?)


Finally: there are some differences in the Enterprise
PL/I compiler regarding compile time options and
options available for declaring functions and
subroutines so I ask this: is your expectation that
your customers will be running the Enterprise PL/I
compiler or some earlier compiler?



--

Kind regards,

-Steve Comstock
The Trainer's Friend, Inc.

303-355-2752
http://www.trainersfriend.com

* To get a good Return on your Investment, first make an investment!
  + Training your people is an excellent investment

* Try our tool for calculating your Return On Investment
for training dollars at
  http://www.trainersfriend.com/ROI/roi.html

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

Re: openssl make - z/OS UNIX question - Help

Hi Kirk,
  Not sure about the extra asterisks, I copied your example at the beginning of 
this email and pasted into my Configure file.

I did make it into 1 long line then.

I don't know too much, or pretty much nothing about how these parms should 
look, so I am sortof at a loss and try a few things before I respond.  I took 
your new example and pasted into my Configure and again made it into 1 long 
line.

The Configure works and received Configured for *OS/390*.

When I tried to the gmake install I get
W012108:SDEV(DEV):/u/w012108/temp/openssl-1.0.1  gmake install 
making all in crypto... 
gmakeÝ1¨: Entering directory `/u/w012108/temp/openssl-1.0.1/crypto' 
xlc -I. -I.. -I../include  -DOPENSSL_THREADS  -O -DB_ENDIAN -DCHARSET_EBCDIC -DN
O_SYS_PARAM_H -Wc,xplink,langlvl(longlong) -D_ALL_SOURCE   -c -o cryptlib.o 
cryptlib.c  

syntax error: got (, expecting Newline  
gmakeÝ1¨: *** Ýcryptlib.o¨ Error 1  
gmakeÝ1¨: Leaving directory `/u/w012108/temp/openssl-1.0.1/crypto'  
gmake: *** Ýbuild_crypto¨ Error 1   

So it looks like there is something wrong with the specification but not sure 
what?

I tried looking at the OSXL C/C++User's Guide but there are really no examples 
on how this would be specified in the perl script.

I appreciate your help and sorry to be lost.

Thanks

Ms. Terri E. Shaffer 
terri.e.shaf...@jpmchase.com
Engineer
J.P.Morgan Chase  Co.
GTI DCT ECS Core Services zSoftware Group / Emerging Technologies 
Office: # 614-213-3467
Cell: # 412-519-2592 


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
Kirk Wolf
Sent: Tuesday, April 10, 2012 9:46 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: openssl make - z/OS UNIX question - Help

The langlvl(longlong) is a compiler option, so it must be specified following a 
-Wc, like:

-Wc,xplink,langlvl(longlong)

Also, you seem to have some asterisks in your Configure line that don't make 
sense to me.

For my port of 0.9.8q, I had (on one line):

OS/390,xlc:-O -DB_ENDIAN -DCHARSET_EBCDIC -DNO_SYS_PARAM_H  -Wc,xplink 
-D_ALL_SOURCE-Wl,xplink:THIRTY_TWO_BIT DES_PTR DES_UNROLL MD2_CHAR 
RC4_INDEX RC4_CHAR BF_PTR:::,

If you need langlvl(longlong) for 1.0.1, then perhaps use:

OS/390,xlc:-O -DB_ENDIAN -DCHARSET_EBCDIC -DNO_SYS_PARAM_H
 -Wc,xplink,langlvl(longlong) -D_ALL_SOURCE-Wl,xplink:THIRTY_TWO_BIT
DES_PTR DES_UNROLL MD2_CHAR RC4_INDEX RC4_CHAR BF_PTR:::,


Kirk Wolf
Dovetailed Technologies
http://dovetail.com

On Tue, Apr 10, 2012 at 6:53 AM, Shaffer, Terri E  
terri.e.shaf...@jpmchase.com wrote:

 Hi Kirk.
  Thanks, You have helped lots, But I must have added it wrong. Here is 
 the way I specified using your entry in Configure.

 *OS/390*,*xlc*:-O -DB_ENDIAN -DCHARSET_EBCDIC -DNO_SYS_PARAM_H *
 -WC,XPLINK* LANGLVL(LONGLONG) 
 -D_ALL_SOURCE::*::-WL,XPLINK*:THIRTY_TWO_BIT
 DES_PTR DES_UNROLL MD2_CHAR RC4_INDEX RC4_CHAR BF_PTR:::,

 Then when I do the config.

 IsMK1MF=0
 CC=*xlc*
 CFLAG =-DOPENSSL_THREADS * -O -DB_ENDIAN -DCHARSET_EBCDIC
 -DNO_SYS_PARAM
 _H *
 -WC,XPLINK* LANGLVL(LONGLONG) -D_ALL_SOURCE
 EX_LIBS   =-WL,XPLINK*
 make: Makefile: line 64:  Error -- Expecting macro or rule defn, found 
 neither

 Not sure how/what I did incorrectly?

 Thanks

 Ms. Terri E. Shaffer
 terri.e.shaf...@jpmchase.com
 Engineer
 J.P.Morgan Chase  Co.
 GTI DCT ECS Core Services zSoftware Group / Emerging Technologies
 Office: # 614-213-3467
 Cell: # 412-519-2592


 -Original Message-
 From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On 
 Behalf Of Kirk Wolf
 Sent: Monday, April 09, 2012 4:26 PM
 To: IBM-MAIN@bama.ua.edu
 Subject: Re: openssl make - z/OS UNIX question - Help

 langlvl(longlong) would go on the OS/390 Configure line as a 
 compiler (-Wc ) option.

 If you change Configure, you need to rerun ./config



 On Mon, Apr 9, 2012 at 2:27 PM, Shaffer, Terri E  
 terri.e.shaf...@jpmchase.com wrote:

  Hi Kirk,
   I think I made it further now, but get an error about when I to the 
  actual gmake
 
  ERROR CCN3115 ../../include/openssl/sha.h:184   Duplicate type specifier
  long
  ignored.
  ERROR CCN3115 ../../include/openssl/sha.h:185   Duplicate type specifier
  long
  ignored.
  ERROR CCN3115 ../../include/openssl/sha.h:187   Duplicate type specifier
  long
  ignored.
  CCN0793(I) Compilation failed for file ./sha_dgst.c.  Object file 
  not created.
  FSUM3065 The COMPILE step ended with return code 12.
  EZZ0158I SELECTEX FAILED: errno=1038176216 errno2=3d623b50
 
  And think I need to pass the langlvl but can't figure out where it 
  goes after many attempts.
 
  Could you please tell me where I set that parm?
 
  Thanks
 
  Ms. Terri E. Shaffer

Re: HSM z/OS 1.13

2012-04-10 Thread Skip Robinson

As an early adopter of 1.13 (ESP customer) and a SHARE user experience 
presenter, I was curious why we have never seen this problem. I just 
checked our shared-system RNLs and did not find ARCGPA anywhere. If we 
were ever instructed to include it in the distant past, we (thankfully) 
missed the boat. 

.
.
JO.Skip Robinson
SCE Infrastructure Technology Services
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
jo.skip.robin...@sce.com



From:   Andy White awh...@metlife.com
To: IBM-MAIN@bama.ua.edu
Date:   04/10/2012 05:48 AM
Subject:Re: HSM z/OS 1.13
Sent by:IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu



Sorry here is what IBM recommended for us to change
 
ACTION TAKEN: Reviewed the dumps and found that the ARCGPA/ARCCAT 
resource was being propagated as a SYSTEMS ENQ. that this 
resource needs to remain a SYSTEM ENQ. Recommended that to remove the 
ARCGPA entry from the GRS INCLUDE RNL (which will allow the resource to 
be obtained as a SYSTEM ENQ instead of a SYSTEMS). 


Thanks

Andy S. White


 Andy - 
 
 What adjustments to you plan to make to GRS for this?  Can you provide 
any
 additional information about the 'lock up'?  From the information you 
 provided from
 your ETR, it seems that HSM wouldn't totally lock up, but that some 
 functions 
 would appear to be delayed or possibly 'locked' until the CDS Backup 
 completes.  Am
 I missing something?
 
 thanks - ddk



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

Re: openssl make - z/OS UNIX question - Help

2012-04-10 Thread David Crayford

Make sure you are using the right codepage. Are you sure you are running 
the shell in 1047? looks like it may be 037 judging by the mangled 
square brackets


On 10/04/2012 10:46 PM, Shaffer, Terri E wrote:

Hi Kirk,
   Not sure about the extra asterisks, I copied your example at the beginning 
of this email and pasted into my Configure file.

I did make it into 1 long line then.

I don't know too much, or pretty much nothing about how these parms should 
look, so I am sortof at a loss and try a few things before I respond.  I took 
your new example and pasted into my Configure and again made it into 1 long 
line.

The Configure works and received Configured for *OS/390*.

When I tried to the gmake install I get
W012108:SDEV(DEV):/u/w012108/temp/openssl-1.0.1  gmake install
making all in crypto...
gmakeÝ1¨: Entering directory `/u/w012108/temp/openssl-1.0.1/crypto'
xlc -I. -I.. -I../include  -DOPENSSL_THREADS  -O -DB_ENDIAN -DCHARSET_EBCDIC -DN
O_SYS_PARAM_H -Wc,xplink,langlvl(longlong) -D_ALL_SOURCE   -c -o cryptlib.o 
cryptlib.c
syntax error: got (, expecting Newline
gmakeÝ1¨: *** Ýcryptlib.o¨ Error 1
gmakeÝ1¨: Leaving directory `/u/w012108/temp/openssl-1.0.1/crypto'
gmake: *** Ýbuild_crypto¨ Error 1

So it looks like there is something wrong with the specification but not sure 
what?

I tried looking at the OSXL C/C++User's Guide but there are really no examples 
on how this would be specified in the perl script.

I appreciate your help and sorry to be lost.

Thanks

Ms. Terri E. Shaffer
terri.e.shaf...@jpmchase.com
Engineer
J.P.Morgan Chase  Co.
GTI DCT ECS Core Services zSoftware Group / Emerging Technologies
Office: # 614-213-3467
Cell: # 412-519-2592


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
Kirk Wolf
Sent: Tuesday, April 10, 2012 9:46 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: openssl make - z/OS UNIX question - Help

The langlvl(longlong) is a compiler option, so it must be specified following a 
-Wc, like:

-Wc,xplink,langlvl(longlong)

Also, you seem to have some asterisks in your Configure line that don't make 
sense to me.

For my port of 0.9.8q, I had (on one line):

OS/390,xlc:-O -DB_ENDIAN -DCHARSET_EBCDIC -DNO_SYS_PARAM_H  -Wc,xplink 
-D_ALL_SOURCE-Wl,xplink:THIRTY_TWO_BIT DES_PTR DES_UNROLL MD2_CHAR RC4_INDEX RC4_CHAR 
BF_PTR:::,

If you need langlvl(longlong) for 1.0.1, then perhaps use:

OS/390,xlc:-O -DB_ENDIAN -DCHARSET_EBCDIC -DNO_SYS_PARAM_H
  -Wc,xplink,langlvl(longlong) -D_ALL_SOURCE-Wl,xplink:THIRTY_TWO_BIT
DES_PTR DES_UNROLL MD2_CHAR RC4_INDEX RC4_CHAR BF_PTR:::,


Kirk Wolf
Dovetailed Technologies
http://dovetail.com

On Tue, Apr 10, 2012 at 6:53 AM, Shaffer, Terri E  
terri.e.shaf...@jpmchase.com  wrote:


Hi Kirk.
  Thanks, You have helped lots, But I must have added it wrong. Here is
the way I specified using your entry in Configure.

*OS/390*,*xlc*:-O -DB_ENDIAN -DCHARSET_EBCDIC -DNO_SYS_PARAM_H *
-WC,XPLINK* LANGLVL(LONGLONG)
-D_ALL_SOURCE::*::-WL,XPLINK*:THIRTY_TWO_BIT
DES_PTR DES_UNROLL MD2_CHAR RC4_INDEX RC4_CHAR BF_PTR:::,

Then when I do the config.

IsMK1MF=0
CC=*xlc*
CFLAG =-DOPENSSL_THREADS * -O -DB_ENDIAN -DCHARSET_EBCDIC
-DNO_SYS_PARAM
_H *
-WC,XPLINK* LANGLVL(LONGLONG) -D_ALL_SOURCE
EX_LIBS   =-WL,XPLINK*
make: Makefile: line 64:  Error -- Expecting macro or rule defn, found
neither

Not sure how/what I did incorrectly?

Thanks

Ms. Terri E. Shaffer
terri.e.shaf...@jpmchase.com
Engineer
J.P.Morgan Chase  Co.
GTI DCT ECS Core Services zSoftware Group / Emerging Technologies
Office: # 614-213-3467
Cell: # 412-519-2592


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
Behalf Of Kirk Wolf
Sent: Monday, April 09, 2012 4:26 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: openssl make - z/OS UNIX question - Help

langlvl(longlong) would go on the OS/390 Configure line as a
compiler (-Wc ) option.

If you change Configure, you need to rerun ./config



On Mon, Apr 9, 2012 at 2:27 PM, Shaffer, Terri E
terri.e.shaf...@jpmchase.com  wrote:


Hi Kirk,
  I think I made it further now, but get an error about when I to the
actual gmake

ERROR CCN3115 ../../include/openssl/sha.h:184   Duplicate type specifier
long
ignored.
ERROR CCN3115 ../../include/openssl/sha.h:185   Duplicate type specifier
long
ignored.
ERROR CCN3115 ../../include/openssl/sha.h:187   Duplicate type specifier
long
ignored.
CCN0793(I) Compilation failed for file ./sha_dgst.c.  Object file
not created.
FSUM3065 The COMPILE step ended with return code 12.
EZZ0158I SELECTEX FAILED: errno=1038176216 errno2=3d623b50

And think I need to pass the langlvl but can't figure out where it
goes after many attempts.

Could you please tell me where I set that parm?

Thanks

Ms. Terri E. Shaffer
terri.e.shaf...@jpmchase.com
Engineer
J.P.Morgan Chase  Co.
GTI DCT ECS Core Services zSoftware Group / Emerging Technologies
Office: # 614-213-3467
Cell: # 412-519-2592


-Original

Re: IBM Global Copy/Global Mirror

We started with PPRC on Sharks, upgraded to XRC on DS8100's, then later added 
GDPS. This has been stable plus or minus for a year or two and seems to be 
working well. 

I imagine that you'll find that details of your implementation will be somewhat 
unique to your specific situation.  


 


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
Steve Dover
Sent: Monday, April 09, 2012 10:26 AM
To: IBM-MAIN@bama.ua.edu
Subject: IBM Global Copy/Global Mirror

We have recently started remote replication to DR site.  We are replicating 
mainframe and open systems data.  We have ironed out all of the issues we have 
except for our DS6800 Global Mirror.  I have had the benefit of speaking with 
2 different resources about the best practices way to do this and have 2 
different answers.  I am hoping there is someone here who is actually doing 
this I could talk to.  I need someone with practical experience and not a bunch 
of book reading.  Any assistance will be appreciated.
Thanks,
Steve

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@bama.ua.edu with the message: INFO IBM-MAIN
NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.

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

Re: HSM z/OS 1.13

2012-04-10 Thread Veilleux, Jon L

Andy, I have a couple of questions from our MIM support person:

Do you know if this customer enabled the AUTHQLVL=2 parm in GRSCNFxx that was a 
new feature with 1.13.  Which also only effects HSM ENQ's.  We run the default 
AUTHQLVL=1.

Also do you know if the customer run HSMs with CDSR or CDSQ.  We run CDSR=YES.  
These parms determine how HSM will issue its ENQ's.  We primarily use 
Reserve/Release.   

Thanks,
Jon

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
Andy White
Sent: Tuesday, April 10, 2012 8:48 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: HSM z/OS 1.13

Sorry here is what IBM recommended for us to change
 
ACTION TAKEN: Reviewed the dumps and found that the ARCGPA/ARCCAT resource was 
being propagated as a SYSTEMS ENQ. that this resource needs to remain a SYSTEM 
ENQ. Recommended that to remove the ARCGPA entry from the GRS INCLUDE RNL 
(which will allow the resource to be obtained as a SYSTEM ENQ instead of a 
SYSTEMS). 


Thanks

Andy S. White


 Andy -
 
 What adjustments to you plan to make to GRS for this?  Can you provide
any
 additional information about the 'lock up'?  From the information you 
 provided from your ETR, it seems that HSM wouldn't totally lock up, 
 but that some functions would appear to be delayed or possibly 
 'locked' until the CDS Backup completes.  Am I missing something?
 
 thanks - ddk

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@bama.ua.edu with the message: INFO IBM-MAIN
This e-mail may contain confidential or privileged information. If
you think you have received this e-mail in error, please advise the
sender by reply e-mail and then delete this e-mail immediately.
Thank you. Aetna   

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

Re: Questions regarding SMS compacted dataset

2012-04-10 Thread Victor Zhang

Chris,
Thanks for the reply.
Using dss is to back extended files to tape/virtual tape.

Your answer said the data read will be expanded. So even by setting compact as 
N, the amount of data written to tape/virtual tape will be same, right?

My another question is:
If I set compact=N for storage class, so data sets will not be 
compressed/compacted.

If I use same utility to copy it to tape/virtual tape, will there any 
difference for the data stream writing to tape?

I already noticed a difference:
By enabling compact option in storage class, I have very low compression ratio 
for data written to tape/virtual tape, do you have any idea?

Regards
Victor

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

Re: Questions regarding SMS compacted dataset

2012-04-10 Thread Mike Schwab

On Tue, Apr 10, 2012 at 10:00 AM, Victor Zhang
victor_wor...@yahoo.com.cn wrote:
deleted

 I already noticed a difference:
 By enabling compact option in storage class, I have very low compression 
 ratio for data written to tape/virtual tape, do you have any idea?

 Regards
 Victor

You are sending compressed data,  You can't compress it anymore.
-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

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

Re: Enterprise COBOL and XML attributes

- Original Message -
 From: Steve Comstock st...@trainersfriend.com
 To: IBM-MAIN@bama.ua.edu
 Cc: 
 Sent: Saturday, April 7, 2012 8:46 AM
 Subject: Re: Enterprise COBOL and XML attributes

 On 4/6/2012 5:29 PM, Frank Swarbrick wrote:
  Enterprise COBOL v4.2.

  First real
  world attempt at using XML GENERATE.  Works as designed, and relatively
  user friendly, but not particularly flexible for real world
  requirements.

  XML
    GENERATE will generate no fields as attributes unless with WITH
  ATTRIBUTES phrase is specified.  In that case it will generate
  attributes (rather than elements) ANYWHERE it can.

  I
    just want to make sure, before I go any further, that there is
  ABSOLUTELY NO WAY, using just XML GENERATE, that some fields that COULD
  be attributes can not be forced to be elements if the WITH ATTRIBUTES
  phrase is specified.  For example, I cannot generate the following using
    XML GENERATE alone (no post-processing to modify the generated XML
  document):

     underwritingrequest
       crossSellOfferId12000/crossSellOfferId
       channelTypeWEB-IA/channelType
       offerCategoryConsumer/offerCategory
       preApprovedProds
         product categoryCode=CC limit=5000/
         product categoryCode=CR limit=1000/
       /preApprovedProds
       parties
         party
           dob01/01/1950/dob
           scoreNo725298/scoreNo
           income10/income
           housingExpense1200/housingExpense
           housingStatusOwns/housingStatus
         /party
       /parties
     /underwritingrequest

  As you can see, all of the elementary data items are XML 
 elements EXCEPT for the categoryCode and limit fields 
 under product.

  Current COBOL group data item:
  01  underwritingrequest.
       05  crossSellOfferId      pic x(10).
       05  channelType           pic x(10).
       05  preApprovedProds.
           10  product.
               15  categoryCode  pic x(2).
               15  l1mit         pic 9(7).
       05  parties.
           10  party             occurs 1 to 10 times
                                 depending on party-count
                                 indexed by p_idx.
               15  dob           pic 99/99/.
               15  scoreNo       pic 9(9).
               15  income        pic 9(9).
               15  housingExpense pic 9(9).
               15  housingStatus pic x(10).

  Please note that I have seen the tech note XML GENERATE should create 
 attributes under COBOL;

  http://www-01.ibm.com/support/docview.wss?uid=swg21218516
  All I can say is (to quote Seth Meyers and Amy Poehler): 
 Really?!?!

  Since we own the process that consumes this XML document I hope I can 
 convince them to go either all attributes or all elements, but not this 
 little 
 mish-mash.  But I want to make sure I am not missing something SIMPLE that I 
 can 
 do to get what they really want.

  (I already have to change use field name '1imit' instead of 
 'limit' and then do INSPECT UWR-DOC REPLACING ALL l1mit BY 
 limit, because LIMIT is a COBOL reserved word.  Oy!)

  some short time later
  Ah hah, here's a trick. I don't love it, but I can perhaps live 
 with it. I
  canspecify OCCURS 1 for any field that I want to be an element rather
  than an attribute:

    01  underwritingrequest.
        05  crossSellOfferId      pic x(10) occurs 1.
        05  channelType           pic x(10) occurs 1.
        05  preApprovedProds.
            10  product.
                15  categoryCode  pic x(2).
                15  l1mit         pic 9(7).
        05  parties.
            10  party             occurs 1 to 10 times
                                  depending on party-count
                                  indexed by p_idx.
                15  dob           pic 99/99/ occurs 1.
                15  scoreNo       pic 9(9) occurs 1.
                15  income        pic 9(9) occurs 1.
                15  housingExpense pic 9(9) occurs 1.
                15  housingStatus pic x(10) occurs 1.

  Funky, but it works. Of course I now have to use a subscript qualification
  (oran extra one, in the case of the party children. Oh well!

  If there's a better way I'd still like to know, but at least I got 
 it to work.

  Thanks!

  Frank

 Frank,

 That is really cool! How did you come up with that? I'm going
 to add that technique to my course Enterprise COBOL: Unicode
 and XML Support.

Is it really that cool?  Rather a kludge.

Discovering it was a combination of figuring out what kind of fields could not 
be converted to attributes (fields with occurrences), and the fact that we 
have a vendor XML product that also uses the occurs 1 kludge, but for a 
different reason.

(for what I am wanting here it seemed simpler to use Enterprise COBOL XML 
support; plus I wanted to try it out.)

Frank

--
For IBM-MAIN subscribe / signoff / archive access instructions,

Re: USS YORKTOWN(was Accessing USS on Mainframe thru Telnet)

I read about such, um, issues a while back. Seems that there were more and more 
shipboard systems, but each was evolving on its own way lacking a common 
strategy. That means the systems were often fundamentally incompatible and 
therefore unable to communicate. Sounds silly, but I think an example was that 
neither the radars nor the sonar could send target information to the guns. 

Say what you will about Windows, but it at least offered some potential 
solution. While we laugh about Windows on warships giving a whole new meaning 
of the BSOD, I believe that it behooved the military to give it a try.   Of 
course, the military doesn't like to talk about how its weapons systems work 
and I guess we'll never know for sure what really happened. 

But I can envision the Navy wanting a integrated situation where the OIC could 
point to a target and click 'kill'. The ship would then use all of its 
resources optimally to attack and destroy while, at the same time, defending 
itself from everything from missiles to a lovesick whale. 
 



-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
Dave Day
Sent: Friday, April 06, 2012 2:20 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: USS YORKTOWN(was Accessing USS on Mainframe thru Telnet)

It's hard for me to imagine the navy allowing itself to get into a situation 
where the operation of the ship's main engines and steering would be completely 
subject to some PC, or number of PC's on a network within the ship.
I put just shy of 3yrs. in an engine room aboard a navy ship, back in the 
1960's.  The ship had redundancy built into practically every piece of 
equipment that was needed to maintain steerage, even down to manual pumps to 
pump hydraulic fluid thru the steering gear.  If you are dead in the water, you 
are a sitting duck.
They just don't build 'em like that.  They may have waited some period of time 
before going to manual systems to get underway, but I doubt seriously if a 
network crash would would have prevented complete movement.

 --Dave


On 4/6/2012 1:54 PM, Mike Schwab wrote:
 http://en.wikipedia.org/wiki/USS_Yorktown_(CG-48)
 On 21 September 1997, while on maneuvers off the coast of Cape 
 Charles, Virginia, a crew member entered a zero into a database field 
 causing a divide by zero error in the ship's Remote Data Base Manager 
 which brought down all the machines on the network, causing the ship's 
 propulsion system to fail.[5] [deleted[ Atlantic Fleet officials also 
 denied the towing, reporting that Yorktown was dead in the water for 
 just 2 hours and 45 minutes.[6] [deleted]

 On Fri, Apr 6, 2012 at 8:32 AM, McKown, John 
 john.mck...@healthmarkets.com  wrote:
 Probably, given how we do things anymore, it would likely run Windows. I 
 dread the day that we lose a war because our weapons blue screened.

 --
 John McKown
 Systems Engineer IV

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@bama.ua.edu with the message: INFO IBM-MAIN
NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.

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

Re: Doing a little research on Performance Modeling

Indeed, Dr. Merrill literally 'wrote the book' on every performance issue known 
to man (and a few known only to women) :-)

The manual that Lizette refers to evolved from that book. 

 


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
Lizette Koehler
Sent: Friday, April 06, 2012 9:51 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Doing a little research on Performance Modeling

If you have MXG, then look for the SOURCLIB dataset. This is where the MXG 
manual is located (chapter by chapter) and you should find the wonderful 
details Dr. Merrill put into the MXG code and how things work.

Lizette


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
Hylton Tom P
Sent: Friday, April 06, 2012 7:36 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Doing a little research on Performance Modeling

Much to our chagrin, MICS went away about a decade ago.   

Still have MXG and SAS, and a few others.We do a lot of reporting and lots 
of system level capacity/hardware planning, just trying to wrap my head around 
more broad based performance modeling approach on a large  project basis: 
critical path,   simulation, forecasting, what/if etc..


Anyone members of acm.org as well as cmg?

They had a few special interest groups that seemed worthwhile:

SIGMETRICS: http://www.sigmetrics.org/
SIGSIM: http://www.sigsim.org/
SIGMIS: http://www.sigmis.org/

I casually checked into them a few months ago to see about organization 
memberships and such akin to how Share and IDUG work, but all I could find was 
a yearly fee for their digital library and it seemed a  bit salty so I didn't 
look much further.   But looking, CMG is  individual based with yearly fees as 
well, so maybe I'll have to look again.

If you could choose only one for performance modeling , cmg or acm?

If you could choose only one for capacity/hardware planning? 

Thanks again, 
tom



-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
Lizette Koehler
Sent: Thursday, April 05, 2012 4:41 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Doing a little research on Performance Modeling

Tom
Do you have SAS and (MICS or MXG)?  if so, that is a good starting point.  CMG 
is also a good place to go look for info if you are a member.

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

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.

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

Re: Coding IEASYMxx

In
CAHTvvRU9B69uG3cQnsAX=gxzww-6_bcft8fckldnazy1p1j...@mail.gmail.com,
on 04/10/2012
   at 08:49 AM, Jake anderson justmainfra...@gmail.com said:

In this scenario how do make use of the SYMBOLIC parameter when 
two Source SYSRES volumes(MOD-3) are copied to Single SYSRES
volume(mod-9).

Set SYSR2 to SYSR1.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see http://patriot.net/~shmuel/resume/brief.html 
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: z/OS X-Windows (was: ASCII (was: Unix path name))

In 2738512312058187.wa.dap04bigpond.net...@bama.ua.edu, on
04/09/2012
   at 12:08 AM, David Price da...@bigpond.net.au said:

Does this imply that X-Windows under z/OS UNIX System Services is
usable

It implies that you can run an X-Window (no S) client.

Turning to the z/OS MVS side for a moment, I see that GDDM/MVS
supports X-Windows graphics through the GDDMXD/MVS interface. 

Do you mean that there is an X-Window server using GDDM, or that there
is an X-Window client to send GDDM graphics to an X-Server?
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see http://patriot.net/~shmuel/resume/brief.html 
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: Unix path name

In
CAArMM9SJmSrwnEMHqH-_j6wHMa7L-+oe4fVdN=yc-25mrxk...@mail.gmail.com,
on 04/08/2012
   at 08:49 PM, Tony Harminc t...@harminc.net said:

I'm just curious about these many UNIX-like, presumably non-POSIX,
systems. There's Linux (or GNU Linux, if you prefer), but what are
the others?

FreeBSD, NetBSD, OpenBSD and their derivatives are the obvious ones.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see http://patriot.net/~shmuel/resume/brief.html 
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: Coding IEASYMxx

In 1F12ED8366BB43D9986651EDCBE95978@barryf93b83d71, on 04/08/2012
   at 03:29 PM, retired mainframer retired-mainfra...@q.com said:

I have always put it in SYS1.PARMLIB but
that may be just force of habit.

Well, if you're following the IBM convention of

SYS1.PARMLIB
CPAC.PARMLIB
SYS1.IBM.PARMLIB

then SYS1.PARMLIB is the obvious choice.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see http://patriot.net/~shmuel/resume/brief.html 
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: ASCII (was: Unix path name)

In 9575668525598233.wa.paulgboulderaim@bama.ua.edu, on
04/08/2012
   at 03:58 PM, Paul Gilmartin paulgboul...@aim.com said:

Overall, yes, but, last time I checked, no Curses; no X11.

Those aren't ASCII issues.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see http://patriot.net/~shmuel/resume/brief.html 
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: HSM z/OS 1.13

Jon -   for the record we don't run MIM native GRS.

we run HSM (had to check with storage guy) with CDSQ=YES and CDRS=NO


We don't have AUTHQLVL coded so taking default. 


Andy S. White


IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu wrote on 04/10/2012 
10:57:29 AM:

 [image removed] 
 
 Re: [IBM-MAIN] HSM z/OS 1.13
 
 Veilleux, Jon L 
 
 to:
 
 IBM-MAIN
 
 04/10/2012 10:59 AM
 
 Sent by:
 
 IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu
 
 Please respond to IBM Mainframe Discussion List
 
 Andy, I have a couple of questions from our MIM support person:
 
 Do you know if this customer enabled the AUTHQLVL=2 parm in GRSCNFxx
 that was a new feature with 1.13.  Which also only effects HSM 
 ENQ's.  We run the default AUTHQLVL=1.
 
 Also do you know if the customer run HSMs with CDSR or CDSQ.  We run
 CDSR=YES.  These parms determine how HSM will issue its ENQ's.  We 
 primarily use Reserve/Release. 
 
 Thanks,
 Jon
 


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

Re: Questions regarding SMS compacted dataset

2012-04-10 Thread R.S.

In each case when you copy dataset from DASD to TAPE ar vice versa, the
data in transit are uncompressed. Compression/lack of compression on
source/target doesn't matter.

--
Radoslaw Skorupka
Lodz, Poland

W dniu 2012-04-10 17:00, Victor Zhang pisze:

Chris,
Thanks for the reply.
Using dss is to back extended files to tape/virtual tape.

Your answer said the data read will be expanded. So even by setting compact as
N, the amount of data written to tape/virtual tape will be same, right?

My another question is:
If I set compact=N for storage class, so data sets will not be
compressed/compacted.

If I use same utility to copy it to tape/virtual tape, will there any
difference for the data stream writing to tape?

I already noticed a difference:
By enabling compact option in storage class, I have very low compression ratio
for data written to tape/virtual tape, do you have any idea?

Regards
Victor

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

--
Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku
przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie
jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem
niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania
adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie
lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by
karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie
zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo
wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive.

BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax
+48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl
Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88.
Wedug stanu na dzie 01.01.2012 r. kapita zakadowy BRE Banku SA (w caoci wpacony) wynosi 168.410.984 zotych.

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

Re: OT: Keyboards for the archaic uber-geek

In 4f82ea50.2010...@trainersfriend.com, on 04/09/2012
   at 07:55 AM, Steve Comstock st...@trainersfriend.com said:

I have been trying for years to interest someone in the
Optimus keyboard, which is a keyboard where each key is
a small (48px * 48px) screen. You can dynamically assign icons 
and codepoints and build your own keyboard.

I'd be interested if it came with Linux and OS/2 software, inclding PM
and X, and had tables for the more common keyboard layouts.

http://www.artlebedev.com/everything/optimus/

I don't see the Converged (122 key) keybooard layout there.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see http://patriot.net/~shmuel/resume/brief.html 
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: Enterprise COBOL and XML attributes

We have a home grown XML generator tool, which
is controlled by something which we call interface description.
This interface description can be derived from XML schema definitions
and is translated by a special translator to PL/1 or C include files
(containing structure definitions containing constants), which are then
given as parameters to the XML generator.

This way it is possible to define per field, if is is generated as a
XML tag or as a attribute.

It is also possible to have counter fields as part of the structure,
which are not written to the XML document, but control the number
of sub-structures contained in the document. For example, the structure
that leads to the XML document has an array with 50 elements, but only
the first 7 are filled with values; then you set the counter variable to
7, and

from the interface definition the XML generator knows where it has to take
the value from that controls the number of sub-structures etc. - and it
only

writes 7 sub-tags to the XML dokument and ignores the remaining 43
array elements.

I strongly believe that without such a description that controls an XML
generator,

it will be pretty useless. An XML generator which produces the XML documents
simply by looking at the structure definition of some programming language
(without additional control information) doesn't lead you very far.

Kind regards

Bernd

Am 10.04.2012 17:25, schrieb Frank Swarbrick:

Is it really that cool? Rather a kludge.

Discovering it was a combination of figuring out what kind of fields could not be converted to
attributes (fields with occurrences), and the fact that we have a vendor XML product
that also uses the occurs 1 kludge, but for a different reason.

(for what I am wanting here it seemed simpler to use Enterprise COBOL XML
support; plus I wanted to try it out.)

Frank

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

Re: A deep question about VSAM SHR(4) - can you help?

Um, be careful about drawing any conclusions from a simple test other than the 
syntax is close. Data sharing is a very complex issue with gotcha's aplenty.  
You cannot possibly test every variation of access, update, and timings.  The 
VSAM folks have, IMHO, done a fine job of preventing you from screwing up too 
bad. But VSAM is still not a DBMS and doesn't claim to be. 

If the philosophy cannot change, then maybe neither can the solution.  Yes, it 
can be really that simple. 

Now, this is not to say that one couldn't forge right on and things would seem 
to work just fine, maybe for years. Or maybe not. 'Unpredictable results' 
include seemingly successful tests.  

Imagine corruption slowly creeping in and not discovered until the last good 
backup has rolled off and the tape reused. 

I believe what you want to do is doable. But you just gotta follow the rules. 
If you do, then CICS and VSAM can work together to avoid corruption and enhance 
performance. 

 

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
Mike Kovach
Sent: Thursday, April 05, 2012 3:23 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: A deep question about VSAM SHR(4) - can you help?

Thanks Robert. That is exactly what I was thinking. Will be running a test 
early next week.
 
Regards,
 
Mike Kovach
 
 



From: Robert A. Rosenberg hal9...@panix.com
To: IBM-MAIN@bama.ua.edu
Sent: Thursday, April 5, 2012 4:03 PM
Subject: Re: A deep question about VSAM SHR(4) - can you help?

At 07:16 -0700 on 04/05/2012, Mike Kovach wrote about A deep question about 
VSAM SHR(4) - can you help?:

 I have a VSAM KSDS CLUSTER which is written to by ONLY ONE PROGRAM in ONLY 
 ONE CICS REGION. Currently, this file is defined in CICS with STRNO(1).  The 
 file is defined with SHR(4,3) because while being written ONLY in CICS, it is 
 being read by a non-reentrent ASSEMBLER program running in BATCH.  SHR 4 
 forces VSAM to harden each I/O (yeah, I know!) so the BATCH gets the current 
 information. Please spare me all the comments about how poor this solution is 
 as it stands. It has been in place for decades and due to a myriad of 
 reasons, the philosophy CANNOT change.  My specific question is this:  I want 
 to introduce multi tasking so that 5 copies of the program can update the 
 file concurrently. If we change STRNO(1) to STRNO(5) on the CICS FCT 
 Definition, will VSAM be smart enough to manage the writes to the file so we 
 don't break it and the BATCH still gets the current information?

So long as you are still using one CICS Region, I do not think you will run 
into problems. The STRNO(5) will allow you to have 5 CIs being updated at a 
time (one CI per copy of the program). If more than one copy attempts to access 
records from the same CI, it should cause the subsequent requesters to wait for 
the owning copy to finish its update and release/write the CI (just make sure 
that all your VSAM is being done by SubTasks which I think CICS does 
automatically). You should increase the number of buffers so there are enough 
for all the copies.

  I am interested in any discussion you might share, but I am most 
interested in a specific reference to a reliable document.  Please 
help.    Thanks  Mike Kovach
 
 --
 For IBM-MAIN subscribe / signoff / archive access instructions, send 
 email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

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

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@bama.ua.edu with the message: INFO IBM-MAIN
NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.

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

Wish somebody had this for z/OS!

http://www.idevcloud.com/Menu.htm

This is a site where you can get a i/OS (iSeries aka AS/400) logon on a shared 
server with 10G of space for $50.00 a month. You can go all the way up to a 
dedicated server (running in the equivalent of an LPAR) with an unlimited 
number of users for only $200/month. I do know about the IBM z/OS in Dallas, 
but I don't know how much that costs. And I am fairly sure it is for 
development partners, not just somebody like me who would use it to do 
development for my own learning (and maybe to give to the CBT).

John McKown
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)

9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone *
john.mck...@healthmarkets.com * www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or 
proprietary information. If you are not the intended recipient, please contact 
the sender by reply e-mail and destroy all copies of the original message. 
HealthMarkets(r) is the brand name for products underwritten and issued by the 
insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance 
Company(r), Mid-West National Life Insurance Company of TennesseeSM and The 
MEGA Life and Health Insurance Company.SM


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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)

Steve Comstock wrote:
I'm confused here, because the title of the thread
is 'C calling HLASM' and here we are talking about
PL/I.

Yeah, true...topic drift. Renamed.

So what's really going on here that is the mystery?

My guess is: you have a C function that you want to
call from, in this instance, a PL/I program. Right?

Right.

Can you show us the definition of the C function
(not the body, just the definition of parameters
along with any pragma statements you might have,
and compiler options relevant to calls / function
references)?

See below.

Can you show us how you invoke the function from
C, COBOL, and Assembler? That is, some sample calls
or function references that work successfully, both
with two arguments and four arguments (BTW: do you
allow the output buffer to be specified without the
last length argument? How about no output buffer
but with a length? In other words, must the user
specify exactly two or exactly four arguments?)

The previous post had an example from COBOL; C is the same, only in C syntax. 
Assembler too. We validate that we got three or five arguments (note there's an 
initial, required argument).

Finally: there are some differences in the Enterprise
PL/I compiler regarding compile time options and
options available for declaring functions and
subroutines so I ask this: is your expectation that
your customers will be running the Enterprise PL/I
compiler or some earlier compiler?

Here's a C prototype, with the serial numbers filed off:

int THEFUNCTION( char *magic,
 char *inputBuffer,
 int  *inputLength,
 ...)

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

Re: USS YORKTOWN(was Accessing USS on Mainframe thru Telnet)

On Tue, 10 Apr 2012 15:27:29 +, Hal Merritt wrote:

I read about such, um, issues a while back. Seems that there were more and 
more shipboard systems, but each was evolving on its own way lacking a common 
strategy. That means the systems were often fundamentally incompatible and 
therefore unable to communicate. Sounds silly, but I think an example was that 
neither the radars nor the sonar could send target information to the guns.

Say what you will about Windows, but it at least offered some potential 
solution. ...
 
The solution is not Windows per se, but uniformity.  There are specialized OSes
used in, for example spacecraft, simpler and more robust which should be
more suitable for embedded software.  We seem to be back to the Bad Old Days
of No one ever lost his job for recommending IBM!  C 'IBM' 'Microsoft' ALL

-- gil

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

z/OS (was: ASCII (was: Unix path name))

On Tue, 10 Apr 2012 08:41:26 -0400, Shmuel Metz (Seymour J.) wrote:

In 9575668525598233.wa.paulgboulderaim@bama.ua.edu, on
04/08/2012
   at 03:58 PM, Paul Gilmartin paulgboul...@aim.com said:

Overall, yes, but, last time I checked, no Curses; no X11.

Those aren't ASCII issues.
 
Agreed.  They're z/OS C/C++ compiler/RTL issues.  Apologies
for not changing the Subject: soon enough.

-- gil

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

Re: USS YORKTOWN(was Accessing USS on Mainframe thru Telnet)

2012-04-10 Thread zMan

On Tue, Apr 10, 2012 at 11:27 AM, Hal Merritt hmerr...@jackhenry.comwrote:

 But I can envision the Navy wanting a integrated situation where the OIC
 could point to a target and click 'kill'. The ship would then use all of
 its resources optimally to attack and destroy while, at the same time,
 defending itself from everything from missiles to a lovesick whale.


OK, I gotta ask -- how DO you defend against a lovesick whale?
-- 
zMan -- I've got a mainframe and I'm not afraid to use it

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

Re: Wish somebody had this for z/OS!

On Tue, 10 Apr 2012 10:53:34 -0500, McKown, John wrote:

http://www.idevcloud.com/Menu.htm

This is a site where you can get a i/OS (iSeries aka AS/400) ...

Oh no!  Another TLA war!

-- gil

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

Re: HSM z/OS 1.13

2012-04-10 Thread Mark Jacobs

I just looked at our GRSRNL list and ARCGPA is in the EXCL list. Should 
I just take it out?


Mark Jacobs

On 04/10/12 10:54, Skip Robinson wrote:

As an early adopter of 1.13 (ESP customer) and a SHARE user experience
presenter, I was curious why we have never seen this problem. I just
checked our shared-system RNLs and did not find ARCGPA anywhere. If we
were ever instructed to include it in the distant past, we (thankfully)
missed the boat.

.
.
JO.Skip Robinson
SCE Infrastructure Technology Services
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
jo.skip.robin...@sce.com



From:   Andy Whiteawh...@metlife.com
To: IBM-MAIN@bama.ua.edu
Date:   04/10/2012 05:48 AM
Subject:Re: HSM z/OS 1.13
Sent by:IBM Mainframe Discussion ListIBM-MAIN@bama.ua.edu



Sorry here is what IBM recommended for us to change

ACTION TAKEN: Reviewed the dumps and found that the ARCGPA/ARCCAT
resource was being propagated as a SYSTEMS ENQ. that this
resource needs to remain a SYSTEM ENQ. Recommended that to remove the
ARCGPA entry from the GRS INCLUDE RNL (which will allow the resource to
be obtained as a SYSTEM ENQ instead of a SYSTEMS).


Thanks

Andy S. White


   

Andy -

What adjustments to you plan to make to GRS for this?  Can you provide
 

any
   

additional information about the 'lock up'?  From the information you
provided from
your ETR, it seems that HSM wouldn't totally lock up, but that some
functions
would appear to be delayed or possibly 'locked' until the CDS Backup
completes.  Am
I missing something?

thanks - ddk
 



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

   



--
Mark Jacobs
Time Customer Service
Tampa, FL


Learn from yesterday, live for today, hope for tomorrow.
The important thing is to not stop questioning.

- Albert Einstein

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

Re: HSM z/OS 1.13

2012-04-10 Thread Mark Zelden

On Tue, 10 Apr 2012 08:16:56 -0400, Andy White awh...@metlife.com wrote:

We had a problem on Monday morning which was a bit of a surprised. Over
the weekend we installed z/OS 1.13 on all of our remaining systems.

Thought i'd pass along as a 'heads up'. We didn't see much about this in
any of the migration manuals or from SHARE we attended. 

My client is only running 1.13 in sandbox LPARs so far, but I alerted the
storage team of this when I found it in the migration manual:

8.3.6 DFSMShsm: Stop using the HOLD command to quiesce activity prior to 
control data set backup
 
Description: Before z/OS V1R13, you might have manually or programmatically 
held DFSMShsm activity using the HOLD command prior to starting a control data 
set (CDS) backup. Starting with z/OS V1R13, the ARCCAT resource is released by 
all functions running on z/OS V1R13 DFSMShsm hosts, and the functions are 
quiesced when CDS backup starts. Manually or programmatically holding DFSMShsm 
activity is no longer necessary.
 
++
¦ Element or feature:¦ DFSMShsm. ¦
++---¦
¦ When change was introduced:¦ z/OS V1R13.   ¦
++---¦
¦ Applies to migration from: ¦ z/OS V1R12 and z/OS V1R11.¦
++---¦
¦ Timing:¦ After the first IPL of z/OS   ¦
¦¦ V1R13.¦
++---¦
¦ Is the migration action required?  ¦ No, but recommended because   ¦
¦¦ DFSMShsm will automatically   ¦
¦¦ release the ARCCAT resource when  ¦
¦¦ a CDS backup is starts.   ¦
++---¦
¦ Target system hardware ¦ Cross coupling facility (XCF) ¦
¦ requirements:  ¦ services are required to  ¦
¦¦ communicate the start of a CDS¦
¦¦ backup to all DFSMShsm hosts. XCF ¦
¦¦ services must be available and¦
¦¦ configured properly.  ¦
++---¦
¦ Target system software ¦ None. ¦
¦ requirements:  ¦   ¦
++---¦
¦ Other system (coexistence or   ¦ None. ¦
¦ fallback) requirements:¦   ¦
++---¦
¦ Restrictions:  ¦ The following are restrictions of ¦
¦¦ taking this migration action. ¦
¦¦   ¦
¦¦    In a record-level sharing ¦
¦¦ (RLS) CDS environment, all¦
¦¦ DFSMShsm hosts in the HSMPlex ¦
¦¦ must be z/OS V1R13 or later   ¦
¦¦ hosts.¦
¦¦   ¦
¦¦    In a non-RLS CDS environment, ¦
¦¦ this migration action can be  ¦
¦¦ taken on z/OS V1R13 DFSMShsm  ¦
¦¦ hosts without changing hosts  ¦
¦¦ running on prior releases of  ¦
¦¦ z/OS. ¦
¦¦   ¦
¦¦    Some DFSMShsm environment ¦
¦¦ configuration do not require  ¦
¦¦ XCF services.  Specifically,  ¦
¦¦ a non-RLS CDS non-multiple¦
¦¦ address space DFSMShsm (MASH) ¦
¦¦ configuration typically does  ¦
¦¦ not require XCF services. ¦
¦¦ However, XCF services are ¦
¦¦ required and must be  ¦
¦

Re: Coding IEASYMxx

I use that, but extend it by having the first PARMLIB be a system unique one 
name SYS1.SYSNAME..PARMLIB. But I must admit that I wouldn't do it that way if 
I did it again. I had to create our two system sysplex by cloning our single 
monoplex. And I knew nothing about how to set up a sysplex, did not get any 
training, and had to have it completed in about 3 weeks, maximum. Lots of bad 
decisions, which I cannot fix because it wouldn't be allowed because it works! 
Don't mess with it!

-- 
John McKown 
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)
 
9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone * 
john.mck...@healthmarkets.com * www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or 
proprietary information. If you are not the intended recipient, please contact 
the sender by reply e-mail and destroy all copies of the original message. 
HealthMarkets(r) is the brand name for products underwritten and issued by the 
insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance 
Company(r), Mid-West National Life Insurance Company of TennesseeSM and The 
MEGA Life and Health Insurance Company.SM

 

 -Original Message-
 From: IBM Mainframe Discussion List 
 [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Shmuel Metz (Seymour J.)
 Sent: Tuesday, April 10, 2012 7:44 AM
 To: IBM-MAIN@bama.ua.edu
 Subject: Re: Coding IEASYMxx
 
 In 1F12ED8366BB43D9986651EDCBE95978@barryf93b83d71, on 04/08/2012
at 03:29 PM, retired mainframer retired-mainfra...@q.com said:
 
 I have always put it in SYS1.PARMLIB but
 that may be just force of habit.
 
 Well, if you're following the IBM convention of
 
 SYS1.PARMLIB
 CPAC.PARMLIB
 SYS1.IBM.PARMLIB
 
 then SYS1.PARMLIB is the obvious choice.
  
 -- 
  Shmuel (Seymour J.) Metz, SysProg and JOAT
  ISO position; see http://patriot.net/~shmuel/resume/brief.html 
 We don't care. We don't have to care, we're Congress.
 (S877: The Shut up and Eat Your spam act of 2003)
 
 --
 For IBM-MAIN subscribe / signoff / archive access instructions,
 send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
 
 

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

Re: HSM z/OS 1.13

2012-04-10 Thread Veilleux, Jon L

Thanks much Andy!

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
Andy White
Sent: Tuesday, April 10, 2012 11:36 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: HSM z/OS 1.13

Jon -   for the record we don't run MIM native GRS.

we run HSM (had to check with storage guy) with CDSQ=YES and CDRS=NO

We don't have AUTHQLVL coded so taking default. 

Andy S. White

IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu wrote on 04/10/2012
10:57:29 AM:

 [image removed]

 Re: [IBM-MAIN] HSM z/OS 1.13

 Veilleux, Jon L

 to:

 IBM-MAIN

 04/10/2012 10:59 AM

 Sent by:

 IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu

 Please respond to IBM Mainframe Discussion List

 Andy, I have a couple of questions from our MIM support person:

 Do you know if this customer enabled the AUTHQLVL=2 parm in GRSCNFxx 
 that was a new feature with 1.13.  Which also only effects HSM ENQ's.  
 We run the default AUTHQLVL=1.

 Also do you know if the customer run HSMs with CDSR or CDSQ.  We run 
 CDSR=YES.  These parms determine how HSM will issue its ENQ's.  We 
 primarily use Reserve/Release.

 Thanks,
 Jon

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@bama.ua.edu with the message: INFO IBM-MAIN
This e-mail may contain confidential or privileged information. If
you think you have received this e-mail in error, please advise the
sender by reply e-mail and then delete this e-mail immediately.
Thank you. Aetna   

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

Re: Wish somebody had this for z/OS!

2012-04-10 Thread Scott Ford

Gil,

What's TLA ?

Sent from my iPad
Scott Ford
Senior Systems Engineer
www.identityforge.com



On Apr 10, 2012, at 12:10 PM, Paul Gilmartin paulgboul...@aim.com wrote:

 On Tue, 10 Apr 2012 10:53:34 -0500, McKown, John wrote:
 
 http://www.idevcloud.com/Menu.htm
 
 This is a site where you can get a i/OS (iSeries aka AS/400) ...
 
 Oh no!  Another TLA war!
 
 -- gil
 
 --
 For IBM-MAIN subscribe / signoff / archive access instructions,
 send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

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

Re: LE C calling HLASM

In 0363431161795505.wa.elardus.engelbrechtsita.co...@bama.ua.edu, on
04/10/2012
   at 05:39 AM, Elardus Engelbrecht elardus.engelbre...@sita.co.za
said:

http://publib.boulder.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ibm.zos.r12.ikjb300%2Fpack.htm

Yes. TSO/E also picked up up PCF.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see http://patriot.net/~shmuel/resume/brief.html 
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: HSM z/OS 1.13

Mark - for the record we don't hold our CDS backups this was why we didn't 
feel this pertained to us.
Andy S. White

 Description: Before z/OS V1R13, you might have manually or 
 programmatically held DFSMShsm activity using the HOLD command prior
 to starting a control data set (CDS) backup. Starting with z/OS 
 V1R13, the ARCCAT resource is released by all functions running on 
 z/OS V1R13 DFSMShsm hosts, and the functions are quiesced when CDS 
 backup starts. Manually or programmatically holding DFSMShsm 
 activity is no longer necessary.
 


 --
 Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS 

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

Enhanced HOLDDATA

2012-04-10 Thread Richards, Robert B.

Can someone provide me with the CICS equivalent to z/OS for SMPE/FTP syntax for 
retrieving enhanced HOLDDATA?

Bob
-
Robert B. Richards(Bob)
US Office of Personnel Management
1900 E Street NW Room: BH04L
Washington, D.C.  20415
Phone: (202) 606-1195
Email: robert.richa...@opm.govmailto:robert.richa...@opm.gov
-

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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)

I only happened to learn PL/I this weekend, so take this with a grain of salt, 
but can't you activate THEFUNCTION with a call rather than as a function in 
order to be able to use LINKAGE(SYSTEM)?  And then use PLIRETV() in order to 
get the return code?

declare THEFUNCTION entry options(ASM RETCODE LINKAGE(SYSTEM));
(I think LINKAGE(SYSTEM) is redundant here.)


call THEFUNCTION(one, two, three);
display(pliretv());
call THEFUNCTION(one, two, three, four, five);
display(pliretv());

(Not sure if the declare entry requires the parms to be declared.)


Maybe you can even wrap the above into a PL/I function so that your PL/I 
programs can invoke it as a function.

Just a WAG.  Good luck!

Frank



- Original Message -
 From: Phil Smith p...@voltage.com
 To: IBM-MAIN@bama.ua.edu
 Cc: 
 Sent: Tuesday, April 10, 2012 9:57 AM
 Subject: Re: PL/I with variable PLISTs (was: LE C calling HLASM)
 
 Steve Comstock wrote:
 I'm confused here, because the title of the thread
 is 'C calling HLASM' and here we are talking about
 PL/I.
 
 Yeah, true...topic drift. Renamed.
 
 So what's really going on here that is the mystery?
 
 My guess is: you have a C function that you want to
 call from, in this instance, a PL/I program. Right?
 
 Right.
 
 Can you show us the definition of the C function
 (not the body, just the definition of parameters
 along with any pragma statements you might have,
 and compiler options relevant to calls / function
 references)?
 
 See below.
 
 Can you show us how you invoke the function from
 C, COBOL, and Assembler? That is, some sample calls
 or function references that work successfully, both
 with two arguments and four arguments (BTW: do you
 allow the output buffer to be specified without the
 last length argument? How about no output buffer
 but with a length? In other words, must the user
 specify exactly two or exactly four arguments?)
 
 The previous post had an example from COBOL; C is the same, only in C syntax. 
 Assembler too. We validate that we got three or five arguments (note there's 
 an initial, required argument).
 
 Finally: there are some differences in the Enterprise
 PL/I compiler regarding compile time options and
 options available for declaring functions and
 subroutines so I ask this: is your expectation that
 your customers will be running the Enterprise PL/I
 compiler or some earlier compiler?
 
 Here's a C prototype, with the serial numbers filed off:
 
 int THEFUNCTION( char *magic,
              char *inputBuffer,
              int  *inputLength,
              ...)
 
 --
 For IBM-MAIN subscribe / signoff / archive access instructions,
 send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
 

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

Re: openssl make - z/OS UNIX question - Help

2012-04-10 Thread Kirk Wolf

David is right about your encoding.  Make sure that you have:  export
LANG=C   which is the default.
But the problem might be that you are running the z/OS Unix shell under TSO
OMVS.  If so, set the encoding of your TN3270 emulator to be IBM-1047.
 Even better would be to use ssh to login to a tty shell directly.

But I don't think that this is your only problem...
Since Configure builds a make file, then these command arguments are passed
through the shell.  It looks to me like the parenthesis in
langlvl(longlong) need to be somehow quoted or escaped.   This is tricky,
since the string is supplied as part of a Perl variable (in Configure).

So try adding a backslash like this:

...langlvl\(longlong\)

if that doesn't work, try double backslashes.

if that doesn't work, let me know and I'll try playing around with this
release myself.   I probably won't get to it today though.

Kirk Wolf
Dovetailed Technologies
http://dovetail.com


On Tue, Apr 10, 2012 at 9:55 AM, David Crayford dcrayf...@gmail.com wrote:

 Make sure you are using the right codepage. Are you sure you are running
 the shell in 1047? looks like it may be 037 judging by the mangled square
 brackets


 On 10/04/2012 10:46 PM, Shaffer, Terri E wrote:

 Hi Kirk,
   Not sure about the extra asterisks, I copied your example at the
 beginning of this email and pasted into my Configure file.

 I did make it into 1 long line then.

 I don't know too much, or pretty much nothing about how these parms
 should look, so I am sortof at a loss and try a few things before I
 respond.  I took your new example and pasted into my Configure and again
 made it into 1 long line.

 The Configure works and received Configured for *OS/390*.

 When I tried to the gmake install I get
 W012108:SDEV(DEV):/u/w012108/**temp/openssl-1.0.1  gmake install
 making all in crypto...
 gmakeÝ1¨: Entering directory `/u/w012108/temp/openssl-1.0.**1/crypto'
 xlc -I. -I.. -I../include  -DOPENSSL_THREADS  -O -DB_ENDIAN
 -DCHARSET_EBCDIC -DN
 O_SYS_PARAM_H -Wc,xplink,langlvl(longlong) -D_ALL_SOURCE   -c -o
 cryptlib.o cryptlib.c
 syntax error: got (, expecting Newline
 gmakeÝ1¨: *** Ýcryptlib.o¨ Error 1
 gmakeÝ1¨: Leaving directory `/u/w012108/temp/openssl-1.0.**1/crypto'
 gmake: *** Ýbuild_crypto¨ Error 1

 So it looks like there is something wrong with the specification but not
 sure what?

 I tried looking at the OSXL C/C++User's Guide but there are really no
 examples on how this would be specified in the perl script.

 I appreciate your help and sorry to be lost.

 Thanks

 Ms. Terri E. Shaffer
 terri.e.shaf...@jpmchase.com
 Engineer
 J.P.Morgan Chase  Co.



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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)

Frank Swarbrick suggested using a CALL instead of a function.

I'll try that; I'm not sure it's an acceptable change to the usage, but thanks.

I'm off after today for surgery for a herniated disc, so might be a while.

Still find it hard to believe that PL/I makes this so hard!

...phsiii

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

Re: Enhanced HOLDDATA

2012-04-10 Thread John Eells


Richards, Robert B. wrote:

Can someone provide me with the CICS equivalent to z/OS for SMPE/FTP syntax for 
retrieving enhanced HOLDDATA?

snip

I'm not sure I understand the question.  You get it for z/OS and CICS 
the same way.  The same HOLDDATA file, from the same source, covers the 
entire z/OS platform's worth of SMP/E-installed products, including CICS.


--
John Eells
z/OS Technical Marketing
IBM Poughkeepsie
ee...@us.ibm.com

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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)


On 4/10/2012 9:57 AM, Phil Smith wrote:

Steve Comstock wrote:

I'm confused here, because the title of the thread
is 'C calling HLASM' and here we are talking about
PL/I.


Yeah, true...topic drift. Renamed.


So what's really going on here that is the mystery?



My guess is: you have a C function that you want to
call from, in this instance, a PL/I program. Right?


Right.


Can you show us the definition of the C function
(not the body, just the definition of parameters
along with any pragma statements you might have,
and compiler options relevant to calls / function
references)?


See below.


Can you show us how you invoke the function from
C, COBOL, and Assembler? That is, some sample calls
or function references that work successfully, both
with two arguments and four arguments (BTW: do you
allow the output buffer to be specified without the
last length argument? How about no output buffer
but with a length? In other words, must the user
specify exactly two or exactly four arguments?)


The previous post had an example from COBOL; C is the same, only in C
syntax.Assembler too. We validate that we got three or five arguments
(note there's an initial, required argument).



Yeah, but I don't have the previous post. I'm trying
to get better about cleaning out my inbasket, and
sometimes I get overzealous.




Finally: there are some differences in the Enterprise
PL/I compiler regarding compile time options and
options available for declaring functions and
subroutines so I ask this: is your expectation that
your customers will be running the Enterprise PL/I
compiler or some earlier compiler?


And the answer is?





Here's a C prototype, with the serial numbers filed off:

int THEFUNCTION( char *magic,
  char *inputBuffer,
  int  *inputLength,
  ...)


Do you really have the ellipsis? If so, my reading
of the docs is that all arguments after int  *inputLength,
will have to be of that type (that is, all pointers to
integer values) and not pointer to char followed by pointer
to int; of course, you can play games. But I think that
would be a problem.

Generally, the above C function will expect, when it is
called, to have R1 set up this way:

(R1) - a(magic)
a(inputBuffer)
a(inputLength)
a(outputBuffer)
a(outputLength)


So how, in your C code, do you currently check how
many arguments have been received?

This won't be hard, really, :-) , but we need to pay
attention to detail.

What's weird to me is that PL/I and C share parts of
the same compiler logic! Ah well.


--

Kind regards,

-Steve Comstock
The Trainer's Friend, Inc.

303-355-2752
http://www.trainersfriend.com

* To get a good Return on your Investment, first make an investment!
  + Training your people is an excellent investment

* Try our tool for calculating your Return On Investment
for training dollars at
  http://www.trainersfriend.com/ROI/roi.html

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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)


On 4/10/2012 11:15 AM, Frank Swarbrick wrote:

I only happened to learn PL/I this weekend,


Well I'm impressed!


so take this with a grain of salt,

but can't you activate THEFUNCTION with a call rather than as a function in
order to be able to use LINKAGE(SYSTEM)? And then use PLIRETV() in order to get
the return code?

1. Yes you can, theoretically, set this up as a procedure

2. And, yes, the call to PLIRETV should work (although in
   the literature it says for this to work the called
   program should have made a call to PLIRETC, the effect
   from the C function will probably match that)

3. But the problem he is concerned with: how to pass
   three parameters or five parameters and have the
   C function know which have been passed

   If he is counting on the end-of-list flag, then
   the C function must have something like

 #pragma linkage(thefunction,OS)

   but it's not clear if that is the case here

   That's why I wanted to see how he checks for the
   number of parms in his C code.


Also, to turn on the end-of-list flag, the call from
the PL/I program will have to have options(asm), so:

  call thefunction(magic, inbuff, inbufflen, outbuff, outbufflen) options(asm);

or

  call thefunction(magic, inbuff, inbufflen) options(asm);


Also note that if the subroutine were declared as a function,
then options(asm) is not allowed.




declare THEFUNCTION entry options(ASM RETCODE LINKAGE(SYSTEM));
(I think LINKAGE(SYSTEM) is redundant here.)


call THEFUNCTION(one, two, three);
display(pliretv());
call THEFUNCTION(one, two, three, four, five);
display(pliretv());

(Not sure if the declare entry requires the parms to be declared.)


Maybe you can even wrap the above into a PL/I function so that your PL/I 
programs can invoke it as a function.

Just a WAG.  Good luck!

Frank



- Original Message -

From: Phil Smithp...@voltage.com
To: IBM-MAIN@bama.ua.edu
Cc:
Sent: Tuesday, April 10, 2012 9:57 AM
Subject: Re: PL/I with variable PLISTs (was: LE C calling HLASM)

Steve Comstock wrote:

I'm confused here, because the title of the thread
is 'C calling HLASM' and here we are talking about
PL/I.


Yeah, true...topic drift. Renamed.


So what's really going on here that is the mystery?



My guess is: you have a C function that you want to
call from, in this instance, a PL/I program. Right?


Right.


Can you show us the definition of the C function
(not the body, just the definition of parameters
along with any pragma statements you might have,
and compiler options relevant to calls / function
references)?


See below.


Can you show us how you invoke the function from
C, COBOL, and Assembler? That is, some sample calls
or function references that work successfully, both
with two arguments and four arguments (BTW: do you
allow the output buffer to be specified without the
last length argument? How about no output buffer
but with a length? In other words, must the user
specify exactly two or exactly four arguments?)


The previous post had an example from COBOL; C is the same, only in C syntax.
Assembler too. We validate that we got three or five arguments (note there's
an initial, required argument).


Finally: there are some differences in the Enterprise
PL/I compiler regarding compile time options and
options available for declaring functions and
subroutines so I ask this: is your expectation that
your customers will be running the Enterprise PL/I
compiler or some earlier compiler?


Here's a C prototype, with the serial numbers filed off:

int THEFUNCTION( char *magic,
  char *inputBuffer,
  int  *inputLength,
  ...)





--

Kind regards,

-Steve Comstock
The Trainer's Friend, Inc.

303-355-2752
http://www.trainersfriend.com

* To get a good Return on your Investment, first make an investment!
  + Training your people is an excellent investment

* Try our tool for calculating your Return On Investment
for training dollars at
  http://www.trainersfriend.com/ROI/roi.html

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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)

OK, Steve, here's the previous post...thanks again!

From: Phil Smith
Sent: Tuesday, April 10, 2012 9:00 AM
To: ibm-main@bama.ua.edu
Subject: RE: Re: LE C calling HLASM

Steve Comstock wrote:
Ah, so that's what you want it for. But if the output buffer
length is zero, doesn't that tell you to use the input buffer?

And if an argument is omitted, it will appear as zero, right?
I mean, why else would you pass a buffer length of zero?

Because users make mistakes? I mean, we could do that, but it doesn't really 
solve the problem. We don't want to force them to type OMITTED - at that point 
they might as well code:
   rc = THEFUNCTION(inbuffer, inlength, inbuffer, inlength);

What we want is to allow both:
   rc = THEFUNCTION(inbuffer, inlength, outbuffer, outlength);
and
   rc = THEFUNCTION(inbuffer, inlength); /* Works same as if inbuffer/inlength 
specified again as 3rd  4th parameters */

as we can in COBOL. Or even in C, for that matter. I still find it hard to 
believe that PL/I can't do this!

Remember that LIST seemed like the answer, except that the high bit never got 
set on the last parameter. And then LINKAGE(SYSTEM) seemed like the answer, 
except that you can't specify that on a function call.

...phsiii (will it go 'round in circles...?)

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

Re: Wish somebody had this for z/OS!

2012-04-10 Thread Sevetson, Phil

Three
Letter
Acronym

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
Scott Ford
Sent: Tuesday, April 10, 2012 12:49 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Wish somebody had this for z/OS!

Gil,

What's TLA ?

Sent from my iPad
Scott Ford
Senior Systems Engineer
www.identityforge.com



On Apr 10, 2012, at 12:10 PM, Paul Gilmartin paulgboul...@aim.com wrote:

 On Tue, 10 Apr 2012 10:53:34 -0500, McKown, John wrote:
 
 http://www.idevcloud.com/Menu.htm
 
 This is a site where you can get a i/OS (iSeries aka AS/400) ...
 
 Oh no!  Another TLA war!
 
 -- gil
 
 --
 For IBM-MAIN subscribe / signoff / archive access instructions,
 send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

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

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

Re: Wish somebody had this for z/OS!

And he's probably going with IBM's i/OS for the iSeries versus Apple's iOS on 
the iPad/iPhone. Hum, do you need an iPhone to dial up an iSeries? grin

-- 
John McKown 
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)

9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone * 
john.mck...@healthmarkets.com * www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or 
proprietary information. If you are not the intended recipient, please contact 
the sender by reply e-mail and destroy all copies of the original message. 
HealthMarkets(r) is the brand name for products underwritten and issued by the 
insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance 
Company(r), Mid-West National Life Insurance Company of TennesseeSM and The 
MEGA Life and Health Insurance Company.SM

 

 -Original Message-
 From: IBM Mainframe Discussion List 
 [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Sevetson, Phil
 Sent: Tuesday, April 10, 2012 1:34 PM
 To: IBM-MAIN@bama.ua.edu
 Subject: Re: Wish somebody had this for z/OS!
 
 Three
 Letter
 Acronym
 
 -Original Message-
 From: IBM Mainframe Discussion List 
 [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Scott Ford
 Sent: Tuesday, April 10, 2012 12:49 PM
 To: IBM-MAIN@bama.ua.edu
 Subject: Re: Wish somebody had this for z/OS!
 
 Gil,
 
 What's TLA ?
 
 Sent from my iPad
 Scott Ford
 Senior Systems Engineer
 www.identityforge.com
 
 
 
 On Apr 10, 2012, at 12:10 PM, Paul Gilmartin 
 paulgboul...@aim.com wrote:
 
  On Tue, 10 Apr 2012 10:53:34 -0500, McKown, John wrote:
  
  http://www.idevcloud.com/Menu.htm
  
  This is a site where you can get a i/OS (iSeries aka AS/400) ...
  
  Oh no!  Another TLA war!
  
  -- gil
  
  
 --
  For IBM-MAIN subscribe / signoff / archive access instructions,
  send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
 
 --
 For IBM-MAIN subscribe / signoff / archive access instructions,
 send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
 
 --
 For IBM-MAIN subscribe / signoff / archive access instructions,
 send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
 
 

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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)


On 4/10/2012 12:33 PM, Phil Smith wrote:

OK, Steve, here's the previous post...thanks again!


Umm... that doesn't show the COBOL call, nor the Assembler call
those are what I was wanting to see, to compare them to your
PL/I invocations



From: Phil Smith
Sent: Tuesday, April 10, 2012 9:00 AM
To: ibm-main@bama.ua.edu
Subject: RE: Re: LE C calling HLASM

Steve Comstock wrote:

Ah, so that's what you want it for. But if the output buffer
length is zero, doesn't that tell you to use the input buffer?



And if an argument is omitted, it will appear as zero, right?
I mean, why else would you pass a buffer length of zero?


Because users make mistakes? I mean, we could do that, but it doesn't really 
solve the problem. We don't want to force them to type OMITTED - at that point 
they might as well code:
rc = THEFUNCTION(inbuffer, inlength, inbuffer, inlength);

What we want is to allow both:
rc = THEFUNCTION(inbuffer, inlength, outbuffer, outlength);
and
rc = THEFUNCTION(inbuffer, inlength); /* Works same as if inbuffer/inlength 
specified again as 3rd  4th parameters */

as we can in COBOL. Or even in C, for that matter. I still find it hard to 
believe that PL/I can't do this!

Remember that LIST seemed like the answer, except that the high bit never got 
set on the last parameter. And then LINKAGE(SYSTEM) seemed like the answer, 
except that you can't specify that on a function call.

...phsiii (will it go 'round in circles...?)

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




--

Kind regards,

-Steve Comstock
The Trainer's Friend, Inc.

303-355-2752
http://www.trainersfriend.com

* To get a good Return on your Investment, first make an investment!
  + Training your people is an excellent investment

* Try our tool for calculating your Return On Investment
for training dollars at
  http://www.trainersfriend.com/ROI/roi.html

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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)

Steve Comstock wrote:
re whether we'll expect customers to be running Enterprise PL/I:
And the answer is?

Oops...meant to answer this. Um...I guess whatever's current was my 
assumption. Are the older compilers supported?

Re our C prototype:

Do you really have the ellipsis? If so, my reading
of the docs is that all arguments after int  *inputLength,
will have to be of that type (that is, all pointers to
integer values) and not pointer to char followed by pointer
to int; of course, you can play games. But I think that
would be a problem.

Generally, the above C function will expect, when it is
called, to have R1 set up this way:

(R1) - a(magic)
   a(inputBuffer)
   a(inputLength)
   a(outputBuffer)
   a(outputLength)

That isn't the behavior we've observed.

So how, in your C code, do you currently check how
many arguments have been received?

This won't be hard, really, :-) , but we need to pay
attention to detail.

High-bit.

What's weird to me is that PL/I and C share parts of
the same compiler logic! Ah well.

Indeed.

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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)

Steve Comstock wrote:
Umm... that doesn't show the COBOL call, nor the Assembler call
those are what I was wanting to see, to compare them to your
PL/I invocations

? COBOL is basically the same, don't have assembler handy but that's even 
easier:

call THEFUNCTION using inbuffer inlength inbuffer inlength returning rc


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

Re: openssl make - z/OS UNIX question - Help

Hi Kirk,
  I figured out the backslashes in the Configure file on my own with the help 
of google searches, so I was able to get past passing the compiler parm issue. 
After it completed:

I had to edit the makefile and change the cflag for langlvl and put back the 
backslashes.

CC= xlc 
CFLAG= -DOPENSSL_THREADS  -O -DB_ENDIAN -DCHARSET_EBCDIC -DNO_SYS_PARAM_H 
-D_ALL_SOURCE -W c,xplink,langlvl\(longlong\)
DEPFLAG= -DOPENSSL_NO_EC_NISTP_64_GCC_128 -DOPENSSL_NO_GMP -DOPENSSL_NO_JPAKE 
-D OPENSSL_NO_MD2 -DOPENSSL_NO_RC4 -DOPENSSL_NO_RC5 -DOPENSSL_NO_RFC3779 
-DOPENSSL_NO_SCTP -DOPENSSL_NO_STORE

I tried double backslashes also and that caused other issues when I got to the 
gmake install but the Configure liked them.

But the makefile was missing the backslashes, so I still had to edit.

Everything else I think looked okay.

I was then able to issue the gmake install command and my next round of 
problems started occurring.

The first thing I will say this runs about 20 minutes until it stops even with 
the first 4 issues for ignored.

xlc -I. -I.. -I../include  -DOPENSSL_THREADS  -O -DB_ENDIAN -DCHARSET_EBCDIC -DN
O_SYS_PARAM_H -D_ALL_SOURCE -W c,xplink,langlvl\(longlong\)   -c -o cversion.o 
cversion.c  
 
WARNING CCN3235 ./cversion.c:83Incorrect escape sequence \(. \ ignored. 
WARNING CCN3235 ./cversion.c:83Incorrect escape sequence \). \ ignored. 
WARNING CCN3235 ./cversion.c:85Incorrect escape sequence \(. \ ignored. 
WARNING CCN3235 ./cversion.c:85Incorrect escape sequence \). \ ignored. 

Goes thru many directories within the crypto directory until it hits this 
error. 

xlc -I.. -I../.. -I../modes -I../asn1 -I../evp -I../../include  -DOPENSSL_THREAD
S  -O -DB_ENDIAN -DCHARSET_EBCDIC -DNO_SYS_PARAM_H -D_ALL_SOURCE -W c,xplink,lan
glvl\(longlong\)   -c -o b_sock.o b_sock.c  
ERROR CCN3045 ./b_sock.c:888   Undeclared identifier NI_MAXHOST.
ERROR CCN3195 ./b_sock.c:888   Integral constant expression with a value greater
 than zero is required. 
ERROR CCN3045 ./b_sock.c:888   Undeclared identifier NI_MAXSERV.
ERROR CCN3195 ./b_sock.c:888   Integral constant expression with a value greater
 than zero is required. 
CCN0793(I) Compilation failed for file ./b_sock.c.  Object file not created.
gmakeÝ2¨: *** Ýb_sock.o¨ Error 12   
gmakeÝ2¨: Leaving directory `/u/w012108/temp/openssl-1.0.1/crypto/bio'  
gmakeÝ1¨: *** Ýsubdirs¨ Error 1 
gmakeÝ1¨: Leaving directory `/u/w012108/temp/openssl-1.0.1/crypto'  
gmake: *** Ýbuild_crypto¨ Error 1

I looked at the b.sock file and see char   hÝNI_MAXHOST¨,sÝNI_MAXSERV¨;  

I can also see .o members for many members that look like they worked.

I understand about the codepage and my displays but not sure that would cause 
the make issues?

At this stage I am not sure If I have a code issue with 1.0.1 version or 
something else I did wrong?

Any ideas you have or if you try it is great. Tomorrow or Thursday or whenever 
is fine for a response, I just appreciate everything you have provided so far.

My last option could be to download the previous version and try that to see if 
some of these new errors go away.  

Thanks

Ms. Terri E. Shaffer 
terri.e.shaf...@jpmchase.com
Engineer
J.P.Morgan Chase  Co.
GTI DCT ECS Core Services zSoftware Group / Emerging Technologies 
Office: # 614-213-3467
Cell: # 412-519-2592 


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
Kirk Wolf
Sent: Tuesday, April 10, 2012 1:19 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: openssl make - z/OS UNIX question - Help

David is right about your encoding.  Make sure that you have:  export
LANG=C   which is the default.
But the problem might be that you are running the z/OS Unix shell under TSO 
OMVS.  If so, set the encoding of your TN3270 emulator to be IBM-1047.
 Even better would be to use ssh to login to a tty shell directly.

But I don't think that this is your only problem...
Since Configure builds a make file, then these command arguments are passed 
through the shell.  It looks to me like the parenthesis in
langlvl(longlong) need to be somehow quoted or escaped.   This is tricky,
since the string is supplied as part of a Perl variable (in Configure).

So try adding a backslash like this:

...langlvl\(longlong\)

if that doesn't work, try double backslashes.

if that doesn't work, let me know and I'll try playing around with this
release myself.   I probably won't get to it today though.

Kirk Wolf
Dovetailed Technologies
http://dovetail.com


On Tue, Apr 10, 2012 at

Re: PL/I with variable PLISTs (was: LE C calling HLASM)


On 4/10/2012 12:44 PM, Phil Smith wrote:

Steve Comstock wrote:

re whether we'll expect customers to be running Enterprise PL/I:
And the answer is?


Oops...meant to answer this. Um...I guess whatever's current was my
assumption. Are the older compilers supported?


Some are. But there are, apparently, many customers running with
unsupported compilers. Some of the posts here have been pretty
incredibly about how old the software is.

But, we'll assume current Enterprise PL/I, then. Thanks.




Re our C prototype:


Do you really have the ellipsis? If so, my reading
of the docs is that all arguments after int  *inputLength,
will have to be of that type (that is, all pointers to
integer values) and not pointer to char followed by pointer
to int; of course, you can play games. But I think that
would be a problem.



Generally, the above C function will expect, when it is
called, to have R1 set up this way:



(R1) -  a(magic)
   a(inputBuffer)
   a(inputLength)
   a(outputBuffer)
   a(outputLength)


That isn't the behavior we've observed.


Ah, that's why I asked about any pragma's you may have
and what compiler options you are setting in C

Generally, what I've show is true; however, in some cases
the actual first element in the list is the address of
where the function value will be returned. The docs are
a little ambiguous, so I'm trying to nail down the details.





So how, in your C code, do you currently check how
many arguments have been received?



This won't be hard, really, :-) , but we need to pay
attention to detail.


High-bit.


But I would like to see the code you use to test the high bit, please.
Nothing proprietary, just informative




What's weird to me is that PL/I and C share parts of
the same compiler logic! Ah well.


Indeed.





--

Kind regards,

-Steve Comstock
The Trainer's Friend, Inc.

303-355-2752
http://www.trainersfriend.com

* To get a good Return on your Investment, first make an investment!
  + Training your people is an excellent investment

* Try our tool for calculating your Return On Investment
for training dollars at
  http://www.trainersfriend.com/ROI/roi.html

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

Re: Wish somebody had this for z/OS!

2012-04-10 Thread Scott Ford

Oh duh ...sorry brain cramp today...

Sent from my iPad
Scott Ford
Senior Systems Engineer
www.identityforge.com



On Apr 10, 2012, at 2:33 PM, Sevetson, Phil psevet...@fisa.nyc.gov wrote:

 Three
 Letter
 Acronym
 
 -Original Message-
 From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf 
 Of Scott Ford
 Sent: Tuesday, April 10, 2012 12:49 PM
 To: IBM-MAIN@bama.ua.edu
 Subject: Re: Wish somebody had this for z/OS!
 
 Gil,
 
 What's TLA ?
 
 Sent from my iPad
 Scott Ford
 Senior Systems Engineer
 www.identityforge.com
 
 
 
 On Apr 10, 2012, at 12:10 PM, Paul Gilmartin paulgboul...@aim.com wrote:
 
 On Tue, 10 Apr 2012 10:53:34 -0500, McKown, John wrote:
 
 http://www.idevcloud.com/Menu.htm
 
 This is a site where you can get a i/OS (iSeries aka AS/400) ...
 
 Oh no!  Another TLA war!
 
 -- gil
 
 --
 For IBM-MAIN subscribe / signoff / archive access instructions,
 send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
 
 --
 For IBM-MAIN subscribe / signoff / archive access instructions,
 send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
 
 --
 For IBM-MAIN subscribe / signoff / archive access instructions,
 send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

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

Re: openssl make - z/OS UNIX question - Help

I just looked at the cversion.c member and I guess this code doesn't like the 
backslashes escapes.

As these are lines 83 and 85 of the source.

#ifdef CFLAGS 
  static char bufÝsizeof(CFLAGS)+11¨; 
  
  BIO_snprintf(buf,sizeof buf,compiler: %s,CFLAGS); 
  return(buf);

Thanks

Ms. Terri E. Shaffer 
terri.e.shaf...@jpmchase.com
Engineer
J.P.Morgan Chase  Co.
GTI DCT ECS Core Services zSoftware Group / Emerging Technologies 
Office: # 614-213-3467
Cell: # 412-519-2592 


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
Shaffer, Terri E
Sent: Tuesday, April 10, 2012 2:52 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: openssl make - z/OS UNIX question - Help

Hi Kirk,
  I figured out the backslashes in the Configure file on my own with the help 
of google searches, so I was able to get past passing the compiler parm issue. 
After it completed:

I had to edit the makefile and change the cflag for langlvl and put back the 
backslashes.

CC= xlc 
CFLAG= -DOPENSSL_THREADS  -O -DB_ENDIAN -DCHARSET_EBCDIC -DNO_SYS_PARAM_H 
-D_ALL_SOURCE -W c,xplink,langlvl\(longlong\) DEPFLAG= 
-DOPENSSL_NO_EC_NISTP_64_GCC_128 -DOPENSSL_NO_GMP -DOPENSSL_NO_JPAKE -D 
OPENSSL_NO_MD2 -DOPENSSL_NO_RC4 -DOPENSSL_NO_RC5 -DOPENSSL_NO_RFC3779 
-DOPENSSL_NO_SCTP -DOPENSSL_NO_STORE

I tried double backslashes also and that caused other issues when I got to the 
gmake install but the Configure liked them.

But the makefile was missing the backslashes, so I still had to edit.

Everything else I think looked okay.

I was then able to issue the gmake install command and my next round of 
problems started occurring.

The first thing I will say this runs about 20 minutes until it stops even with 
the first 4 issues for ignored.

xlc -I. -I.. -I../include  -DOPENSSL_THREADS  -O -DB_ENDIAN -DCHARSET_EBCDIC -DN
O_SYS_PARAM_H -D_ALL_SOURCE -W c,xplink,langlvl\(longlong\)   -c -o cversion.o 
cversion.c  
 
WARNING CCN3235 ./cversion.c:83Incorrect escape sequence \(. \ ignored. 
WARNING CCN3235 ./cversion.c:83Incorrect escape sequence \). \ ignored. 
WARNING CCN3235 ./cversion.c:85Incorrect escape sequence \(. \ ignored. 
WARNING CCN3235 ./cversion.c:85Incorrect escape sequence \). \ ignored. 

Goes thru many directories within the crypto directory until it hits this 
error. 

xlc -I.. -I../.. -I../modes -I../asn1 -I../evp -I../../include  
-DOPENSSL_THREAD S  -O -DB_ENDIAN -DCHARSET_EBCDIC -DNO_SYS_PARAM_H 
-D_ALL_SOURCE -W c,xplink,lan
glvl\(longlong\)   -c -o b_sock.o b_sock.c  
ERROR CCN3045 ./b_sock.c:888   Undeclared identifier NI_MAXHOST.
ERROR CCN3195 ./b_sock.c:888   Integral constant expression with a value greater
 than zero is required. 
ERROR CCN3045 ./b_sock.c:888   Undeclared identifier NI_MAXSERV.
ERROR CCN3195 ./b_sock.c:888   Integral constant expression with a value greater
 than zero is required. 
CCN0793(I) Compilation failed for file ./b_sock.c.  Object file not created.
gmakeÝ2¨: *** Ýb_sock.o¨ Error 12   
gmakeÝ2¨: Leaving directory `/u/w012108/temp/openssl-1.0.1/crypto/bio'  
gmakeÝ1¨: *** Ýsubdirs¨ Error 1 
gmakeÝ1¨: Leaving directory `/u/w012108/temp/openssl-1.0.1/crypto'  
gmake: *** Ýbuild_crypto¨ Error 1

I looked at the b.sock file and see char   hÝNI_MAXHOST¨,sÝNI_MAXSERV¨;  

I can also see .o members for many members that look like they worked.

I understand about the codepage and my displays but not sure that would cause 
the make issues?

At this stage I am not sure If I have a code issue with 1.0.1 version or 
something else I did wrong?

Any ideas you have or if you try it is great. Tomorrow or Thursday or whenever 
is fine for a response, I just appreciate everything you have provided so far.

My last option could be to download the previous version and try that to see if 
some of these new errors go away.  

Thanks

Ms. Terri E. Shaffer
terri.e.shaf...@jpmchase.com
Engineer
J.P.Morgan Chase  Co.
GTI DCT ECS Core Services zSoftware Group / Emerging Technologies
Office: # 614-213-3467
Cell: # 412-519-2592 


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
Kirk Wolf
Sent: Tuesday, April 10, 2012 1:19 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: openssl make - z/OS UNIX question - Help

David is right about your encoding.  Make sure that you have:  export
LANG=C   which is the default.
But the

Re: USS YORKTOWN(was Accessing USS on Mainframe thru Telnet)

Sorry, but that's classified :-D

 


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
zMan
Sent: Tuesday, April 10, 2012 11:05 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: USS YORKTOWN(was Accessing USS on Mainframe thru Telnet)

On Tue, Apr 10, 2012 at 11:27 AM, Hal Merritt hmerr...@jackhenry.comwrote:

 But I can envision the Navy wanting a integrated situation where the 
 OIC could point to a target and click 'kill'. The ship would then use 
 all of its resources optimally to attack and destroy while, at the 
 same time, defending itself from everything from missiles to a lovesick whale.


OK, I gotta ask -- how DO you defend against a lovesick whale?
--
zMan -- I've got a mainframe and I'm not afraid to use it

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@bama.ua.edu with the message: INFO IBM-MAIN
NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.

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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)

Steve Comstock wrote:
But I would like to see the code you use to test the high bit, please.
Nothing proprietary, just informative

OK, something like this:
 L R2,0(,R8)
 TM0(R8),X'80'
 BOLASTPARM

? Pretty basic...

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

Re: openssl make - z/OS UNIX question - Help

Ah. how did you create the files? If they were in a tar file, then you needed 
to do:

pax -ofrom=iso8859-1,to=ibm-1047 file.tar

The main thing is that the files need to be in ibm-1047 (C language code page) 
to work properly. Or you need to tell the C compiler what code page they are in.

--
John McKown 
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets®

9151 Boulevard 26 . N. Richland Hills . TX 76010
(817) 255-3225 phone . 
john.mck...@healthmarkets.com . www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or 
proprietary information. If you are not the intended recipient, please contact 
the sender by reply e-mail and destroy all copies of the original message. 
HealthMarkets® is the brand name for products underwritten and issued by the 
insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance 
Company®, Mid-West National Life Insurance Company of TennesseeSM and The MEGA 
Life and Health Insurance Company.SM

 

 -Original Message-
 From: IBM Mainframe Discussion List 
 [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Shaffer, Terri E
 Sent: Tuesday, April 10, 2012 2:06 PM
 To: IBM-MAIN@bama.ua.edu
 Subject: Re: openssl make - z/OS UNIX question - Help
 
 I just looked at the cversion.c member and I guess this code 
 doesn't like the backslashes escapes.
 
 As these are lines 83 and 85 of the source.
 
 #ifdef CFLAGS 
   static char bufÝsizeof(CFLAGS)+11¨; 
   
   BIO_snprintf(buf,sizeof buf,compiler: %s,CFLAGS); 
   return(buf);
 
 Thanks
 
 Ms. Terri E. Shaffer 
 terri.e.shaf...@jpmchase.com
 Engineer
 J.P.Morgan Chase  Co.
 GTI DCT ECS Core Services zSoftware Group / Emerging Technologies 
 Office: # 614-213-3467
 Cell: # 412-519-2592 
 
 
 -Original Message-
 From: IBM Mainframe Discussion List 
 [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Shaffer, Terri E
 Sent: Tuesday, April 10, 2012 2:52 PM
 To: IBM-MAIN@bama.ua.edu
 Subject: Re: openssl make - z/OS UNIX question - Help
 
 Hi Kirk,
   I figured out the backslashes in the Configure file on my 
 own with the help of google searches, so I was able to get 
 past passing the compiler parm issue. After it completed:
 
 I had to edit the makefile and change the cflag for langlvl 
 and put back the backslashes.
 
 CC= xlc   
   
 CFLAG= -DOPENSSL_THREADS  -O -DB_ENDIAN -DCHARSET_EBCDIC 
 -DNO_SYS_PARAM_H -D_ALL_SOURCE -W 
 c,xplink,langlvl\(longlong\) DEPFLAG= 
 -DOPENSSL_NO_EC_NISTP_64_GCC_128 -DOPENSSL_NO_GMP 
 -DOPENSSL_NO_JPAKE -D OPENSSL_NO_MD2 -DOPENSSL_NO_RC4 
 -DOPENSSL_NO_RC5 -DOPENSSL_NO_RFC3779 -DOPENSSL_NO_SCTP 
 -DOPENSSL_NO_STORE
 
 I tried double backslashes also and that caused other issues 
 when I got to the gmake install but the Configure liked them.
 
 But the makefile was missing the backslashes, so I still had to edit.
 
 Everything else I think looked okay.
 
 I was then able to issue the gmake install command and my 
 next round of problems started occurring.
 
 The first thing I will say this runs about 20 minutes until 
 it stops even with the first 4 issues for ignored.
 
 xlc -I. -I.. -I../include  -DOPENSSL_THREADS  -O -DB_ENDIAN 
 -DCHARSET_EBCDIC -DN
 O_SYS_PARAM_H -D_ALL_SOURCE -W c,xplink,langlvl\(longlong\)   
 -c -o cversion.o cversion.c   
 
 WARNING CCN3235 ./cversion.c:83Incorrect escape sequence 
 \(. \ ignored. 
 WARNING CCN3235 ./cversion.c:83Incorrect escape sequence 
 \). \ ignored. 
 WARNING CCN3235 ./cversion.c:85Incorrect escape sequence 
 \(. \ ignored. 
 WARNING CCN3235 ./cversion.c:85Incorrect escape sequence 
 \). \ ignored. 
 
 Goes thru many directories within the crypto directory until 
 it hits this error. 
 
 xlc -I.. -I../.. -I../modes -I../asn1 -I../evp 
 -I../../include  -DOPENSSL_THREAD S  -O -DB_ENDIAN 
 -DCHARSET_EBCDIC -DNO_SYS_PARAM_H -D_ALL_SOURCE -W c,xplink,lan
 glvl\(longlong\)   -c -o b_sock.o b_sock.c
   
 ERROR CCN3045 ./b_sock.c:888   Undeclared identifier 
 NI_MAXHOST.
 ERROR CCN3195 ./b_sock.c:888   Integral constant expression 
 with a value greater
  than zero is required.   
   
 ERROR CCN3045 ./b_sock.c:888   Undeclared identifier 
 NI_MAXSERV.
 ERROR CCN3195 ./b_sock.c:888   Integral constant expression 
 with a value greater
  than zero is required.   
   
 CCN0793(I) Compilation failed for file ./b_sock.c.  Object 
 file not created.
 gmakeÝ2¨: *** Ýb_sock.o¨ Error 12 
   
 gmakeÝ2¨: Leaving directory 
 `/u/w012108/temp/openssl-1.0.1/crypto/bio'

Re: openssl make - z/OS UNIX question - Help

Sorry:

pax -ofrom=iso8859-1,to=ibm-1047 -rf file.tar

--
John McKown
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets®

9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone *
john.mck...@healthmarkets.com * www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or 
proprietary information. If you are not the intended recipient, please contact 
the sender by reply e-mail and destroy all copies of the original message. 
HealthMarkets® is the brand name for products underwritten and issued by the 
insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance 
Company®, Mid-West National Life Insurance Company of TennesseeSM and The MEGA 
Life and Health Insurance Company.SM



 -Original Message-
 From: IBM Mainframe Discussion List
 [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of McKown, John
 Sent: Tuesday, April 10, 2012 2:31 PM
 To: IBM-MAIN@bama.ua.edu
 Subject: Re: openssl make - z/OS UNIX question - Help

 Ah. how did you create the files? If they were in a tar file,
 then you needed to do:

 pax -ofrom=iso8859-1,to=ibm-1047 file.tar

 The main thing is that the files need to be in ibm-1047 (C
 language code page) to work properly. Or you need to tell the
 C compiler what code page they are in.

 --
 John McKown
 Systems Engineer IV
 IT

 Administrative Services Group

 HealthMarkets®

 9151 Boulevard 26 . N. Richland Hills . TX 76010
 (817) 255-3225 phone .
 john.mck...@healthmarkets.com . www.HealthMarkets.com

 Confidentiality Notice: This e-mail message may contain
 confidential or proprietary information. If you are not the
 intended recipient, please contact the sender by reply e-mail
 and destroy all copies of the original message.
 HealthMarkets® is the brand name for products underwritten
 and issued by the insurance subsidiaries of HealthMarkets,
 Inc. -The Chesapeake Life Insurance Company®, Mid-West
 National Life Insurance Company of TennesseeSM and The MEGA
 Life and Health Insurance Company.SM



  -Original Message-
  From: IBM Mainframe Discussion List
  [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Shaffer, Terri E
  Sent: Tuesday, April 10, 2012 2:06 PM
  To: IBM-MAIN@bama.ua.edu
  Subject: Re: openssl make - z/OS UNIX question - Help
 
  I just looked at the cversion.c member and I guess this code
  doesn't like the backslashes escapes.
 
  As these are lines 83 and 85 of the source.
 
  #ifdef CFLAGS
static char bufÝsizeof(CFLAGS)+11¨;
 
BIO_snprintf(buf,sizeof buf,compiler: %s,CFLAGS);
return(buf);
 
  Thanks
 
  Ms. Terri E. Shaffer
  terri.e.shaf...@jpmchase.com
  Engineer
  J.P.Morgan Chase  Co.
  GTI DCT ECS Core Services zSoftware Group / Emerging Technologies
  Office: # 614-213-3467
  Cell: # 412-519-2592
 
 
  -Original Message-
  From: IBM Mainframe Discussion List
  [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Shaffer, Terri E
  Sent: Tuesday, April 10, 2012 2:52 PM
  To: IBM-MAIN@bama.ua.edu
  Subject: Re: openssl make - z/OS UNIX question - Help
 
  Hi Kirk,
I figured out the backslashes in the Configure file on my
  own with the help of google searches, so I was able to get
  past passing the compiler parm issue. After it completed:
 
  I had to edit the makefile and change the cflag for langlvl
  and put back the backslashes.
 
  CC= xlc
 
  CFLAG= -DOPENSSL_THREADS  -O -DB_ENDIAN -DCHARSET_EBCDIC
  -DNO_SYS_PARAM_H -D_ALL_SOURCE -W
  c,xplink,langlvl\(longlong\) DEPFLAG=
  -DOPENSSL_NO_EC_NISTP_64_GCC_128 -DOPENSSL_NO_GMP
  -DOPENSSL_NO_JPAKE -D OPENSSL_NO_MD2 -DOPENSSL_NO_RC4
  -DOPENSSL_NO_RC5 -DOPENSSL_NO_RFC3779 -DOPENSSL_NO_SCTP
  -DOPENSSL_NO_STORE
 
  I tried double backslashes also and that caused other issues
  when I got to the gmake install but the Configure liked them.
 
  But the makefile was missing the backslashes, so I still
 had to edit.
 
  Everything else I think looked okay.
 
  I was then able to issue the gmake install command and my
  next round of problems started occurring.
 
  The first thing I will say this runs about 20 minutes until
  it stops even with the first 4 issues for ignored.
 
  xlc -I. -I.. -I../include  -DOPENSSL_THREADS  -O -DB_ENDIAN
  -DCHARSET_EBCDIC -DN
  O_SYS_PARAM_H -D_ALL_SOURCE -W c,xplink,langlvl\(longlong\)
  -c -o cversion.o cversion.c
 
  WARNING CCN3235 ./cversion.c:83Incorrect escape sequence
  \(. \ ignored.
  WARNING CCN3235 ./cversion.c:83Incorrect escape sequence
  \). \ ignored.
  WARNING CCN3235 ./cversion.c:85Incorrect escape sequence
  \(. \ ignored.
  WARNING CCN3235 ./cversion.c:85Incorrect escape sequence
  \). \ ignored.
 
  Goes thru many directories within the crypto directory until
  it hits this error.
 
  xlc -I.. -I../.. -I../modes -I../asn1 -I../evp
  -I../../include  -DOPENSSL_THREAD S  -O -DB_ENDIAN
  -DCHARSET_EBCDIC -DNO_SYS_PARAM_H -D_ALL_SOURCE -W c,xplink,lan
  glvl\(longlong\)   -c -o b_sock.o b_sock.c
 
  ERROR CCN3045 ./b_sock.c:888   Undeclared

Re: PL/I with variable PLISTs (was: LE C calling HLASM)


On 4/10/2012 1:27 PM, Phil Smith wrote:

Steve Comstock wrote:

But I would like to see the code you use to test the high bit, please.
Nothing proprietary, just informative


OK, something like this:
  L R2,0(,R8)
  TM0(R8),X'80'
  BOLASTPARM

? Pretty basic...



Yes. But that's Assembler. I thought the called routine
was C, and you were testing the parms passed in the C
routine. Is that not true? Are there more layers here?


--

Kind regards,

-Steve Comstock
The Trainer's Friend, Inc.

303-355-2752
http://www.trainersfriend.com

* To get a good Return on your Investment, first make an investment!
  + Training your people is an excellent investment

* Try our tool for calculating your Return On Investment
for training dollars at
  http://www.trainersfriend.com/ROI/roi.html

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

Re: openssl make - z/OS UNIX question - Help

2012-04-10 Thread Kirk Wolf

Terri,

I downloaded 1.0.1 and here's how I built it:

1) Update the Configure perl script and add this line (after the existing
OS390-Unix line, which isn't used):

OS/390,c99_x:-O -DB_ENDIAN -DCHARSET_EBCDIC -DNO_SYS_PARAM_H
 -D_ALL_SOURCE::(unknown):::THIRTY_TWO_BIT DES_PTR DES_UNROLL MD2_CHAR
RC4_INDEX RC4_CHAR BF_PTR:::,

Notice that all I changed was to change the label to OS/390 and to use
the c99_x command.
- c99 means to use STDC99, which automatically implies LONGLONG.  This
avoids the shell quoting issues.
- the c99_x means to compile and link using XPLINK linkage.  You may or may
not want this, depending on what you are using it for.   If you have a
non-XPLINK application and you want to use it with the openssl dll, then
you will want to use just c99

2) ensure that perl and gmake are in your PATH

3) chmod +x tools/*

4)
export MAKE=gmake
export _C89_CCMODE=1   (not sure that this is needed any more with the c99
command)

5) $MAKE

I get these errors:
ERROR CCN3045 ./b_sock.c:888   Undeclared identifier NI_MAXHOST.
ERROR CCN4324 ./b_sock.c:888   Array size must have integer type.
ERROR CCN3045 ./b_sock.c:888   Undeclared identifier NI_MAXSERV.
ERROR CCN4324 ./b_sock.c:888   Array size must have integer type.

So, I added these lines to crypto/bio/b_sock.c starting at line 102

#ifndef NI_MAXSERV
#define NI_MAXSERV 32
#endif
#ifndef NI_MAXHOST
#define NI_MAXHOST 1025
#endif

I get the following warnings, which I think may be OK.  The problem are
missing #includes (which are probably different on z/OS) -

WARNING CCN4421 ./a_print.c:90Implicit function declaration for
function isalnum
WARNING CCN4421 ./t_x509.c:498   Implicit function declaration for function
isupper.
WARNING CCN4421 ./ameth_lib.c:234   Implicit function declaration for
function strncasecmp.
WARNING CCN4421 ./f_int.c:136   Implicit function declaration for function
isxdigit.
WARNING CCN4421 ./f_string.c:136   Implicit function declaration for
function isxdigit.
WARNING CCN4421 ./v3_ncons.c:408   Implicit function declaration for
function strcasecmp.
WARNING CCN4421 ./v3_ncons.c:430   Implicit function declaration for
function strcasecmp.
WARNING CCN4421 ./v3_ncons.c:453   Implicit function declaration for
function strcasecmp.
WARNING CCN4421 ./v3_ncons.c:494   Implicit function declaration for
function strncasecmp.
WARNING CCN4421 ./v3_ncons.c:500   Implicit function declaration for
function strncasecmp.

but everything links OK, so these are probably OK.  (but the correct
include file may have an improved macro / inlined implementation, so this
should probably be fixed).


Kirk Wolf
Dovetailed Technologies
http://dovetail.com


On Tue, Apr 10, 2012 at 2:06 PM, Shaffer, Terri E 
terri.e.shaf...@jpmchase.com wrote:

 I just looked at the cversion.c member and I guess this code doesn't like
 the backslashes escapes.

 As these are lines 83 and 85 of the source.

 #ifdef CFLAGS
  static char bufÝsizeof(CFLAGS)+11¨;

  BIO_snprintf(buf,sizeof buf,compiler: %s,CFLAGS);
  return(buf);

 Thanks

 Ms. Terri E. Shaffer
 terri.e.shaf...@jpmchase.com
 Engineer
 J.P.Morgan Chase  Co.
 GTI DCT ECS Core Services zSoftware Group / Emerging Technologies
 Office: # 614-213-3467
 Cell: # 412-519-2592


 -Original Message-
 From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
 Behalf Of Shaffer, Terri E
 Sent: Tuesday, April 10, 2012 2:52 PM
 To: IBM-MAIN@bama.ua.edu
 Subject: Re: openssl make - z/OS UNIX question - Help

 Hi Kirk,
  I figured out the backslashes in the Configure file on my own with the
 help of google searches, so I was able to get past passing the compiler
 parm issue. After it completed:

 I had to edit the makefile and change the cflag for langlvl and put back
 the backslashes.

 CC= xlc
 CFLAG= -DOPENSSL_THREADS  -O -DB_ENDIAN -DCHARSET_EBCDIC -DNO_SYS_PARAM_H
 -D_ALL_SOURCE -W c,xplink,langlvl\(longlong\) DEPFLAG=
 -DOPENSSL_NO_EC_NISTP_64_GCC_128 -DOPENSSL_NO_GMP -DOPENSSL_NO_JPAKE -D
 OPENSSL_NO_MD2 -DOPENSSL_NO_RC4 -DOPENSSL_NO_RC5 -DOPENSSL_NO_RFC3779
 -DOPENSSL_NO_SCTP -DOPENSSL_NO_STORE

 I tried double backslashes also and that caused other issues when I got to
 the gmake install but the Configure liked them.

 But the makefile was missing the backslashes, so I still had to edit.

 Everything else I think looked okay.

 I was then able to issue the gmake install command and my next round of
 problems started occurring.

 The first thing I will say this runs about 20 minutes until it stops even
 with the first 4 issues for ignored.

 xlc -I. -I.. -I../include  -DOPENSSL_THREADS  -O -DB_ENDIAN
 -DCHARSET_EBCDIC -DN
 O_SYS_PARAM_H -D_ALL_SOURCE -W c,xplink,langlvl\(longlong\)   -c -o
 cversion.o cversion.c
 WARNING CCN3235 ./cversion.c:83Incorrect escape sequence \(. \ ignored.
 WARNING CCN3235 ./cversion.c:83Incorrect escape sequence \). \ ignored.
 WARNING CCN3235 ./cversion.c:85Incorrect escape sequence \(. \ ignored.
 WARNING CCN3235 ./cversion.c:85Incorrect escape

Re: PL/I with variable PLISTs (was: LE C calling HLASM)

Steve Comstock wrote:
 Yes. But that's Assembler. I thought the called routine
was C, and you were testing the parms passed in the C
routine. Is that not true? Are there more layers here?

Yes, there are lots of layers, it's a mixture of assembler and C, sorry. The 
point is, we're confident that the description of the behavior we've seen is as 
described (we have XDC, too, so can see some of it). it's very strange-as if 
nobody at IBM ever really tried to use variable plists with PL/I!

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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)


On 4/10/2012 1:54 PM, Phil Smith wrote:

Steve Comstock wrote:

Yes. But that's Assembler. I thought the called routine
was C, and you were testing the parms passed in the C
routine. Is that not true? Are there more layers here?


Yes, there are lots of layers, it's a mixture of assembler and C, sorry. The 
point is, we're confident that the description of the behavior we've seen is as 
described (we have XDC, too, so can see some of it). it's very strange-as if 
nobody at IBM ever really tried to use variable plists with PL/I!



Slipperier and slipperier. OK, let's try a different approach:

You tell me exactly what you want to see from the PL/I routine calling
your API and I'll see if I can cause PL/I to construct that.

In other words, your routine will see

(R1) - 



--

Kind regards,

-Steve Comstock
The Trainer's Friend, Inc.

303-355-2752
http://www.trainersfriend.com

* To get a good Return on your Investment, first make an investment!
  + Training your people is an excellent investment

* Try our tool for calculating your Return On Investment
for training dollars at
  http://www.trainersfriend.com/ROI/roi.html

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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)

Steve Comstock wrote:
Slipperier and slipperier. OK, let's try a different approach:

You tell me exactly what you want to see from the PL/I routine calling
your API and I'll see if I can cause PL/I to construct that.

In other words, your routine will see

(R1) - 

rc = THEFUNCTION(magic,inputbuffer,inputlength)

(R1) == A(magic),A(inputbuffer),A(inputlength) == high bit set on the third 
fullword

OR (the fully specified case):

rc = THEFUNCTION(magic,inputbuffer,inputlength,outputbuffer,outputlength)

(R1) == A(magic),A(inputbuffer),A(inputlength),A(outputbuffer),A(outputlength) 
== high bit set on the fifth fullword

Pretty standard, yes?

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

Strange SDSF behavior


Twice today the order of jobs in the SDSF status queue
has been changed on me without my issuing any commands.
That is, if you choose the View menu and Sort option,
the value is different from what I set!


I'm the only one on the system.

Has anyone else seen this behavior? (z/OS 1.13)


--

Kind regards,

-Steve Comstock
The Trainer's Friend, Inc.

303-355-2752
http://www.trainersfriend.com

* To get a good Return on your Investment, first make an investment!
  + Training your people is an excellent investment

* Try our tool for calculating your Return On Investment
for training dollars at
  http://www.trainersfriend.com/ROI/roi.html

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

Re: Strange SDSF behavior

2012-04-10 Thread Richard Pinion

That's what a programmer told me.  I didn't believe him.  Maybe there is 
something to it.  We are at z/OS 1.13 also.

Richard and Vickie Pinion

--- st...@trainersfriend.com wrote:

From: Steve Comstock st...@trainersfriend.com
To: IBM-MAIN@bama.ua.edu
Subject: Strange SDSF behavior
Date: Tue, 10 Apr 2012 15:18:30 -0600

Twice today the order of jobs in the SDSF status queue
has been changed on me without my issuing any commands.
That is, if you choose the View menu and Sort option,
the value is different from what I set!

I'm the only one on the system.

Has anyone else seen this behavior? (z/OS 1.13)

-- 

Kind regards,

-Steve Comstock
The Trainer's Friend, Inc.

303-355-2752
http://www.trainersfriend.com

* To get a good Return on your Investment, first make an investment!
   + Training your people is an excellent investment

* Try our tool for calculating your Return On Investment
 for training dollars at
   http://www.trainersfriend.com/ROI/roi.html

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

_
Netscape.  Just the Net You Need.

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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)

I don't know if it helps you, but using C I would code the two calls 
this way:


rc = THEFUNCTION (magic, inputbuffer,inputlength, NULL, NULL);


rc = THEFUNCTION (magic, inputbuffer,inputlength, outputbuffer,outputlength);


Note that the parameters that are probably integers are prefixed with an 
ampersand

to pass the addresses.

If it is needed that the 3rd and the 5th address has the high order bit 
set,
you can to this in C, too. I would use a macro called HIGHBITON (x), for 
example,

which is coded as follows:

#define HIGHBITON(x)  (void *)((unsigned int)(x) ! 0x8000)

So we have


rc = THEFUNCTION (magic, inputbuffer, HIGHBITON(inputlength), NULL, NULL);


rc = THEFUNCTION (magic, inputbuffer,inputlength, outputbuffer, 
HIGHBITON(outputlength));


The two additional NULL parameters after the 3rd address in the first 
case do no harm.


Kind regards

Bernd



Am 10.04.2012 23:11, schrieb Phil Smith:

Steve Comstock wrote:

Slipperier and slipperier. OK, let's try a different approach:
You tell me exactly what you want to see from the PL/I routine calling
your API and I'll see if I can cause PL/I to construct that.
In other words, your routine will see
(R1) -  

rc = THEFUNCTION(magic,inputbuffer,inputlength)

(R1) ==  A(magic),A(inputbuffer),A(inputlength)== high bit set on the third 
fullword

OR (the fully specified case):

rc = THEFUNCTION(magic,inputbuffer,inputlength,outputbuffer,outputlength)

(R1) ==  
A(magic),A(inputbuffer),A(inputlength),A(outputbuffer),A(outputlength)== high bit 
set on the fifth fullword

Pretty standard, yes?

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



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

Fwd: Re: PL/I with variable PLISTs (was: LE C calling HLASM)


Sorry, the ! should be a |

bitwise or operator in C

I mixed up bitwise or in C with logical or in PL/1

Kind regards

Bernd




 Original-Nachricht 
Betreff:Re: PL/I with variable PLISTs (was: LE C calling HLASM)
Datum:  Tue, 10 Apr 2012 23:23:39 +0200
Von:Bernd Oppolzer bernd.oppol...@t-online.de
An: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu



I don't know if it helps you, but using C I would code the two calls
this way:

rc = THEFUNCTION (magic, inputbuffer,inputlength, NULL, NULL);


rc = THEFUNCTION (magic, inputbuffer,inputlength, outputbuffer,outputlength);


Note that the parameters that are probably integers are prefixed with an
ampersand
to pass the addresses.

If it is needed that the 3rd and the 5th address has the high order bit
set,
you can to this in C, too. I would use a macro called HIGHBITON (x), for
example,
which is coded as follows:

#define HIGHBITON(x)  (void *)((unsigned int)(x) ! 0x8000)

So we have


rc = THEFUNCTION (magic, inputbuffer, HIGHBITON(inputlength), NULL, NULL);


rc = THEFUNCTION (magic, inputbuffer,inputlength, outputbuffer, 
HIGHBITON(outputlength));


The two additional NULL parameters after the 3rd address in the first
case do no harm.

Kind regards

Bernd



Am 10.04.2012 23:11, schrieb Phil Smith:

 Steve Comstock wrote:

 Slipperier and slipperier. OK, let's try a different approach:
 You tell me exactly what you want to see from the PL/I routine calling
 your API and I'll see if I can cause PL/I to construct that.
 In other words, your routine will see
 (R1) -   

 rc = THEFUNCTION(magic,inputbuffer,inputlength)

 (R1) ==   A(magic),A(inputbuffer),A(inputlength)== high bit set on the third 
fullword

 OR (the fully specified case):

 rc = THEFUNCTION(magic,inputbuffer,inputlength,outputbuffer,outputlength)

 (R1) ==   
A(magic),A(inputbuffer),A(inputlength),A(outputbuffer),A(outputlength)== high bit 
set on the fifth fullword

 Pretty standard, yes?

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




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

Re: Strange SDSF behavior

2012-04-10 Thread Mark Zelden

On Tue, 10 Apr 2012 15:18:30 -0600, Steve Comstock st...@trainersfriend.com 
wrote:

Twice today the order of jobs in the SDSF status queue
has been changed on me without my issuing any commands.
That is, if you choose the View menu and Sort option,
the value is different from what I set!


I'm the only one on the system.

Has anyone else seen this behavior? (z/OS 1.13)


The columns are now cursor sensitive for sorting in 1.13.   I keep finding 
myself
accidentally doing it also by moving around too fast.   You can disable it
if you want with SET CSORT OFF.   I use point and shoot ever everywhere
else, so for now I'm leaving it on and hopefully I'll get used to it
more with less mistakes.

It helps if you always run with SET DISPLAY ON.  Then at least when you 
turn on sorting (accidentally or not) you can see it is on.

See what's new under HELP for more info.

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS   
mailto:m...@mzelden.com
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html 
Systems Programming expert at http://expertanswercenter.techtarget.com/

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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)

Bernd Oppolzer wrote:
I don't know if it helps you, but using C I would code the two calls this way:

rc = THEFUNCTION (magic, inputbuffer,inputlength, NULL, NULL);

Exactly backwards-the idea here is to NOT be obscure, but to have a nice, 
flexible, intuitive API. Having to specify null parameters or to use a macro 
for things is what we *don't* want to do.

Thanks though!

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

Fwd: Fwd: Re: PL/I with variable PLISTs (was: LE C calling HLASM)


It just came to my mind that you can do the same thing in PL/1,
if you pass Pointers BYVALUE and treat the pointers in the same way
as I did it in my C example.

I often did this (passing Pointers BYVALUE from PL/1 modules),
when there was the need to call C modules from PL/1 programs
and no other definition of the C ENTRY was appropriate.

for example:

DCL YCSPXML ENTRY (PTR BYVALUE,
   PTR BYVALUE,
   PTR BYVALUE,
   PTR BYVALUE,
   PTR BYVALUE,
   PTR BYVALUE)
OPTIONS (ASM RETCODE);

in fact, it is a C program, returning an int (the retcode).

Kind regards

Bernd




 Original-Nachricht 
Betreff:Fwd: Re: PL/I with variable PLISTs (was: LE C calling HLASM)
Datum:  Tue, 10 Apr 2012 23:26:51 +0200
Von:Bernd Oppolzer bernd.oppol...@t-online.de
Antwort an: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu
An: IBM-MAIN@bama.ua.edu
Newsgruppen:bit.listserv.ibm-main
Referenzen: 4f84a4db.8080...@t-online.de



Sorry, the ! should be a |

bitwise or operator in C

I mixed up bitwise or in C with logical or in PL/1

Kind regards

Bernd




 Original-Nachricht 
Betreff:Re: PL/I with variable PLISTs (was: LE C calling HLASM)
Datum:  Tue, 10 Apr 2012 23:23:39 +0200
Von:Bernd Oppolzerbernd.oppol...@t-online.de
An: IBM Mainframe Discussion ListIBM-MAIN@bama.ua.edu



I don't know if it helps you, but using C I would code the two calls
this way:

rc = THEFUNCTION (magic, inputbuffer,inputlength, NULL, NULL);


rc = THEFUNCTION (magic, inputbuffer,inputlength, outputbuffer,outputlength);


Note that the parameters that are probably integers are prefixed with an
ampersand
to pass the addresses.

If it is needed that the 3rd and the 5th address has the high order bit
set,
you can to this in C, too. I would use a macro called HIGHBITON (x), for
example,
which is coded as follows:

#define HIGHBITON(x)  (void *)((unsigned int)(x) ! 0x8000)

So we have


rc = THEFUNCTION (magic, inputbuffer, HIGHBITON(inputlength), NULL, NULL);


rc = THEFUNCTION (magic, inputbuffer,inputlength, outputbuffer, 
HIGHBITON(outputlength));


The two additional NULL parameters after the 3rd address in the first
case do no harm.

Kind regards

Bernd



Am 10.04.2012 23:11, schrieb Phil Smith:

  Steve Comstock wrote:

  Slipperier and slipperier. OK, let's try a different approach:
  You tell me exactly what you want to see from the PL/I routine calling
  your API and I'll see if I can cause PL/I to construct that.
  In other words, your routine will see
  (R1) -

  rc = THEFUNCTION(magic,inputbuffer,inputlength)

  (R1) ==A(magic),A(inputbuffer),A(inputlength)== high bit set on the 
third fullword

  OR (the fully specified case):

  rc = THEFUNCTION(magic,inputbuffer,inputlength,outputbuffer,outputlength)

  (R1) ==
A(magic),A(inputbuffer),A(inputlength),A(outputbuffer),A(outputlength)== high bit 
set on the fifth fullword

  Pretty standard, yes?

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




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



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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)


IMHO the problem is:

there are different solutions for variable length parameter lists that are
not compatible.

I don't know about the PL/1 solution. Maybe Steve Comstock can help
us with this.

There are two other solutions, but they don't fit well together:

- the OS/360 solution: the last parameter address has the first bit set.
Note that this solution works only with addresses, that is, call by 
reference,

and that it requires 31 bit addressing. Parameters passed by value have
a problem, because they can be negative integers, which seems like the
end of the parameter list

- the C solution with stdarg.h. This solution needs a leading fixed number
of arguments; from those fixed arguments, the total number and the types
of the following variable argument list has to be derived (like in 
printf etc.).

The called function cannot examine the parameter list and recognize
the end of the parameter list, as in the OS solution.

That's IMO the whole dilemma. I don't see any clever solution to this 
problem,

that is: there will be no solution that works perfectly for all languages.

There are more problems with parameter passing. If you are restricted to
parameter passing mechanisms that work in more than one language
(in our case for example: PL/1, ASSEMBLER, C), you have to be very
restrictive. In our case, for example, we found the following solutions:

- no PL/1 descriptors

- only pointers to structures

- only integer results (returncodes)

- structure definitions generated by central repository, so that there are
no different alignment considerations from the three languages (and all
structure components match)

Kind regards

Bernd



Am 10.04.2012 23:31, schrieb Phil Smith:

Bernd Oppolzer wrote:

I don't know if it helps you, but using C I would code the two calls this way:
rc = THEFUNCTION (magic, inputbuffer,inputlength, NULL, NULL);

Exactly backwards-the idea here is to NOT be obscure, but to have a nice, 
flexible, intuitive API. Having to specify null parameters or to use a macro 
for things is what we *don't* want to do.

Thanks though!

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



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

System completion code 201

2012-04-10 Thread Micheal Butz

Hi

I have a piece of CSA storage sp 241
That I am obtaining in key 8
(I know this is a no no)

When go to supervisor state should i code KEY=NZERO on the modeset I am assuming
NZERO is 8 or should I specifically set the storage key to 8


As I am getting a system 201 durning a post/wait of an ECB from this storage

Thanks

Sent from my iPhone

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

Re: Strange SDSF behavior

2012-04-10 Thread Mike Schwab

I was getting that on one particular system.  Supposedly just a few
people, but every few enters to check the progress the order would
change.

On Tue, Apr 10, 2012 at 4:18 PM, Steve Comstock
st...@trainersfriend.com wrote:
 Twice today the order of jobs in the SDSF status queue
 has been changed on me without my issuing any commands.
 That is, if you choose the View menu and Sort option,
 the value is different from what I set!


 I'm the only one on the system.

 Has anyone else seen this behavior? (z/OS 1.13)

-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)

I don't know if this is relevant, but I was looking at the PL/I DL/I (IMS) 
interface (PLITDLI) and noticed that they actually have to pass, as the first 
parameter, a fullword containing the remaining number of items!  Crazy!

For example, in COBOL you say:

call 'CBLTDLI' using ghnp, pcb-mask, i-o-area, ssa-1 ssa-2.

In PL/I it looks like you'd do something like this:
call PLITDLI (five, ghnp, pcb-mask, i-o-area, ssa-1 ssa-2);

See here for more details:
http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp?topic=%2Fcom.ibm.ims11.doc.apg%2Fims_imsdbpliapp.htm

I was pretty happy about what I learned about PL/I until I saw this.  Yuck!

Frank
  


- Original Message -
 From: Phil Smith p...@voltage.com
 To: IBM-MAIN@bama.ua.edu
 Cc: 
 Sent: Tuesday, April 10, 2012 1:54 PM
 Subject: Re: PL/I with variable PLISTs (was: LE C calling HLASM)
 
 Steve Comstock wrote:
  Yes. But that's Assembler. I thought the called routine
 was C, and you were testing the parms passed in the C
 routine. Is that not true? Are there more layers here?
 
 Yes, there are lots of layers, it's a mixture of assembler and C, sorry. The 
 point is, we're confident that the description of the behavior we've 
 seen is as described (we have XDC, too, so can see some of it). it's very 
 strange-as if nobody at IBM ever really tried to use variable plists with 
 PL/I!
 
 --
 For IBM-MAIN subscribe / signoff / archive access instructions,
 send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
 

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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)

Pure speculation on my part:

There are some systems or software components that require that on all calls
(even when the number of parameters is fixed) the last parameter address has
the high order bit set. I recall GDDM, where this was the case.

When I wanted to call GDDM routines from PASCAL/VS (in the 80s), this
was a nightmare.
The GDDM routines complained, because PASCAL/VS did not set the high
order bit

on the last parameter address.

I had to generate ASSEMBLER interfaces in between to insert the high
order bit
at the appropriate position - that is: for every GDDM call there had to
be a short
ASSEMBLER stub that knew the number of parameters and inserted the high
order

bit at the proper position.

Maybe the first word in PLITDLI has exactly the same purpose.

Kind regards

Bernd

Am 11.04.2012 00:19, schrieb Frank Swarbrick:

I don't know if this is relevant, but I was looking at the PL/I DL/I (IMS)
interface (PLITDLI) and noticed that they actually have to pass, as the first
parameter, a fullword containing the remaining number of items! Crazy!

For example, in COBOL you say:

call 'CBLTDLI' using ghnp, pcb-mask, i-o-area, ssa-1 ssa-2.

In PL/I it looks like you'd do something like this:
call PLITDLI (five, ghnp, pcb-mask, i-o-area, ssa-1 ssa-2);

See here for more details:
http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp?topic=%2Fcom.ibm.ims11.doc.apg%2Fims_imsdbpliapp.htm

I was pretty happy about what I learned about PL/I until I saw this. Yuck!

Frank

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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)

- Original Message -
 From: Phil Smith p...@voltage.com
 To: IBM-MAIN@bama.ua.edu
 Cc: 
 Sent: Tuesday, April 10, 2012 3:31 PM
 Subject: Re: PL/I with variable PLISTs (was: LE C calling HLASM)
 
 Bernd Oppolzer wrote:
 I don't know if it helps you, but using C I would code the two calls 
 this way:
 
 rc = THEFUNCTION (magic, inputbuffer,inputlength, NULL, NULL);
 
 Exactly backwards-the idea here is to NOT be obscure, but to have a nice, 
 flexible, intuitive API. Having to specify null parameters or to use a macro 
 for 
 things is what we *don't* want to do.

Haha, I can agree with that!

Funny thing with Enterprise COBOL...  It properly sets the high-order bit on 
the last parm, but supplies no way to interrogate it!  So if THEFUNCTION was 
written in COBOL then you have to invoke it thusly:

CALL 'THEFUNCTION' USING MAGIC, INPUT-BUFFER, INPUT-LENGTH, OMITTED, OMITTED
RETURNING RC.

(The OMITTED keyword simply passes an address of NULL.)

Oy!

Frank

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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)


I would not blame PL/1 for this.
It is not OK IMHO to request the caller to set the
high order bit on the last parameter, when the number of the parameters 
is fixed
(see also my GDDM example on the other post). This is not required by 
any OS convention,

at least that's my understanding.

Kind regards

Bernd



Am 11.04.2012 00:19, schrieb Frank Swarbrick:

I don't know if this is relevant, but I was looking at the PL/I DL/I (IMS) 
interface (PLITDLI) and noticed that they actually have to pass, as the first 
parameter, a fullword containing the remaining number of items!  Crazy!

For example, in COBOL you say:

call 'CBLTDLI' using ghnp, pcb-mask, i-o-area, ssa-1 ssa-2.

In PL/I it looks like you'd do something like this:
call PLITDLI (five, ghnp, pcb-mask, i-o-area, ssa-1 ssa-2);

See here for more details:
http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp?topic=%2Fcom.ibm.ims11.doc.apg%2Fims_imsdbpliapp.htm

I was pretty happy about what I learned about PL/I until I saw this.  Yuck!

Frank




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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)

Well, in the DLI interfaces the number of items passed is NOT fixed.  You can 
pass one or more SSAs on a get call (and some others), and some calls do not 
require an SSA at all.  Some don't even require an I-O area.

Frank



- Original Message -
 From: Bernd Oppolzer bernd.oppol...@t-online.de
 To: IBM-MAIN@bama.ua.edu
 Cc: 
 Sent: Tuesday, April 10, 2012 4:48 PM
 Subject: Re: PL/I with variable PLISTs (was: LE C calling HLASM)
 
 I would not blame PL/1 for this.
 It is not OK IMHO to request the caller to set the
 high order bit on the last parameter, when the number of the parameters 
 is fixed
 (see also my GDDM example on the other post). This is not required by 
 any OS convention,
 at least that's my understanding.
 
 Kind regards
 
 Bernd
 
 
 
 Am 11.04.2012 00:19, schrieb Frank Swarbrick:
  I don't know if this is relevant, but I was looking at the PL/I DL/I 
 (IMS) interface (PLITDLI) and noticed that they actually have to pass, as the 
 first parameter, a fullword containing the remaining number of items!  Crazy!
 
  For example, in COBOL you say:
 
  call 'CBLTDLI' using ghnp, pcb-mask, i-o-area, ssa-1 ssa-2.
 
  In PL/I it looks like you'd do something like this:
  call PLITDLI (five, ghnp, pcb-mask, i-o-area, ssa-1 ssa-2);
 
  See here for more details:
 
 http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp?topic=%2Fcom.ibm.ims11.doc.apg%2Fims_imsdbpliapp.htm
 
  I was pretty happy about what I learned about PL/I until I saw this.  Yuck!
 
  Frank
 
 
 
 --
 For IBM-MAIN subscribe / signoff / archive access instructions,
 send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
 

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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)

On Wed, 11 Apr 2012 00:48:33 +0200, Bernd Oppolzer wrote:

I would not blame PL/1 for this.
It is not OK IMHO to request the caller to set the
high order bit on the last parameter, when the number of the parameters is 
fixed
(see also my GDDM example on the other post). This is not required by
any OS convention,
at least that's my understanding.

It's inconsistently deprecated.  In:

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2a7b0/5.1.8

5.0 ATTACH and ATTACHX -- Create a new task
Subtopics:
* 5.1 Description 

Specify VL=1 only if the called program can be passed a variable number
of parameters. VL=1 causes the high-order bit of the last address to be
set to 1; the bit can be checked to find the end of the list.

Note the word only.  But this admonition appears for ATTACH, but not
for CALL.  Is there any rationale for this difference, or is an RCF in order?
(I haven't checked LINK nor XCTL; they're in a different volume.)

-- gil

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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)


Ok, this is one thing; needs probably some claryfying from IBM.

But, as Frank mentioned in the other post:

I think the high order bit is really needed in the PLITDLI case,
because the number of parameters is not fixed and cannot be
derived from the other parameters in every case (I guess, the number
of SSAs is really variable on the GET request, and the high order bit on
the last SSA marks the end of the list - only speculating; I know almost
nothing about IMS).

So we here have a design where the API relies heavily on the OS/360
high order bit mechanism. Languages that do not set the high order bit
on the last parm address must prefix the address list with the parmcount,
so that the DLI interface knows the number of the parameters.

My opinion is: there are languages that even don't support variable length
parameter lists. But you always find a way to overcome this restriction;
for example: you could pass an array of SSAs as a single parameter
in the case of the IMS GET request (together with a number of entries).
This is what I would normally do in C - starting address of the array and
number of elements, two parameters. You don't really need variable
length parameter lists - they are comfortable sometimes, like with
printf etc, but you can live without them.

Kind regards

Bernd



Am 11.04.2012 01:07, schrieb Paul Gilmartin:

On Wed, 11 Apr 2012 00:48:33 +0200, Bernd Oppolzer wrote:


I would not blame PL/1 for this.
It is not OK IMHO to request the caller to set the
high order bit on the last parameter, when the number of the parameters is fixed
(see also my GDDM example on the other post). This is not required by
any OS convention,
at least that's my understanding.


It's inconsistently deprecated.  In:

 http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2a7b0/5.1.8

 5.0 ATTACH and ATTACHX -- Create a new task
 Subtopics:
 * 5.1 Description

 Specify VL=1 only if the called program can be passed a variable number
 of parameters. VL=1 causes the high-order bit of the last address to be
 set to 1; the bit can be checked to find the end of the list.

Note the word only.  But this admonition appears for ATTACH, but not
for CALL.  Is there any rationale for this difference, or is an RCF in order?
(I haven't checked LINK nor XCTL; they're in a different volume.)

-- gil

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



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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)

We don't have PL/I in our shop (I downloaded an old trial version of 
VisualAge PL/I for Windows to play with at home), but it seems to me that one 
MIGHT be able to do the following for PL/I to call DL/I:

declare CEETDLI entry linkage(SYSTEM);
or perhaps
declare CEETDLI entry(char(4), *, *, *, *, *, *, *, *, *, *) linkage(SYSTEM);

Then call without passing the number of parms:

call CEETDLI(ghnp, pcb-mask, i-o-area, ssa-1 ssa-2);

I am assuming that LINKAGE(SYSTEM) does indeed set the high-order bit in the 
last parm.
I used CEETDLI rather than PLITDLI because I know it can be called from any 
language (COBOL, PL/I, Assembler, maybe C and Fortran), so it can obviously(!) 
handle the high-order bit indicator.


I would be vary curious to have someone with both PL/I and IMS test this out.

Frank



- Original Message -
 From: Bernd Oppolzer bernd.oppol...@t-online.de
 To: IBM-MAIN@bama.ua.edu
 Cc: 
 Sent: Tuesday, April 10, 2012 5:31 PM
 Subject: Re: PL/I with variable PLISTs (was: LE C calling HLASM)
 
 Ok, this is one thing; needs probably some claryfying from IBM.
 
 But, as Frank mentioned in the other post:
 
 I think the high order bit is really needed in the PLITDLI case,
 because the number of parameters is not fixed and cannot be
 derived from the other parameters in every case (I guess, the number
 of SSAs is really variable on the GET request, and the high order bit on
 the last SSA marks the end of the list - only speculating; I know almost
 nothing about IMS).
 
 So we here have a design where the API relies heavily on the OS/360
 high order bit mechanism. Languages that do not set the high order bit
 on the last parm address must prefix the address list with the parmcount,
 so that the DLI interface knows the number of the parameters.
 
 My opinion is: there are languages that even don't support variable length
 parameter lists. But you always find a way to overcome this restriction;
 for example: you could pass an array of SSAs as a single parameter
 in the case of the IMS GET request (together with a number of entries).
 This is what I would normally do in C - starting address of the array and
 number of elements, two parameters. You don't really need variable
 length parameter lists - they are comfortable sometimes, like with
 printf etc, but you can live without them.
 
 Kind regards
 
 Bernd
 
 
 
 Am 11.04.2012 01:07, schrieb Paul Gilmartin:
  On Wed, 11 Apr 2012 00:48:33 +0200, Bernd Oppolzer wrote:
 
  I would not blame PL/1 for this.
  It is not OK IMHO to request the caller to set the
  high order bit on the last parameter, when the number of the parameters 
 is fixed
  (see also my GDDM example on the other post). This is not required by
  any OS convention,
  at least that's my understanding.
 
  It's inconsistently deprecated.  In:
 
       
 http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2a7b0/5.1.8
 
       5.0 ATTACH and ATTACHX -- Create a new task
       Subtopics:
       * 5.1 Description
 
       Specify VL=1 only if the called program can be passed a variable 
 number
       of parameters. VL=1 causes the high-order bit of the last address to 
 be
       set to 1; the bit can be checked to find the end of the list.
 
  Note the word only.  But this admonition appears for ATTACH, 
 but not
  for CALL.  Is there any rationale for this difference, or is an RCF in 
 order?
  (I haven't checked LINK nor XCTL; they're in a different volume.)
 
  -- gil
 
  --
  For IBM-MAIN subscribe / signoff / archive access instructions,
  send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
 
 
 --
 For IBM-MAIN subscribe / signoff / archive access instructions,
 send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
 

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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)

On 4/10/2012 4:33 PM, Frank Swarbrick wrote:

- Original Message -

From: Phil Smithp...@voltage.com
To: IBM-MAIN@bama.ua.edu
Cc:
Sent: Tuesday, April 10, 2012 3:31 PM
Subject: Re: PL/I with variable PLISTs (was: LE C calling HLASM)

Bernd Oppolzer wrote:

I don't know if it helps you, but using C I would code the two calls

this way:

rc = THEFUNCTION (magic, inputbuffer,inputlength, NULL, NULL);

Exactly backwards-the idea here is to NOT be obscure, but to have a nice,
flexible, intuitive API. Having to specify null parameters or to use a macro for
things is what we *don't* want to do.

Haha, I can agree with that!

Funny thing with Enterprise COBOL... It properly sets the high-order bit
on

the last parm, but supplies no way to interrogate it! So if THEFUNCTION was

written in COBOL then you have to invoke it thusly:

CALL 'THEFUNCTION' USING MAGIC, INPUT-BUFFER, INPUT-LENGTH, OMITTED, OMITTED
RETURNING RC.

(The OMITTED keyword simply passes an address of NULL.)

Oy!

Well, there is a little trick you use, involving defining the
trailing parameters as pointers coming in by value, on the
procedure division header name the pointers not the items,
defining items you expect in linkage, redefining a binary
item on top of the pointers, to access one of the data items
use 'set addres of data_item to pointer', when you're done
with an item check if the redefined (binary version) is
negative - that indicates the end of list bit is on.

No problem.

:-)

Frank

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

--

Kind regards,

-Steve Comstock
The Trainer's Friend, Inc.

303-355-2752
http://www.trainersfriend.com

* To get a good Return on your Investment, first make an investment!
  + Training your people is an excellent investment

* Try our tool for calculating your Return On Investment
for training dollars at
  http://www.trainersfriend.com/ROI/roi.html

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

Share in Anaheim - Call for Presentations

2012-04-10 Thread Russell Witt

The deadline for submitting a possible presentation at SHARE in Anaheim is
this Friday (yes, Friday the 13th falls on a Friday this month). In
particular, if you have any MVS Storage related topic, we are always looking
for user presentations. You can either use the SHARE website for submission
at https://share.confex.com/share/119/cfp.cgi or for any MVS Storage related
topics you can submit directly to David at david.astembor...@efirstbank.com.
Either way, if you are an experienced presenter or a first-time newbie, we
would love to hear from you. 

Russell Witt
MVSS Project Manager

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

Re: PL/I with variable PLISTs (was: LE C calling HLASM)