Re: Hipersockets - xposted to VM-L IBM-Main

2008-05-27 Thread Mark Pace
Sorry for the late reply, I've been on vacation.  (some of you may remember
those).

I do not see where you would specify a port name on z/OS.  I've tried to
remove the port names from the z/VM definitions, but thus far it has not
made a difference.

On Tue, May 13, 2008 at 3:32 AM, Alan Altmark [EMAIL PROTECTED]
wrote:

 On Monday, 05/12/2008 at 01:53 EDT, Stephen Frazier
 [EMAIL PROTECTED] wrote:
  My recollection is that the port name must be the same everywhere or
 absent
  everywhere.
  Try removing your port names and see if that works.

 Port names are meaningful to z/OS, not Linux or z/VM. It is ok if some are
 using port names and others are not.  If you are using port names, then
 all users must have the same port name.  First one in wins.

 Alan Altmark
 z/VM Development
 IBM Endicott




-- 
Mark Pace
Mainline Information Systems


Publicly Accessible minidisks

2008-05-27 Thread Hilliard, Chris
Hello List,

 

I'm wrapping up the install of DFSMS/VM...yikes...not the most intuitive
install I've ever done.  Anyway, one of the installation steps calls for
making the DFSMS 1B5 minidisk publicly accessible.  How do you do this
short of including a link for it in each user directory entry?  Is there
some sort of link list facility like there is in z/OS?

 

Thanks...Chris



Re: ESM for SFS

2008-05-27 Thread Bill Munson
Shimon,

Full Function VM:Secure (with Rules Facility enabled) is a very good 
Security Manager and it plays very well with SafeSFS.

good luck

Bill Munson
VM System Programmer
201-418-7588

President MVMUA
http://www2.marist.edu/~mvmua/





Shimon Lebowitz [EMAIL PROTECTED] 
Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
05/25/2008 07:53 AM
Please respond to
The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU


To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
Re: ESM for SFS






 ACF2 and RACF provide ESM support for SFS.
With all the functionality of SafeSFS? Or something different? 
Thanks,
Shimon
-- 

Shimon Lebowitzmailto:[EMAIL PROTECTED]
VM System Programmer   .
Israel Police National HQ. 
Jerusalem, Israel  phone: +972 2 542-9877  fax: 542-9308


*** IMPORTANT
NOTE* The opinions expressed in this
message and/or any attachments are those of the author and not
necessarily those of Brown Brothers Harriman  Co., its
subsidiaries and affiliates (BBH). There is no guarantee that
this message is either private or confidential, and it may have
been altered by unauthorized sources without your or our knowledge.
Nothing in the message is capable or intended to create any legally
binding obligations on either party and it is not intended to
provide legal advice. BBH accepts no responsibility for loss or
damage from its use, including damage from virus.



Re: Publicly Accessible minidisks

2008-05-27 Thread Alan Altmark
On Tuesday, 05/27/2008 at 09:41 EDT, Hilliard, Chris 
[EMAIL PROTECTED] wrote:

 I?m wrapping up the install of DFSMS/VM?yikes?not the most intuitive 
install I?
 ve ever done.  Anyway, one of the installation steps calls for making 
the DFSMS 
 1B5 minidisk publicly accessible.  How do you do this short of including 
a link 
 for it in each user directory entry?  Is there some sort of ?link list? 
 facility like there is in z/OS?

If you do not have a security product installed:
1. Set the read password on the MDISK for DFSMS 1B5 in USER DIRECT to 
ALL
2. Get a security product (IBM recommends the use of an external security 
manager )

If you have a security product installed, change the access rights of the 
DFSMS 1B5 to be everyone has READ authority.  For RACF, this means 
UACC(READ) on the profile.

Alan Altmark
z/VM Development
IBM Endicott


Re: Publicly Accessible minidisks

2008-05-27 Thread Michael Coffin
That would cause the disk to be LINKed, but it still needs to be
ACCESSed as well.

Chris, your best advice is to set up a minidisk that is for public
stuff that you don't want to put on the MAINT 190 or 19E minidisk (the
ONLY two system disks that are automatically accessed when CMS is
IPL'ed).  You will find that there are going to be things that you want
all users to have access to, and you may want to override certain things
on the 190/19E minidisks so access your local public disk at a
filemode lower than S (say R or Q).

I am assuming that you have standard PROFILE statements in your CP
source directory (whether using an ESM like VM:Secure, DIRMAINT or
nothing at all).  For the purposes of this discussion, let's say you
create a userid named PUBLIC and its 191 disk is what you want all users
to access as R, linked as 319.  You'll create a little exec named
VMCONFIG to do your local customizations:

1.  Add the following to your directory PROFILE(s):  LINK PUBLIC 191 319
RR

2.  Modify the SYSPROF EXEC on the MAINT 490/190 disk(s) to call a local
user exit.  HINT: Your code should execute right after the 'SET COMDIR
RELOAD' statement.  Remember that SYSPROF EXEC is in the INSTSEG so
you'll need to resave this once your updates have been made, and of
course since this is a CMS system minidisk makes your changes to MAINT
490, test them, then promote them to MAINT 190 using VMSES update
procedures.

3.  Create your VMCONFIG EXEC and put it on PUBLIC 191.  It can be as
simple as one statement which reads ACCESS 319 R, but of course since
ALL users will now execute this you can be a lot more creative if you
choose to.  My VMCONFIG customizes virtual machines based on CP account
numbers and ACIGROUPs.

That's it!  You now have a public disk that all users will have access
to.  It preceeds the CMS minidisks so you can override programs on the
CMS minidisks if you need to (assuming they aren't NUCX or EXEC loaded,
in which case you'll need to make sure the RIGHT programs get loaded
accordingly).  Put ANY stuff that you want all users to have access to
on PUBLIC 191 and they'll automagically pick up access to it at filemode
R.

-Mike

-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Alan Altmark
Sent: Tuesday, May 27, 2008 9:50 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Publicly Accessible minidisks


On Tuesday, 05/27/2008 at 09:41 EDT, Hilliard, Chris 
[EMAIL PROTECTED] wrote:

 I?m wrapping up the install of DFSMS/VM?yikes?not the most intuitive
install I?
 ve ever done.  Anyway, one of the installation steps calls for making
the DFSMS 
 1B5 minidisk publicly accessible.  How do you do this short of 
 including
a link 
 for it in each user directory entry?  Is there some sort of ?link 
 list?
 facility like there is in z/OS?

Oh, and I forgot to mention that authorizing the disk to be publicly 
available does not automatically cause a LINK to be issued.  This is 
normally handled by placing the LINK statement in a directory profile in

USER DIRECT that gets INCLUDEd.  See Creating directory profiles in 
Chapter 17 of the CP Planning and Admin book.

Alan Altmark
z/VM Development
IBM Endicott


Re: Publicly Accessible minidisks

2008-05-27 Thread Alan Altmark
On Tuesday, 05/27/2008 at 09:41 EDT, Hilliard, Chris 
[EMAIL PROTECTED] wrote:

 I?m wrapping up the install of DFSMS/VM?yikes?not the most intuitive 
install I?
 ve ever done.  Anyway, one of the installation steps calls for making 
the DFSMS 
 1B5 minidisk publicly accessible.  How do you do this short of including 
a link 
 for it in each user directory entry?  Is there some sort of ?link list? 
 facility like there is in z/OS?

Oh, and I forgot to mention that authorizing the disk to be publicly 
available does not automatically cause a LINK to be issued.  This is 
normally handled by placing the LINK statement in a directory profile in 
USER DIRECT that gets INCLUDEd.  See Creating directory profiles in 
Chapter 17 of the CP Planning and Admin book.

Alan Altmark
z/VM Development
IBM Endicott


Re: Publicly Accessible minidisks

2008-05-27 Thread Thomas Kern
To make that disk PUBLIC these days, I would give it a Read-Password of A
LL
(or set appropriate rules in your ESM product of choice) and put an entry

for it in a USERPROD NAMES file on the Y-Disk. These steps should allow a
ny
user to issue the 'VMLINK DFSMS_nickname' command and get the minidisk
linked and accessed. Inside the USERPROD NAMES entry you can specify the
virtual address and access mode that you want to be used. 

If you then want ALL users to get the minidisk automatically (I don't kno
w
why, but you might) then you can put that VMLINK command into your SYSPRO
F
EXEC extension.

/Tom Kern
/301-903-2211


On Tue, 27 May 2008 09:40:48 -0400, Hilliard, Chris
[EMAIL PROTECTED] wrote:

I'm wrapping up the install of DFSMS/VM...yikes...not the most intuitive

install I've ever done.  Anyway, one of the installation steps calls for

making the DFSMS 1B5 minidisk publicly accessible.  How do you do this
short of including a link for it in each user directory entry?  Is there

some sort of link list facility like there is in z/OS?

Thanks...Chris


Re: Getting Console Logs Files to z/OS from z/VM

2008-05-27 Thread Neale Ferguson
Yep since 1.7 I believe.


On 5/27/08 10:12 AM, Michael Coffin [EMAIL PROTECTED] wrote:

 Hi David,
  
 Does z/OS speak TCPNJE?  I thought it had to be SNANJE (at least that was the
 deal back in 2002 when I last looked into this).  Have the z/OS guys finally
 seen the light and provided a TCPNJE protocol?
  
 When a client was getting rid of SNA on VM, we still needed to be able to
 spool files between VM (using RSCS) and z/OS.  Since z/OS did not (at that
 time, at least) support TCPNJE protocol I had to roll my own method which
 basically used LPD protocol for spooling between the two systems.  It worked,
 but not as seamlessly as just having a TCPNJE-driven link would have
 worked.



Re: Publicly Accessible minidisks

2008-05-27 Thread Michael Coffin
Ooops, correction - the ACCESS 319 R statement must (of course) be in
SYSPROF prior to calling your local VMCONFIG EXEC to do other things.
Failing that, VMCONFIG would need to be on the 190 or 19E minidisks, but
that makes changing it later a nuisance so decide what works best for
you.

-Mike

-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Michael Coffin
Sent: Tuesday, May 27, 2008 10:07 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Publicly Accessible minidisks


That would cause the disk to be LINKed, but it still needs to be
ACCESSed as well.

Chris, your best advice is to set up a minidisk that is for public
stuff that you don't want to put on the MAINT 190 or 19E minidisk (the
ONLY two system disks that are automatically accessed when CMS is
IPL'ed).  You will find that there are going to be things that you want
all users to have access to, and you may want to override certain things
on the 190/19E minidisks so access your local public disk at a
filemode lower than S (say R or Q).

I am assuming that you have standard PROFILE statements in your CP
source directory (whether using an ESM like VM:Secure, DIRMAINT or
nothing at all).  For the purposes of this discussion, let's say you
create a userid named PUBLIC and its 191 disk is what you want all users
to access as R, linked as 319.  You'll create a little exec named
VMCONFIG to do your local customizations:

1.  Add the following to your directory PROFILE(s):  LINK PUBLIC 191 319
RR

2.  Modify the SYSPROF EXEC on the MAINT 490/190 disk(s) to call a local
user exit.  HINT: Your code should execute right after the 'SET COMDIR
RELOAD' statement.  Remember that SYSPROF EXEC is in the INSTSEG so
you'll need to resave this once your updates have been made, and of
course since this is a CMS system minidisk makes your changes to MAINT
490, test them, then promote them to MAINT 190 using VMSES update
procedures.

3.  Create your VMCONFIG EXEC and put it on PUBLIC 191.  It can be as
simple as one statement which reads ACCESS 319 R, but of course since
ALL users will now execute this you can be a lot more creative if you
choose to.  My VMCONFIG customizes virtual machines based on CP account
numbers and ACIGROUPs.

That's it!  You now have a public disk that all users will have access
to.  It preceeds the CMS minidisks so you can override programs on the
CMS minidisks if you need to (assuming they aren't NUCX or EXEC loaded,
in which case you'll need to make sure the RIGHT programs get loaded
accordingly).  Put ANY stuff that you want all users to have access to
on PUBLIC 191 and they'll automagically pick up access to it at filemode
R.

-Mike

-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Alan Altmark
Sent: Tuesday, May 27, 2008 9:50 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Publicly Accessible minidisks


On Tuesday, 05/27/2008 at 09:41 EDT, Hilliard, Chris 
[EMAIL PROTECTED] wrote:

 I?m wrapping up the install of DFSMS/VM?yikes?not the most intuitive
install I?
 ve ever done.  Anyway, one of the installation steps calls for making
the DFSMS 
 1B5 minidisk publicly accessible.  How do you do this short of
 including
a link 
 for it in each user directory entry?  Is there some sort of ?link
 list?
 facility like there is in z/OS?

Oh, and I forgot to mention that authorizing the disk to be publicly 
available does not automatically cause a LINK to be issued.  This is 
normally handled by placing the LINK statement in a directory profile in

USER DIRECT that gets INCLUDEd.  See Creating directory profiles in 
Chapter 17 of the CP Planning and Admin book.

Alan Altmark
z/VM Development
IBM Endicott


Re: Getting Console Logs Files to z/OS from z/VM

2008-05-27 Thread Mark Jacobs
Michael Coffin wrote:
 Hi David,
  
 Does z/OS speak TCPNJE?  I thought it had to be SNANJE (at least that
 was the deal back in 2002 when I last looked into this).  Have the
 z/OS guys finally seen the light and provided a TCPNJE protocol?
  
 When a client was getting rid of SNA on VM, we still needed to be able
 to spool files between VM (using RSCS) and z/OS.  Since z/OS did not
 (at that time, at least) support TCPNJE protocol I had to roll my
 own method which basically used LPD protocol for spooling between the
 two systems.  It worked, but not as seamlessly as just having a
 TCPNJE-driven link would have worked.
  
 -Mike

JES2 at the zOS 1.7 with the apar listed below(and above) supports TCPIP NJE

  APAR Identifier .. OA12364 
https://www-304.ibm.com/jct03004c/ibmlink/ast/viewAparDoc.wss?context=apardocumentIds=OA12364lc=encc=US
  Last Changed  07/02/13
  NEW FUNCTION -  ENABLE NJE OVER TCP/IP IN JES2 Z/OS 1.7
  (HJE7720)


Mark Jacobs

 -Original Message-
 *From:* The IBM z/VM Operating System
 [mailto:[EMAIL PROTECTED] *On Behalf Of *David Boyes
 *Sent:* Friday, May 23, 2008 12:28 PM
 *To:* IBMVM@LISTSERV.UARK.EDU
 *Subject:* Re: Getting Console Logs  Files to z/OS from z/VM

  I have to get my z/VM console log files over to z/OS and I don't
 know the best procedure to use to do this.
  What is the best procedure to use?

 We’ve developed a one-link TCPNJE implementation based on REXX and
 CMS Pipelines that provides the ability to transfer files and
 messages to a full TCPNJE implementation located somewhere else on
 the network – kind of a RSCS “lite” that does only the VM spool
 interface component and NJE over IP transmission/receipt functions
 of RSCS. If your z/OS is at release 1.7 or higher, this would
 allow you to just use SENDFILE or use real-time interactive
 messages to get the data to z/OS.

  

 It provides the basic NJE file transfer and interactive message
 capabilities, but can talk to only one remote host (the remote
 host has to have a full TCPNJE implementation, like JES or RSCS,
 or the NJE Bridge for Linux and other non-IBM operating systems).
 All you need is a IP connection between the VM system and the
 remote system running the full TCPNJE implementation.

  

 If anyone would find that useful, I’ll look into making it
 available for download. I’ll probably ask for a small donation to
 help recoup the development costs, but it’s pretty handy (and lots
 cheaper than a full RSCS license…).

  

 -- db

  



-- 
Mark Jacobs
Time Customer Service
Tampa, FL


Progress doesn't come from early risers - progress is made 
by lazy men looking for easier ways to do things.

Robert A. Heinlein - Time Enought for Love(1973)


Re: Getting Console Logs Files to z/OS from z/VM

2008-05-27 Thread Michael Coffin
Hi David,
 
Does z/OS speak TCPNJE?  I thought it had to be SNANJE (at least that
was the deal back in 2002 when I last looked into this).  Have the z/OS
guys finally seen the light and provided a TCPNJE protocol?
 
When a client was getting rid of SNA on VM, we still needed to be able
to spool files between VM (using RSCS) and z/OS.  Since z/OS did not
(at that time, at least) support TCPNJE protocol I had to roll my own
method which basically used LPD protocol for spooling between the two
systems.  It worked, but not as seamlessly as just having a
TCPNJE-driven link would have worked.
 
-Mike

-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of David Boyes
Sent: Friday, May 23, 2008 12:28 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Getting Console Logs  Files to z/OS from z/VM



 I have to get my z/VM console log files over to z/OS and I don't know
the best procedure to use to do this.
 What is the best procedure to use?

We've developed a one-link TCPNJE implementation based on REXX and CMS
Pipelines that provides the ability to transfer files and messages to a
full TCPNJE implementation located somewhere else on the network - kind
of a RSCS lite that does only the VM spool interface component and NJE
over IP transmission/receipt functions of RSCS. If your z/OS is at
release 1.7 or higher, this would allow you to just use SENDFILE or use
real-time interactive messages to get the data to z/OS.

 

It provides the basic NJE file transfer and interactive message
capabilities, but can talk to only one remote host (the remote host has
to have a full TCPNJE implementation, like JES or RSCS, or the NJE
Bridge for Linux and other non-IBM operating systems). All you need is a
IP connection between the VM system and the remote system running the
full TCPNJE implementation. 

 

If anyone would find that useful, I'll look into making it available for
download. I'll probably ask for a small donation to help recoup the
development costs, but it's pretty handy (and lots cheaper than a full
RSCS license.). 

 

-- db

 



Re: Getting Console Logs Files to z/OS from z/VM

2008-05-27 Thread Dave Yarris
Please send it my way..thanks!





Lionel B. Dyck [EMAIL PROTECTED] 
Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
05/27/2008 10:18 AM
Please respond to
The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU


To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
Re: Getting Console Logs  Files to z/OS from z/VM







Hi - we don't have RSCS or TCPNJE so our solution was to build an exec 
that extracts the files from the spool, wraps iebgener jcl around it, and 
then ftp's to z/OS where the job runs and the output is then picked up for 
archiving by CA-View (aka SAR). 

I'd be willing to share this if anyone is interested
Lionel B. Dyck, Consultant/Specialist 
Enterprise Platform Services, Mainframe Engineering 
KP-IT Enterprise Engineering 
925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED] 
AIM: lbdyck | Yahoo IM: lbdyck 
Kaiser Service Credo: Our cause is health. Our passion is service. We're 
here to make lives better. 

I never guess. It is a capital mistake to theorize before one has data. 
Insensibly one begins to twist facts to suit theories, instead of theories 
to suit facts. 
- Sir Arthur Conan Doyle 

NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, 
you are prohibited from sharing, copying, or otherwise using or disclosing 
its contents. If you have received this e-mail in error, please notify the 
sender immediately by reply e-mail and permanently delete this e-mail and 
any attachments without reading, forwarding or saving them. Thank you. 


Re: Getting Console Logs Files to z/OS from z/VM

2008-05-27 Thread Lionel B. Dyck
Hi - we don't have RSCS or TCPNJE so our solution was to build an exec 
that extracts the files from the spool, wraps iebgener jcl around it, and 
then ftp's to z/OS where the job runs and the output is then picked up for 
archiving by CA-View (aka SAR).

I'd be willing to share this if anyone is interested

Lionel B. Dyck, Consultant/Specialist 
Enterprise Platform Services, Mainframe Engineering 
KP-IT Enterprise Engineering 
925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED] 
AIM: lbdyck | Yahoo IM: lbdyck 
Kaiser Service Credo: Our cause is health. Our passion is service. We're 
here to make lives better. 

I never guess. It is a capital mistake to theorize before one has data. 
Insensibly one begins to twist facts to suit theories, instead of theories 
to suit facts. 
- Sir Arthur Conan Doyle 

NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, 
you are prohibited from sharing, copying, or otherwise using or disclosing 
its contents. If you have received this e-mail in error, please notify the 
sender immediately by reply e-mail and permanently delete this e-mail and 
any attachments without reading, forwarding or saving them. Thank you. 

Re: Hipersockets - xposted to VM-L IBM-Main

2008-05-27 Thread Ivica Brodaric
Maybe you are not even using port name on z/OS. I don't know much about
z/OS, so I cannot help you find it, but even if you are not using port name
in z/OS, you have to be sure that nothing else comes up before the z/OS
guest, connects to the hipersocket and changes port name from nothing into
something.(1) Did you check your z/VSE stack for a port name?
(2) Did you have a chance to reset the hipersocket CHPID (vary off the CHPID
from all LPARs *at the same time*, then vary it on to all)?

I remember that on z800 hardware port names could differ in one character
out of eight (but one only), and microcode check would pass. Eg, port names
HSOA1 and HSOB1 were OK, but not HSOB2. Later on I found out that this is in
fact how it worked. This applied both to hipersockets and OSA's. From z990
onwards, this slack was removed and from then on all port names must be
identical or not used at all. So, if you don't really need port names (and
z/VM allows you to not use them from release 4.4 onwards), this exercise of
removing them is well worth your while. And if you do (1) and (2) above, you
will at least be sure that port name is *not* your problem. Then, we'll dig
deeper.

Ivica

On Tue, May 27, 2008 at 10:28 PM, Mark Pace [EMAIL PROTECTED] wrote:

 Sorry for the late reply, I've been on vacation.  (some of you may remember
 those).

 I do not see where you would specify a port name on z/OS.  I've tried to
 remove the port names from the z/VM definitions, but thus far it has not
 made a difference.


 On Tue, May 13, 2008 at 3:32 AM, Alan Altmark [EMAIL PROTECTED]
 wrote:

 On Monday, 05/12/2008 at 01:53 EDT, Stephen Frazier
 [EMAIL PROTECTED] wrote:
  My recollection is that the port name must be the same everywhere or
 absent
  everywhere.
  Try removing your port names and see if that works.

 Port names are meaningful to z/OS, not Linux or z/VM. It is ok if some are
 using port names and others are not.  If you are using port names, then
 all users must have the same port name.  First one in wins.

 Alan Altmark
 z/VM Development
 IBM Endicott




 --
 Mark Pace
 Mainline Information Systems



Re: Getting Console Logs Files to z/OS from z/VM

2008-05-27 Thread Les Geer (607-429-3580)

 Does z/OS speak TCPNJE?  I thought it had to be SNANJE (at least that
 was the deal back in 2002 when I last looked into this).  Have the
 z/OS guys finally seen the light and provided a TCPNJE protocol?

 When a client was getting rid of SNA on VM, we still needed to be able
 to spool files between VM (using RSCS) and z/OS.  Since z/OS did not
 (at that time, at least) support TCPNJE protocol I had to roll my
 own method which basically used LPD protocol for spooling between the
 two systems.  It worked, but not as seamlessly as just having a
 TCPNJE-driven link would have worked.

 -Mike

JES2 at the zOS 1.7 with the apar listed below(and above) supports TCPIP NJE

  APAR Identifier .. OA12364
https://www-304.ibm.com/jct03004c/ibmlink/ast/viewAparDoc.wss?context=apardocumentIds=OA12364lc=encc=US
  Last Changed
 07/02/13
  NEW FUNCTION -  ENABLE NJE OVER TCP/IP IN JES2 Z/OS 1.7
  (HJE7720)


In addition, you should ensure:
JES2 APARs OA19964 and OA22718 have been applied.
JES common code APAR OA19875 is applied
RSCS APAR VM64170 is applied

Best Regards,
Les Geer
IBM z/VM and Linux Development


Re: Getting Console Logs Files to z/OS from z/VM

2008-05-27 Thread Schuh, Richard
I'll second that, said one who found out the hard way. :-) I was in
the process of digging out the APAR numbers when you saved me the
effort. Thanks.  

Regards, 
Richard Schuh 

 

 -Original Message-
 From: The IBM z/VM Operating System 
 [mailto:[EMAIL PROTECTED] On Behalf Of Les Geer (607-429-3580)
 Sent: Tuesday, May 27, 2008 9:09 AM
 To: IBMVM@LISTSERV.UARK.EDU
 Subject: Re: Getting Console Logs  Files to z/OS from z/VM
 
 
 In addition, you should ensure:
 JES2 APARs OA19964 and OA22718 have been applied.
 JES common code APAR OA19875 is applied
 RSCS APAR VM64170 is applied
 
 Best Regards,
 Les Geer
 IBM z/VM and Linux Development
 


Re: Hipersockets

2008-05-27 Thread Alan Altmark
On Tuesday, 05/27/2008 at 11:35 EDT, Ivica Brodaric 
[EMAIL PROTECTED] wrote:
 Maybe you are not even using port name on z/OS. I don't know much about 
z/OS, 
 so I cannot help you find it, but even if you are not using port name in 
z/OS, 
 you have to be sure that nothing else comes up before the z/OS guest, 
connects 
 to the hipersocket and changes port name from nothing into something.

A mismatched port name on an OSA creates an initialization error.  In any 
case, HiperSockets do not have port names.  On z/OS they are addressed 
solely by chpid (DEVICE IUTIQDxx).

My apologies for creating confusion; I was addressing only the incorrect 
assertions about port names rather than focusing on the problem at hand.

It's been a while and I've forgotten the details, but HiperSocket 
communication requires:
1. Both LPARs reference the same HiperSocket chpid.  Note that z/OS does 
not allow specification of a HiperSocket chpid that is being used for 
dynamic XCF.
Verify: Get a packet trace to see that packets are being place on and 
received from the HiperSocket.

2. Both IP stacks have correct local routes.  That is, the same subnet and 
subnet mask with no gateway specification.
Verify: Look at the routing table.  Make sure the gateway for the 
HiperSocket subnet is 0.0.0.0.  And make sure you don't have overlapping 
routes.

3. Both stacks are using the same MTU and that MTU is consistent with the 
MFS value in the chpid definition.
Verify: It shouldn't cause a problem with PING, but will result in lost 
packets for any frame that exceeds the MTU of the receiver.

If you want to do all that, fine, but I'd suggest first bringing up both 
images as z/VM guests and connect them to a HiperSocket Guest LAN instead 
of real HiperSockets.  Be sure to use the CHPID parameter on the NICDEF 
for a z/OS guest to ensure that the correct virtual chpid is chosen, 
matching your real HiperSocket chpid number.

Compare the routing tables.  They should be the same, virtual or real, as 
far as the HiperSocket interface is concerned.

By the way, I'm not cross-posting to IBM-MAIN.  Let's try to consolidate 
discussion in just one place (here).

Alan Altmark
z/VM Development
IBM Endicott


JAVA and Z/VM

2008-05-27 Thread Edward M. Martin
  

Hello Everyone,

 

 Does z/VM TCP/IP support JAVA?  

 

 A Saleman indicated that Unfortunately, IBM doesn't support Java on
VM yet, and our Oracle and SQL Server Interfaces are written in Java.

 

I have found a redbook VM/ESA Network Computing with Java
and NetRexx.

 

Thanks for any info.

 

Ed Martin

330-588-4723

ext 40441

 



Re: JAVA and Z/VM

2008-05-27 Thread Jack Woehr

Edward M. Martin wrote:


 A Saleman indicated that */Unfortunately, IBM doesn't support 
Java on VM yet, and our Oracle and SQL Server Interfaces are written 
in Java./***


* *


More like, Doesn't support Java on VM /anymore/.

--
Jack J. Woehr# Self-delusion is
http://www.well.com/~jax #  half the battle!
http://www.softwoehr.com #  - Zippy the Pinhead



Re: JAVA and Z/VM

2008-05-27 Thread dave
Hi, Ed.

- Original Message Follows -
From: Edward M. Martin [EMAIL PROTECTED]
To: IBMVM@LISTSERV.UARK.EDU
Subject: JAVA and Z/VM
Date: Tue, 27 May 2008 13:09:14 -0400

   
 
 Hello Everyone,
 
  
 
  Does z/VM TCP/IP support JAVA?  
 

No, it does not.

  
 
  A Saleman indicated that Unfortunately, IBM doesn't
 support Java on VM yet, and our Oracle and SQL Server
 Interfaces are written in Java.
 
  

For all intents and purposes, IBM no longer supports Java
under VM, by which I mean Java running in a CMS virtual
machine. The Java support that IBM did ship with VM is now
horribly out of date, not to mention out of service as well.

If you need to run Java applications on VM, the preferred
method is to run them on a VM guest Linux system. 
 
 I have found a redbook VM/ESA Network
 Computing with Java and NetRexx.
 
  

I  believe that most of that material is now out of date, as
well.

Have a good one.

DJ
 
 Thanks for any info.
 
  
 
 Ed Martin
 
 330-588-4723
 
 ext 40441
 
  
 
 


Re: Publicly Accessible minidisks

2008-05-27 Thread David Boyes
How we'd do it (this relates to the discussion of a few weeks ago): 

 

Give it a read password of ALL (or equivalent rule in your ESM), and add
a DFSMS target to USERPROD NAMES on MAINT 19E. Then just tell anyone who
needs it to VMLINK DFSMS, or put it in SYSPROF EXEC and resave CMS. 

 



From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Hilliard, Chris
Sent: Tuesday, May 27, 2008 9:41 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Publicly Accessible minidisks

 

Hello List,

 

I'm wrapping up the install of DFSMS/VM...yikes...not the most intuitive
install I've ever done.  Anyway, one of the installation steps calls for
making the DFSMS 1B5 minidisk publicly accessible.  How do you do this
short of including a link for it in each user directory entry?  Is there
some sort of link list facility like there is in z/OS?

 

Thanks...Chris



Re: Getting Console Logs Files to z/OS from z/VM

2008-05-27 Thread David Boyes
 

Does z/OS speak TCPNJE?  I thought it had to be SNANJE (at least that
was the deal back in 2002 when I last looked into this).  Have the z/OS
guys finally seen the light and provided a TCPNJE protocol?

 

Yes, finally, z/OS 1.7 and later have TCPNJE (although you need some
PTFs for it to work correctly on 1.7). Previous to 1.7, you'd need
either RSCS (SNA or CTC) or the full NJE Bridge (via CTC). 

 



Re: JAVA and Z/VM

2008-05-27 Thread Michael Donovan

Ed,

The Java and NetRexx support discussed in the redbook,  VM/ESA Network
Computing with Java and NetRexx, was discontinued before z/VM 5.1.0 became
generally available.  The level of Java had become very outdated.  If you
want and need Java support, you should be looking at running it from a
Linux guest.

Thanks!
 Mike Donovan





   
 Edward M.
 Martin   
 [EMAIL PROTECTED]  To
 com  IBMVM@LISTSERV.UARK.EDU 
 Sent by: The IBM   cc
 z/VM Operating
 SystemSubject
 [EMAIL PROTECTED] JAVA and Z/VM   
 ARK.EDU  
   
   
 05/27/2008 01:09  
 PM
   
   
 Please respond to 
   The IBM z/VM
 Operating System  
 [EMAIL PROTECTED] 
 ARK.EDU  
   
   





  Hello Everyone,

   Does z/VM TCP/IP support JAVA?

   A Saleman indicated that Unfortunately, IBM doesn't support Java
  on VM yet, and our Oracle and SQL Server Interfaces are written in
  Java.

  I have found a redbook VM/ESA Network Computing with Java
  and NetRexx.

  Thanks for any info.

  Ed Martin
  330-588-4723
  ext 40441


Re: JAVA and Z/VM

2008-05-27 Thread Alan Altmark
On Tuesday, 05/27/2008 at 01:10 EDT, Edward M. Martin 
[EMAIL PROTECTED] wrote:
  A Saleman indicated that Unfortunately, IBM doesn't support Java on 
VM 
 yet, and our Oracle and SQL Server Interfaces are written in Java.

This statement is unclear.  Exactly what Oracle and SQL server did you 
develop your Java for?  Are you talking about server side Java apps? Or 
are you talking about just needing compatibility in the server so that 
your client-side Java apps can talk to it (i.e. JDBC).

If you're running these databases run on Linux, not CMS, the lack of Java 
support in CMS doesn't matter.

Alan Altmark
z/VM Development
IBM Endicott


Re: Hipersockets

2008-05-27 Thread Ivica Brodaric
Alan,


 A mismatched port name on an OSA creates an initialization error.


Correct, but with a caveat explained in the other thread (yes for z990
onwards, before z990 one character could mismatch. I know it sounds weird,
but that's the way it worked)

In any case, HiperSockets do not have port names.


Ummm, no. They can be specified for HiperSocket connection in DEVICE
statement in VM and in DEFINE LINK statement in VSE. And after peeking into
some z/OS manuals, I found that even z/OS is not oblivious to port names.
From z/OS V1R9.0 Communications Server IP Configuration Guide:

quote
Therefore, there are two types of HiperSockets devices:

   - DYNAMICXCF HiperSockets device or interface (TRLE IUTIQDIO and an MPC
   group of subchannel devices). The PORTNAME will be IUTIQDxx, where xx = the
   IQD CHPID that VTAM(R) uses (for example, IUTIQDFD when using IQD CHPID
   x'FD').
   - A user-defined HiperSockets device or interface (TRLE IUTIQDxx and an
   MPC group of subchannel devices). The PORTNAME is not applicable for this
   TRLE.

In both cases, the TRLE is dynamically built by VTAM.

end quote

I presume that we have a user-defined HiperSocket here, but in the response
to Q LAN DETAILS command for the virtual LAN that Mark defined to test the
connection to the VM stack via virtual HiperSocket there is a following
line:

Adapter Owner: ZOS19NIC: 0724  Name: *IUTIQDFF*

That Name: at the end is port name (not device name). If the portname was
not used by z/OS, it should've said Name: UNASSIGNED. So which one is it?
DYNAMICXCF or user-defined? And why did it work anyway? Maybe virtual
HiperSocket is more lax towards the port names than real HiperSocket,
because Mark says that the connection over the virtual HiperSocket worked.

I also do not want to overly emphasize this port name thing, but I still
think that it is worth while clearing.

I think Mark said that he copied z/OS from the LPAR to a guest on VM,
changed the home IP address and attached the real HiperSocket device trio to
z/OS guest as the same addresses that z/OS expects. So I don't think that we
will get any further by doing that again, except that this new copy of z/OS
will be unmodified. Maybe still worth a try...

Your point 1 seems to be in contradiction with the quote above, but I'll
believe you have your reasons.

Your point about MFS and MTU is great. I can't see nothing wrong in NETSTAT
HOME and NETSTAT GATE responses provided in the other thread, but I noticed
there that packet size is 57344 (56K) for IUTLNK1 link. How does that work?
Does z/OS automatically adjust the MTU of the interface when the device is
activated? This would indicate that CHPID is defined with OS=C0 (64K
MFS).

Mark, when you defined a virtual HiperSocket, you used default MFS of 16K as
I see in QUERY LAN response. Try with MFS 64K operand in DEFINE LAN. Just to
remove any difference between the real and virtual HiperSocket...

Ivica Brodaric