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

[David Price]

Looking at z/OS UNIX System Services "Ported Tools"
http://www-03.ibm.com/systems/z/os/zos/features/unix/bpxa1ty1.html
there is an X-Windows editor called "nedit" that IBM makes available for z/OS 
UNIX.

Does this imply that X-Windows under z/OS UNIX System Services is usable 
(perhaps with IBM's Ported Tools)?
I guess if I really wanted to know I'd subscribe to the MVS-OE List Server.

Turning to the z/OS MVS side for a moment, I see that GDDM/MVS supports 
X-Windows graphics through the GDDMXD/MVS interface.  So if your 3270 emulator 
doesn't support drawing graphs etc you could have an X-Window pop up on the 
side and do it that way.

-dap
__
On Sun, Apr 8, 2012 at 1:58 PM, Paul Gilmartin  wrote:

> On Sun, 8 Apr 2012 13:39:11 -0700, Sam Siegel wrote:
> >
> >The IBM XL C/C++ team did a GREAT jobs with ASCII compatibility.  :-)
> >
> Overall, yes, but, last time I checked, no Curses; no X11.
> Sockets?  I don't know.
>
> -- gil

On Sun, 8 Apr 2012 14:00:56 -0700, Sam Siegel wrote:
Good to know.  I'm in luck, my app does not need those features.

--
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

[Mark Post]

>>> On 4/8/2012 at 08:49 PM, Tony Harminc  wrote: 
> 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?

Don't assume that because they're not UNIX branded that they're not POSIX 
compliant.

Besides Linux, there is MacOS, which is based on (one of the) BSDs.  There's 
also BSD, FreeBSD, OpenBSD, NetBSD, Dragonfly BSD, Minix, GNU Hurd, Darwin, 
OpenSolaris, and probably many more that I've never heard of before.


Mark Post

--
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

[Tony Harminc]

On 8 April 2012 13:43, Paul Gilmartin  wrote:

> o While many UNIX-like systems provide a definition of PATH_MAX
>  in /usr/include/limits.h, POSIX deprecates this, and USS does not
>  provide one.  IBM gives the rationale that the limit is filesystem-
>  dependent and code relying on it might become obsoleted by
>  new technology.

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?

> o A very deep path can cause "rm -rf" to fail in violation of POSIX
>  spec with a "too many open files" error.

What has IBM's response been? Surely if they are POSIX/UNIX branded,
they must comply.

Tony H.

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

Re: Coding IEASYMxx

[retired mainframer]

Keep it in the list please.  You get more responses and any incorrect advice
will be caught by others.

 

The few symbols that IBM needs, such as &SYSR1, are built automatically.
There is no need for a default IEASYMxx.  Considering the multitude of
filtering options allowed, I doubt if IBM could come up with one that didn't
cause more problems than it solved.

 

If your LOADxx member specifies your PARMLIB libraries, I think you can
place the IEASYMxx in anyone of those.  The same may be true if your
PARMLIBs are specified in MSTRJCL.  I have always put it in SYS1.PARMLIB but
that may be just force of habit.

 

  _  

From: 
Sent: Sunday, April 08, 2012 5:33 AM

Subject: Re: Coding IEASYMxx

 

Hi,

 

Thanks a bunch again, but recently I have installed a new system.
Surprisingly IEASYmxx were not in any of my parmlibs, so Just wanted to know
If I can create this member manually in any of the parmlib and update the
same in LOADxx member ?

 

Please advise me your expert comment.

 

 

Jake

On Sun, Apr 8, 2012 at 7:46 AM, retired mainframer
 wrote:

:>: -Original Message-
:>: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
:>: Behalf Of Jake anderson
:>: Sent: Saturday, April 07, 2012 6:58 PM
:>: To: IBM-MAIN@bama.ua.edu
:>: Subject: Coding IEASYMxx
:>:
:>: Hello All,

:>:
:>: First of all apology for asking a very basic question and being
:>: ignorant.In
:>: our shop we have two sysres volumes MTSRS1, MTSRS2,MSTRS3 so during
:>: SYSRES
:>: cloning we adopt indirect cataloging. Also it is important to specify
:>: the
:>: symbolic parameter at IEASYMxx member. My only basic question is that
:>: will
:>: it be wise enough to code like below :
:>:
:>: SYMDEF(&SYSR2='MTSRS2')
:>: SYMDEF(&SYSR3='MTSRS3').

If you code it like this, then when you have a second set of SYSRES volumes,
say TSTRS1, TSTRS2, TSTRS3, &SYSR1 will resolve to TSTRS1 as you want but
&SYSR2 will still resolve to the MTSRS2, not TSTRS2.

:>:
:>: I have referred the link
:>: http://publib.boulder.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fco
:>: m.ibm.zos.r12.ieae200%2Fplnsym.htm
:>:  but I am not really able to understand the below coding when we more

:>: than
:>: 1 sysres volumes :
:>:
:>: :SYSDEF .
:>:
:>:.
:>:SYMDEF(&SYSR2='&SYSR1(1:3).RS2') /* second SYSRES logical
:>:   extension */

This code says set the value of &SYSR2 to the first three characters of
&SYSR1 followed by the characters RS2.  When you IPL from MTSRS1, the first
three characters of &SYSRS1 are MTS so &SYSRS2 resolves to MTSRS2.  And when
you IPL from TSTRS1, the first three characters are TST so &SYSR2 will
resolve to TSTRS2.  This insures that &SYSRS1, &SYSRS2, and &SYSRS3 always
resolve to the three volumes that are part of a matched set.

:>:SYMDEF(&SYSR3='&SYSR1(1:3).RS3') /* third SYSRES logical

:>:  extension  */"
:>:
:>:
:>: Could anyone please explain me about the above syntax. How to make use
:>: the of the above syntax reasonably.

The only change you need to make to the above is to decide how many volumes
are involved.  My last system (1.11) had only two 3390-9s so I didn't bother
with &SYSRS3.

--
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: ASCII (was: Unix path name)

[Sam Siegel]

On Sun, Apr 8, 2012 at 1:58 PM, Paul Gilmartin  wrote:

> On Sun, 8 Apr 2012 13:39:11 -0700, Sam Siegel wrote:
> >
> >The IBM XL C/C++ team did a GREAT jobs with ASCII compatibility.  :-)
> >
> Overall, yes, but, last time I checked, no Curses; no X11.
> Sockets?  I don't know.
>

Good to know.  I'm in luck, my app does not need those features.


>
> -- 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

ASCII (was: Unix path name)

[Paul Gilmartin]

On Sun, 8 Apr 2012 13:39:11 -0700, Sam Siegel wrote:
>
>The IBM XL C/C++ team did a GREAT jobs with ASCII compatibility.  :-)
> 
Overall, yes, but, last time I checked, no Curses; no X11.
Sockets?  I don't know.

-- gil

--
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

[Sam Siegel]

On Sun, Apr 8, 2012 at 1:15 PM, Paul Gilmartin  wrote:

> On Sun, 8 Apr 2012 12:55:54 -0700, Sam Siegel wrote:
> >
> >Actually it is C.  The intermediate buffer is used to allow the UNICODE
> >service to translate to ASCII.  UNICODE services need to know how much
> data
> >is being passed in.  The code runs POSIX(ON), XPLINK and is compiled the
> >ASCII option.
> >
> And then the C RTL will further translate it to the "native" EBCDIC.
> Many ASCII-centric systems treat UTF-8 as practically standard.
> (But the filenames contain nonportable characters.)  Does the
> caller pass you ASCII, presumed ISO8859-1, UTF-8, or other?
> Will the files be shared (NFS?) or exported (pax?) to native ASCII
> systems?
>

Yep ... I'm aware that C-RTL will translate it back to EBCDIC.  It is XL C.
 I'm translating it to ASCII because the remainder of the application (~250
KLOC) came over from Windows.  There is no dependency on Windows API.
 However, there are ASCII dependencies.  Rather than do a port, it was
easier, faster, cheaper, safer, etc., to compile with ASCII and translate
the user provided strings to ASCII (ISO8859-1) or UNICODE depending on the
specific need.

The IBM XL C/C++ team did a GREAT jobs with ASCII compatibility.  :-)

The ultimate output file format is UNICODE and binary data.  In reality,
the application creates native excel spreadsheets in either .xls or .xlsx
format on z/OS.  It can be directly download to Windows in binary format
and opened by Excel.  No comma separated format.  Real Excel functions, etc.

There are lots of places where single-byte, multi-byte and
double-byte characters can be provided.  These are translated to UNICODE
(CCSID: 1200).



>
> z/OS C, or Dignus?  Hmmm... can Dignus programs interface to
> LE services for this sort of translation?
>
> 
> 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: Unix path name

[John Gilmore]

My point was that while 'member [name]' and 'alias' are useful terms
in an MVS environment they are without official warrant elsewhere.

The word 'pukka' has the usual Sanskrit==>Hindi==>British English
etymology.  It meant literally 'cooked' and now means legitimate or
high-quality exemplar of.

Cognates abound.  In Farsi, for example, rare meat is described as 'na
pochte', not cooked; and the American 'half-baked', used to describe
some ideas and etymologies, may reflect semantic contamination from
this source.

John Gilmore, Ashland, MA 01721 - USA

--
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

[Paul Gilmartin]

On Sun, 8 Apr 2012 12:55:54 -0700, Sam Siegel wrote:
>
>Actually it is C.  The intermediate buffer is used to allow the UNICODE
>service to translate to ASCII.  UNICODE services need to know how much data
>is being passed in.  The code runs POSIX(ON), XPLINK and is compiled the
>ASCII option.
>
And then the C RTL will further translate it to the "native" EBCDIC.
Many ASCII-centric systems treat UTF-8 as practically standard.
(But the filenames contain nonportable characters.)  Does the
caller pass you ASCII, presumed ISO8859-1, UTF-8, or other?
Will the files be shared (NFS?) or exported (pax?) to native ASCII
systems?

z/OS C, or Dignus?  Hmmm... can Dignus programs interface to
LE services for this sort of translation?


gil

--
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

[Sam Siegel]

On Sun, Apr 8, 2012 at 12:39 PM, Paul Gilmartin wrote:

> On Sun, 8 Apr 2012 11:15:55 -0700, Sam Siegel wrote:
> >
> >Paul - Thanks for the tips.  The code does not create any path segments.
> >
> You're welcome.
>
> >My goal here is to be able to point the user to the reference manuals so
> >they can determine what is appropriate for their use.  It is
> >their responsibility to allocate a buffer large enough to hold any
> >path/file name they create.  When they call my function, they provide the
> >address of the buffer and the number of bytes in the buffer.  A new buffer
> >is allocated (specified size + 2) and the specified number of bytes are
> >copied and a tailing x'' is appended.  My buffer  is passed to the
> >C/C++ runtime fopen function.  If the path/filename provided is invalid,
> >the open fails and the error is returned to the caller.
> >
> Sounds like assembler code insofar as it uses address/length rather
> than a null-terminated string.  So portability is less a concern.
>

Actually it is C.  The intermediate buffer is used to allow the UNICODE
service to translate to ASCII.  UNICODE services need to know how much data
is being passed in.  The code runs POSIX(ON), XPLINK and is compiled the
ASCII option.


>
> >It is
> >their responsibility to allocate a buffer large enough to hold any
> >path/file name they create.
>
> In which case, it depends not on a system limit nor on any
> limit in your code, but on how long a pathname the user
> intends to create.  From what I glean from POSIX and the
> z/390 C/C++ RTL, the limits are to be regarded as dynamic,
> and available from dynamic queries by:
>
>
> http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/edclb1b0/3.661
>3.661 pathconf() -- Determine configurable path name variables
>
> which sounds sort of circular: in order to ask how long a pathname
> is allowed, you must provide some sort of pathname (in the same
> filesystem?) as input.  The operant word is "configurable"; i.e.
> subject to change.
>
> The underlying Assembler callable service is:
>
>
> http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/bpxzb1b0/2.126
>2.126 pathconf (BPX1PCF, BPX4PCF)
>

Thanks ... I will look at both of these manuals.

>
> (Yes, when I first learned about this, I thought it was BS; PITA.)
>
> -- 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: Unix path name

[Paul Gilmartin]

On Sun, 8 Apr 2012 11:15:55 -0700, Sam Siegel wrote:
>
>Paul - Thanks for the tips.  The code does not create any path segments.
>
You're welcome.

>My goal here is to be able to point the user to the reference manuals so
>they can determine what is appropriate for their use.  It is
>their responsibility to allocate a buffer large enough to hold any
>path/file name they create.  When they call my function, they provide the
>address of the buffer and the number of bytes in the buffer.  A new buffer
>is allocated (specified size + 2) and the specified number of bytes are
>copied and a tailing x'' is appended.  My buffer  is passed to the
>C/C++ runtime fopen function.  If the path/filename provided is invalid,
>the open fails and the error is returned to the caller.
> 
Sounds like assembler code insofar as it uses address/length rather
than a null-terminated string.  So portability is less a concern.

>It is
>their responsibility to allocate a buffer large enough to hold any
>path/file name they create.

In which case, it depends not on a system limit nor on any
limit in your code, but on how long a pathname the user
intends to create.  From what I glean from POSIX and the
z/390 C/C++ RTL, the limits are to be regarded as dynamic,
and available from dynamic queries by:

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/edclb1b0/3.661
3.661 pathconf() -- Determine configurable path name variables

which sounds sort of circular: in order to ask how long a pathname
is allowed, you must provide some sort of pathname (in the same
filesystem?) as input.  The operant word is "configurable"; i.e.
subject to change.

The underlying Assembler callable service is:

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/bpxzb1b0/2.126
2.126 pathconf (BPX1PCF, BPX4PCF)

(Yes, when I first learned about this, I thought it was BS; PITA.)

-- gil

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

Re: Coding IEASYMxx

[Rob Schramm]

There is a pretty good description of Symbols, rules, substrings etc
in Chapter 2 of MVS Init and Tuning Reference.  Section titled "Using
system symbols in parmlib" ...  otherwise know as USSiP


Rob Schramm
Senior Systems Consultant
Imperium Group



On Sun, Apr 8, 2012 at 8:29 AM, Jake anderson  wrote:
> Thanks a lot for your precise explanation.
>
> On Sun, Apr 8, 2012 at 7:46 AM, retired mainframer > wrote:
>
>> :>: -Original Message-
>> :>: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
>> :>: Behalf Of Jake anderson
>> :>: Sent: Saturday, April 07, 2012 6:58 PM
>> :>: To: IBM-MAIN@bama.ua.edu
>> :>: Subject: Coding IEASYMxx
>> :>:
>> :>: Hello All,
>> :>:
>> :>: First of all apology for asking a very basic question and being
>> :>: ignorant.In
>> :>: our shop we have two sysres volumes MTSRS1, MTSRS2,MSTRS3 so during
>> :>: SYSRES
>> :>: cloning we adopt indirect cataloging. Also it is important to specify
>> :>: the
>> :>: symbolic parameter at IEASYMxx member. My only basic question is that
>> :>: will
>> :>: it be wise enough to code like below :
>> :>:
>> :>: SYMDEF(&SYSR2='MTSRS2')
>> :>: SYMDEF(&SYSR3='MTSRS3').
>>
>> If you code it like this, then when you have a second set of SYSRES
>> volumes,
>> say TSTRS1, TSTRS2, TSTRS3, &SYSR1 will resolve to TSTRS1 as you want but
>> &SYSR2 will still resolve to the MTSRS2, not TSTRS2.
>>
>> :>:
>> :>: I have referred the link
>> :>:
>> http://publib.boulder.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fco
>> :>: m.ibm.zos.r12.ieae200%2Fplnsym.htm
>> :>:  but I am not really able to understand the below coding when we more
>> :>: than
>> :>: 1 sysres volumes :
>> :>:
>> :>: :SYSDEF .
>> :>:
>> :>:        .
>> :>:        SYMDEF(&SYSR2='&SYSR1(1:3).RS2') /* second SYSRES logical
>> :>:                                                   extension */
>>
>> This code says set the value of &SYSR2 to the first three characters of
>> &SYSR1 followed by the characters RS2.  When you IPL from MTSRS1, the first
>> three characters of &SYSRS1 are MTS so &SYSRS2 resolves to MTSRS2.  And
>> when
>> you IPL from TSTRS1, the first three characters are TST so &SYSR2 will
>> resolve to TSTRS2.  This insures that &SYSRS1, &SYSRS2, and &SYSRS3 always
>> resolve to the three volumes that are part of a matched set.
>>
>> :>:        SYMDEF(&SYSR3='&SYSR1(1:3).RS3') /* third SYSRES logical
>> :>:                                                  extension  */"
>> :>:
>> :>:
>> :>: Could anyone please explain me about the above syntax. How to make use
>> :>: the of the above syntax reasonably.
>>
>> The only change you need to make to the above is to decide how many volumes
>> are involved.  My last system (1.11) had only two 3390-9s so I didn't
>> bother
>> with &SYSRS3.
>>
>> --
>> 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: Unix path name

[John Gilmore]

I like Paul Gilmartin's contribution.  It is marred only by a small
omissis that most readers will remedy for themselves without even
being aware that they are doing so.

The text

|  2) Maximum number of characters in a file in a directory

should be changed to something like

| 2) Maximum number of characters in a [member] NAME in a directory

In a z/OS environment the answer, 255, is enforced by the binder for
both member names and their aliases.[The term 'member' is not a
pukka UNIX one.  It is, however, used in z/OS MVS program management
user's guide and reference, V1.R12 , p. 106 and passim.]


John Gilmore, Ashland, MA 01721 - USA

--
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

[Sam Siegel]

On Sun, Apr 8, 2012 at 10:43 AM, Paul Gilmartin wrote:

> On Sun, 8 Apr 2012 09:55:46 -0600, Steve Comstock wrote:
>
> >On 4/8/2012 9:46 AM, Sam Siegel wrote:
> >> I'm trying to find the manual (by full name or number) that provides
> >> precise definitions about  pathnames (hfs and zfs) for the unix
> subsystem
> >> on zos.  Specifically, I'm interested in knowing the maximum length:
> >>
> >> 1) Entire path from '/' on down
> >> 2) Maximum number of characters in a file in a directory
> >>...
> >
> >1. 1023
> >
> >2. 255
> >
> This is probably in /usr/include/limits.h
>
> With some nasty associated facts that I learned when I was trying
> to write a command interface to realpath():
>
> o realpath() appears to provide no protection against buffer overrun.
>
> o By descending a directory hierarchy, one can create a pathname
>  far longer than that limit.
>
> o While many UNIX-like systems provide a definition of PATH_MAX
>  in /usr/include/limits.h, POSIX deprecates this, and USS does not
>  provide one.  IBM gives the rationale that the limit is filesystem-
>  dependent and code relying on it might become obsoleted by
>  new technology.
>
> o A very deep path can cause "rm -rf" to fail in violation of POSIX
>  spec with a "too many open files" error.
>

Paul - Thanks for the tips.  The code does not create any path segments.

My goal here is to be able to point the user to the reference manuals so
they can determine what is appropriate for their use.  It is
their responsibility to allocate a buffer large enough to hold any
path/file name they create.  When they call my function, they provide the
address of the buffer and the number of bytes in the buffer.  A new buffer
is allocated (specified size + 2) and the specified number of bytes are
copied and a tailing x'' is appended.  My buffer  is passed to the
C/C++ runtime fopen function.  If the path/filename provided is invalid,
the open fails and the error is returned to the caller.

Thanks,
Sam


>
> -- 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: Unix path name

[Paul Gilmartin]

On Sun, 8 Apr 2012 09:55:46 -0600, Steve Comstock wrote:

>On 4/8/2012 9:46 AM, Sam Siegel wrote:
>> I'm trying to find the manual (by full name or number) that provides
>> precise definitions about  pathnames (hfs and zfs) for the unix subsystem
>> on zos.  Specifically, I'm interested in knowing the maximum length:
>>
>> 1) Entire path from '/' on down
>> 2) Maximum number of characters in a file in a directory
>>...
>
>1. 1023
>
>2. 255
> 
This is probably in /usr/include/limits.h

With some nasty associated facts that I learned when I was trying
to write a command interface to realpath():

o realpath() appears to provide no protection against buffer overrun.

o By descending a directory hierarchy, one can create a pathname
  far longer than that limit.

o While many UNIX-like systems provide a definition of PATH_MAX
  in /usr/include/limits.h, POSIX deprecates this, and USS does not
  provide one.  IBM gives the rationale that the limit is filesystem-
  dependent and code relying on it might become obsoleted by
  new technology.

o A very deep path can cause "rm -rf" to fail in violation of POSIX
  spec with a "too many open files" error.

-- gil

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

Negotiating

[Gabe Goldberg]

How to Negotiate Tech Pay
http://h30565.www3.hp.com/t5/Feature-Articles/How-to-Negotiate-Tech-Pay/ba-p/2508 



--
Gabriel Goldberg, Computers and Publishing, Inc.   g...@gabegold.com
3401 Silver Maple Place, Falls Church, VA 22042   (703) 204-0433
LinkedIn: http://www.linkedin.com/in/gabegoldTwitter: GabeG0

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

Re: Oracle DataGuard on Linux on z

[Mark Post]

>>> On 4/8/2012 at 05:13 AM, Mikael Wargh  wrote: 
> We're planning to run Oracle EE database with Data Guard option on Linux on 
> system z. So far everything seems doable, but we found some net presentation 
> telling that the two instances (active-passive) has to be exactly on same 
> software level and on a same type of hardware (chipset etc) to work properly. 
> Now we're wondering if this will work on z196 (active database) and z10BC 
> (passive replication database) combination.

That should be just fine, but you might get a more definitive answer asking 
this question on the linux-390 mailing list.  Damian Gallagher from Oracle 
hangs out there, and he is very knowledgeable about Oracle running on Linux for 
System z.

> Isn't z/VM same from Linux point 
> of view regardless of z hardware where it's running? 

No.  z/VM doesn't "lie" about what hardware you're on, it just makes it 
shareable among many guests.


Mark Post

--
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

[Sam Siegel]

On Sun, Apr 8, 2012 at 8:55 AM, Steve Comstock wrote:

> On 4/8/2012 9:46 AM, Sam Siegel wrote:
>
>> I'm trying to find the manual (by full name or number) that provides
>> precise definitions about  pathnames (hfs and zfs) for the unix subsystem
>> on zos.  Specifically, I'm interested in knowing the maximum length:
>>
>> 1) Entire path from '/' on down
>> 2) Maximum number of characters in a file in a directory
>> 3) Which characters are valid for a file name.
>>
>>
>>
>> Thanks,
>> Sam
>>
>
> 1. 1023
>
> 2. 255
>
> 3. a-z, A-Z, 0-9, period (.), underscore ( _ ), hyphen ( - )
>   are allowed for 'portable' file names; some other characters
>   are allowed if you don't care about portability, but I think
>   you are asking for trouble
>
> Check out the UNIX System Services User's Guide (chapters 16 and 17)
>

Steve - Thanks for the quick answer.

Sam

>
>
> --
>
> 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
>

--
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

[Steve Comstock]

On 4/8/2012 9:46 AM, Sam Siegel wrote:

I'm trying to find the manual (by full name or number) that provides
precise definitions about  pathnames (hfs and zfs) for the unix subsystem
on zos.  Specifically, I'm interested in knowing the maximum length:

1) Entire path from '/' on down
2) Maximum number of characters in a file in a directory
3) Which characters are valid for a file name.



Thanks,
Sam


1. 1023

2. 255

3. a-z, A-Z, 0-9, period (.), underscore ( _ ), hyphen ( - )
   are allowed for 'portable' file names; some other characters
   are allowed if you don't care about portability, but I think
   you are asking for trouble

Check out the UNIX System Services User's Guide (chapters 16 and 17)


--

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

Unix path name

[Sam Siegel]

I'm trying to find the manual (by full name or number) that provides
precise definitions about  pathnames (hfs and zfs) for the unix subsystem
on zos.  Specifically, I'm interested in knowing the maximum length:

1) Entire path from '/' on down
2) Maximum number of characters in a file in a directory
3) Which characters are valid for a file name.



Thanks,
Sam

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

Re: Coding IEASYMxx

[Jake anderson]

Thanks a lot for your precise explanation.

On Sun, Apr 8, 2012 at 7:46 AM, retired mainframer  wrote:

> :>: -Original Message-
> :>: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
> :>: Behalf Of Jake anderson
> :>: Sent: Saturday, April 07, 2012 6:58 PM
> :>: To: IBM-MAIN@bama.ua.edu
> :>: Subject: Coding IEASYMxx
> :>:
> :>: Hello All,
> :>:
> :>: First of all apology for asking a very basic question and being
> :>: ignorant.In
> :>: our shop we have two sysres volumes MTSRS1, MTSRS2,MSTRS3 so during
> :>: SYSRES
> :>: cloning we adopt indirect cataloging. Also it is important to specify
> :>: the
> :>: symbolic parameter at IEASYMxx member. My only basic question is that
> :>: will
> :>: it be wise enough to code like below :
> :>:
> :>: SYMDEF(&SYSR2='MTSRS2')
> :>: SYMDEF(&SYSR3='MTSRS3').
>
> If you code it like this, then when you have a second set of SYSRES
> volumes,
> say TSTRS1, TSTRS2, TSTRS3, &SYSR1 will resolve to TSTRS1 as you want but
> &SYSR2 will still resolve to the MTSRS2, not TSTRS2.
>
> :>:
> :>: I have referred the link
> :>:
> http://publib.boulder.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fco
> :>: m.ibm.zos.r12.ieae200%2Fplnsym.htm
> :>:  but I am not really able to understand the below coding when we more
> :>: than
> :>: 1 sysres volumes :
> :>:
> :>: :SYSDEF .
> :>:
> :>:.
> :>:SYMDEF(&SYSR2='&SYSR1(1:3).RS2') /* second SYSRES logical
> :>:   extension */
>
> This code says set the value of &SYSR2 to the first three characters of
> &SYSR1 followed by the characters RS2.  When you IPL from MTSRS1, the first
> three characters of &SYSRS1 are MTS so &SYSRS2 resolves to MTSRS2.  And
> when
> you IPL from TSTRS1, the first three characters are TST so &SYSR2 will
> resolve to TSTRS2.  This insures that &SYSRS1, &SYSRS2, and &SYSRS3 always
> resolve to the three volumes that are part of a matched set.
>
> :>:SYMDEF(&SYSR3='&SYSR1(1:3).RS3') /* third SYSRES logical
> :>:  extension  */"
> :>:
> :>:
> :>: Could anyone please explain me about the above syntax. How to make use
> :>: the of the above syntax reasonably.
>
> The only change you need to make to the above is to decide how many volumes
> are involved.  My last system (1.11) had only two 3390-9s so I didn't
> bother
> with &SYSRS3.
>
> --
> 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

Oracle DataGuard on Linux on z

[Mikael Wargh]

Hello,
We're planning to run Oracle EE database with Data Guard option on Linux on 
system z. So far everything seems doable, but we found some net presentation 
telling that the two instances (active-passive) has to be exactly on same 
software level and on a same type of hardware (chipset etc) to work properly. 
Now we're wondering if this will work on z196 (active database) and z10BC 
(passive replication database) combination. Isn't z/VM same from Linux point of 
view regardless of z hardware where it's running? 

Best regards,
Mikael Wargh
Tieto, Finland  

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