I used TSO all my life without TN3270, until 2 years ago.
Kees.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of R.S.
Sent: Sunday, March 16, 2014 10:56
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Can we logon to TSO witout having
On 16/03/2014 2:53 AM, Paul Gilmartin wrote:
CA-1's support of non-number tape serials was difficult (needed some sort
of mapping exit as I recall).
Yes, because management got thousands of tape labels printed for the new
MVS system before the sysprogs heard about it.
Details? Does the exit
VTAM is the pre-req, not TN3270.
It depends on the method of *TERMINAL* attachment. If via VTAM, TN3270 is not
needed for anything/
TN3270 is merely TCPIP on one side and SNA on the other...
HTH,
snip
We are running z/os 1.11 and had a strange issue on one of our systems today .
Our shop
W dniu 2014-03-17 09:24, Vernooij, CP (SPLXM) - KLM pisze:
I used TSO all my life without TN3270, until 2 years ago.
1. Before z/OS 1.9 (AFAIR) separate started task for TN3270 was
optional. So it was enough to start TCPIP. Of course non-IP connections
still work without TN3270 and without
Shmuel has this fully correct
This thread was to some extent confusing LLA managing of the directory
entry with LLA managing of the module. They are often the same. Not
always.
When LLA is active, BLDL will always ask LLA if it has the directory entry
cached. If it does, LLA will return it to
There is no guarantee that status has *ever* been saved for any work unit.
Thus it is not predictable whether the data in the IHSA is valid or not.
It's also unlikely that the ASSBIHSA of the lock holder is the right IHSA
for the local lock (unless you know that it's the LOCAL lock, not a CML).
1. that's what I meant: you only need tn3270 if you want to do TSO from IP
devices. And 2 years ago, someone decided that I needed that.
2. well, all my life is not exactly correct, the first 18 years I managed
without. From then at school we had a BASIC based HP2000 system, with Time
Sharing
On Mon, 17 Mar 2014 21:53:19 +1100, Greg Price wrote:
The reason for the non-numeric characters?
Management thought it might be nice if the first two characters were
alphabetics forming a common abbreviation of the corporation name.
SMP/E product tapes are 2 letters and 4 digits, aren't they?
You've gotten some good feedback on RACF-L, however I'll comment here, because
I think this is more appropriate for IBM-MAIN.
(I do disagree with Russ's suggestion to write down the key material though.
There is no point in paying big bucks for the secure key technology and then
storing the
On Mon, 17 Mar 2014 13:12:05 +, Staller, Allan wrote:
VTAM is the pre-req, not TN3270.
It depends on the method of *TERMINAL* attachment. If via VTAM, TN3270 is not
needed for anything/
TN3270 is merely TCPIP on one side and SNA on the other...
VTAM? SNA? I don't know the distinction.
In
cc42e2f56d60f24fb8a6bcc639d1d9632c665...@samtcasxmb13.usa.dce.usps.gov,
on 03/14/2014
at 09:01 PM, Hansen, Dave L - Eagan, MN dave.l.han...@usps.gov
said:
Sorry for the delay. We don't have ISRSUPC in the SYS1.LPALIB. LINK
worked, but I didn't figure out the error.
I gave you the wrong
On Mon, Mar 17, 2014 at 9:19 AM, Paul Gilmartin paulgboul...@aim.comwrote:
On Mon, 17 Mar 2014 13:12:05 +, Staller, Allan wrote:
VTAM is the pre-req, not TN3270.
It depends on the method of *TERMINAL* attachment. If via VTAM, TN3270 is
not needed for anything/
TN3270 is merely TCPIP
In
CALt2WMYeFwyiquHBT4W4Ge_9NgyzS5a_YuFEbsY5Ro-=p7f...@mail.gmail.com,
on 03/16/2014
at 08:29 AM, baby eklavya baby.ekla...@gmail.com said:
I always thought that TN3270 was pre-requisite for anybody to logon
via TSO
Why? The TN3270 server is only relevant to someone using the TN3270
protocol.
In
CAAJSdjhYGYLdfmP94DHw2SQuCUTYDG9devhC+qh=S=dyey7...@mail.gmail.com,
on 03/15/2014
at 11:17 PM, John McKown john.archie.mck...@gmail.com said:
Last, and least, would be if you actually have a local non-SNA 3270
Local SNA will work just as well for TSO and SMCS consoles.
--
Shmuel
W dniu 2014-03-17 15:19, Paul Gilmartin pisze:
On Mon, 17 Mar 2014 13:12:05 +, Staller, Allan wrote:
VTAM is the pre-req, not TN3270.
It depends on the method of *TERMINAL* attachment. If via VTAM, TN3270 is not
needed for anything/
TN3270 is merely TCPIP on one side and SNA on the
Rephrasing:
TN3270 is merely TCPIP on one side and VTAM/SNA on the other...
TN3270 receives TCPIP requests on one side and translates to VTAM/SNA on the
other. (BTW, VTAM also supports BISYNC).
Other points:
Once you have the READY prompt you *ARE* logged on to TSO.
TELNET (dnsname or
On Mon, Mar 17, 2014 at 9:36 AM, Shmuel Metz (Seymour J.)
shmuel+ibm-m...@patriot.net wrote:
In
CAAJSdjhYGYLdfmP94DHw2SQuCUTYDG9devhC+qh=S=dyey7...@mail.gmail.com,
on 03/15/2014
at 11:17 PM, John McKown john.archie.mck...@gmail.com said:
Last, and least, would be if you actually have a
Regarding:
Once you have the READY prompt you *ARE* logged on to TSO.
I think this points out a misconception about mainframes from people that are
used to work with *nix systems.
The question in this thread was: (I always thought that TN3270 was
pre-requisite for anybody) to logon via TSO
I
In
ce3ffbb7e42033469ef752a1d8a19ba10759f...@kl1221tc.cs.ad.klmcorp.net,
on 03/17/2014
at 02:39 PM, Vernooij, CP (SPLXM) - KLM kees.verno...@klm.com
said:
1. that's what I meant: you only need tn3270 if you want to do TSO
from IP devices. And 2 years ago, someone decided that I needed that.
On 3/17/2014 10:34 AM, R.S. wrote:
Both network and local terminal won't work without VTAM. Also
IP-attached terminals do require VTAM.
Local terminals do not need VTAM, if you're willing to do the work to
mimic normal SNA packets with EXCP (or variant). While it's not for the
faint-hearted,
paulgboul...@aim.com (Paul Gilmartin) writes:
VTAM? SNA? I don't know the distinction.
... as an aside ... other divisions used to try and build SNA devices to
the SNA protocol specs ... and they wouldn't work with VTAM ... it turns
out that the only real definition for SNA is what VTAM would
kees.verno...@klm.com (Vernooij, CP - KLM , SPLXM) writes:
The big difference to notice is:
You logon to a *nix system via Telnet or so.
You don't logon to a mainframe. You logon to an application on a
mainframe. So, you don't logon *via* TSO, you logon *to* TSO.
re:
re:
http://www.garlic.com/~lynn/2014d.html#50 Can we logon to TSO witout having
TN3270 up ?
http://www.garlic.com/~lynn/2014d.html#51 Can we logon to TSO witout having
TN3270 up ?
oops, left out
The Evolution of CICS: CICS and Multiprocessor Exploitation (2004)
On Mon, 17 Mar 2014 10:34:05 -0400, Shmuel Metz (Seymour J.) wrote:
I am not sure what LINKPGM would do for me.
It would start the parameter with a halfword length field instead of
passing the length as a separate parameter.
No, and no. LINKMVS prefixes the programmer-supplied parameter
with
John McKown writes:
There is a thread over on TSO-REXX about splitting up a string into
volume serials. This has occasioned two questions to me.
1) Has anybody ever had a VOLSER which was not exactly 6 non-blank
characters for a regularly used volume? Especially any trailing blanks?
RACF
On 2014-03-17, at 08:44, Vernooij, CP (SPLXM) - KLM wrote:
The big difference to notice is:
You logon to a *nix system via Telnet or so.
The *nix argot is login, not logon. I wonder if that
arises from the difference you note?
You don't logon to a mainframe. You logon to an application
Shmuel Metz (Seymour J.) wrote:
I believe John wrote 'white-color'. :-D
That was the point.
Ok.
A new typo! :-D
Mandatory spilling error.
Hehehe. :-D :-D :-D
I like spelling errors on purposes, sometimes you see intended or unintended
puns. ;-D
Groete / Greetings
Elardus Engelbrecht
Hello list,
Someone can tell me the relevant differences between the MVS and z / OS systems?
Thank you
Helio Jose da Silva
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
On Mon, 17 Mar 2014 17:07:14 +, Helio Jose Da Silva wrote:
Someone can tell me the relevant differences between the MVS and z / OS
systems?
Well, z/OS runs on zSeries; MVS doesn't.
But MVS is often used as generic (IBM jargon would say esoteric),
inclusive of MVS, MVS/370, MVS/XA, MVS/ESA,
Peter Relson wrote:
Shmuel has this fully correct
Indeed. I'm not surprised. ;-D
This thread was to some extent confusing LLA managing of the directory entry
with LLA managing of the module. They are often the same. Not always.
Agreed, this is why locating that errant module is a journey a la
https://groups.google.com/forum/#!topic/bit.listserv.tsorexx/JM3Vx1Vkw2w
https://publib.boulder.ibm.com/infocenter/zos/basics/index.jsp?topic=/com.ibm.zos.zconcepts/zconcepts_102.htm
Kolusu
IBM Mainframe Discussion List IBM-MAIN@listserv.ua.edu wrote on
03/17/2014 10:07:14 AM:
From: Helio
On Mon, 17 Mar 2014 17:07:14 + Helio Jose Da Silva
helio.si...@rural.com.br wrote:
:Someone can tell me the relevant differences between the MVS and z / OS
systems?
Depends on the context. What do you mean by MVS and z/OS? Which versions?
--
Binyamin Dissen bdis...@dissensoftware.com
Thanks so
The ONLY to know if the module is LLA managed is if the exit(s) are invoked
ILX1 or 2
Sent from my iPhone
On Mar 17, 2014, at 9:26 AM, Peter Relson rel...@us.ibm.com wrote:
Shmuel has this fully correct
This thread was to some extent confusing LLA managing of the directory
Paul Gilmartin wrote:
Well, z/OS runs on zSeries; MVS doesn't.
More accurately, z/OS ran on zSeries, now runs on System z and zEnterprise. The
zSeries name was obsolete as of 2005 or so.
Yes, I'm being pedantic, but in this context especially it seems appropriate.
...phsiii
W dniu 2014-03-17 16:03, Gerhard Postpischil pisze:
On 3/17/2014 10:34 AM, R.S. wrote:
Both network and local terminal won't work without VTAM. Also
IP-attached terminals do require VTAM.
Local terminals do not need VTAM, if you're willing to do the work to
mimic normal SNA packets with EXCP
Has anyone migrated to Enterprise Cobol 5.1 from earlier enterprise releases?
I guess that I was really surprised that it will not run on z/OS 1.12 and that
the executables can only reside in a PDSE. Am I understanding this correctly?
Sharon Lopez
z/OS Systems Programmer
N.C. Office of
Hi,
If my memory serves me right, back in the 1970s there was OS/MFT, OS/MVT,
OS/VS1, and OS/VS2.
OS/VS2 morphed to OS/SVS and then OS/MVS(? Or maybe just MVS) starting in
the 1980s.
I worked on OS/VS1 Rel 7 back in the 79-80 time frame. I didn¹t get back
to MVS till the mid 90¹s.
Gary
Gary
How did IBM's lawyers define give, client, data, and government?
Bill Fairchild
- Original Message -
From: Ed Gould edgould1...@comcast.net
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Sunday, March 16, 2014 11:21:20 AM
Subject: IBM says it has not given client data to the U.S. government
Hi Sharon,
We are an ISV and I am in the early stages of playing with this. From what
I can tell, the PDSE is a requirement. Maybe someone else will comment. I
have compiled a couple of DB2 V10 programs that use CAF and that were
previous compiled on 4.2 using the DB2 V10 Preprocessor as well
Sharon,
We just had a big discussion on IBM Main on this topic. You should be able
to search the archives and find the various threads. According to Tom Ross
IBM L3 Cobol, - PDS/E is the requirement.
You may wish to see if there have been any SHARE presentations or Migration
PDFs from Marna
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Elardus Engelbrecht
Shmuel Metz (Seymour J.) wrote:
I believe John wrote 'white-color'. :-D
That was the point.
Ok.
A new typo! :-D
Mandatory spilling error.
Hehehe. :-D :-D :-D
I like spelling errors
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Helio Jose Da Silva
Hello list,
Someone can tell me the relevant differences between the MVS and z / OS
systems?
MVS is the kernel; z/OS is the whole package.
-jc-
Close. OS/VS2 was released having been already pre-morphed into SVS and MVS.
SVS was first called OS/VS2 Release 1, was first available in 1974, and that's
when I worked with it. MVS was first called OS/VS2 Release 2, was first
available slightly later (1975, I think), but I didn't begin
gary.shimin...@doit.nh.gov (Shiminsky, Gary) writes:
If my memory serves me right, back in the 1970s there was OS/MFT, OS/MVT,
OS/VS1, and OS/VS2.
OS/VS2 morphed to OS/SVS and then OS/MVS(? Or maybe just MVS) starting in
the 1980s.
OS/VS2 started out as single virtual address space (svs ...
On 17 March 2014 13:51, John Eells ee...@us.ibm.com wrote:
MVS was the prior name of what has become z/OS. What was started out as MVS
in 1974 was renamed to:
[...]
Although the name MVS was around in 1974, IBM chose, for the usual
marketing reasons of the day, to sell it as OS/VS2 Release 2,
Mark,
I was just at SHARE, and was talking to Greg Boyd from IBM. He told me about
your topic on IBM-MAIN (this is the first time I've been on here). I'm also
interested in getting the AES CTR cipher support added to ICSF. Please let me
know how I can get my name added to the list! I discussed
On 03/17/14 15:11, Don Brooke wrote:
Mark,
I was just at SHARE, and was talking to Greg Boyd from IBM. He told me about
your topic on IBM-MAIN (this is the first time I've been on here). I'm also
interested in getting the AES CTR cipher support added to ICSF. Please let me
know how I can get
Both of your statements are correct.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Lopez, Sharon
Sent: Monday, March 17, 2014 2:12 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Enterprise Cobol 5.1
Has anyone migrated to Enterprise
I haven't seen anything more on this yet but I'm digested daily causing
delays...
Dave - re ISRS010W: I haven't tested or researched but is it, perhaps, a
positional parm problem? In my SuperC batch step, I use
PARM=('DELTAL','FILECMP','',''). Hmmm... perhaps it's a lack of parms ie. 4
are
You do understand it correctly - and there's more. It has a hardware
requirement of z990/z890; you cannot run OS/VS COBOL in the same enclave as
COBOL 5.1; it is recommended to have a 200M region size to compile; and when
you do, you can specify the architecture level at compile time in
I've asked our Account team to add us to the interested parties list of the MR's
Jerry Whitteridge
Lead Systems Programmer
Safeway Inc.
925 951 4184
If you feel in control
you just aren't going fast enough.
-Original Message-
From: IBM Mainframe Discussion List
John:
Yes, it does, Its like C with longnames..
Regards,
Scott
From: John Abell
Sent: Monday, March 17, 2014 2:21 PM
To: IBM Mainframe Discussion List
Hi Sharon,
We are an ISV and I am in the early stages of playing with this. From what
I can tell, the PDSE is a
Mark,
I was thinking about whether there are good temporary workarounds for your
problem.
First attempt:
I was thinking that you could maybe use Match for the specific client
host that needs it and then in sshd_config add aes_ctr to the Ciphers for
that client and in zos_sshd_config change
VM was around in 1967. Iirc.
-
-teD
-
Original Message
From: DASDBILL2
Sent: Monday, March 17, 2014 15:09
To: IBM-MAIN@LISTSERV.UA.EDU
Reply To: IBM Mainframe Discussion List
Subject: Re: Difference between MVS and z / OS systems
Close. OS/VS2 was released having been already pre-morphed
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Jousma, David
Both of your statements are correct.
Not only that, but you also need PTFs for four LE APARs and three Binder APARs.
But you can INSTALL COBOL 5.1 on z/OS 1.12 (according to the Program
Directory).
I would like to interrupt this reminiscent thread with a quiz:
How to you replace MVS with z/OS ?
Answer:
the MVSt instruction :-)
Kirk Wolf
Dovetailed Technologies
http://dovetail.com
--
For IBM-MAIN subscribe / signoff
All:
I don't think its just Cobol, I ran into with C with longnames. Had to have a
PDSE allocated.
Regards,
Scott
From: Jousma, David
Sent: Monday, March 17, 2014 2:27 PM
To: IBM Mainframe Discussion List
Both of your statements are correct.
-Original Message-
VM was called CP67 in 1967. It became VM several years later. CP67 would only
run on a S/360 model 67. VM would run on any S/370 system with paging
architecture.
Bill Fairchild
- Original Message -
From: Ted MacNEIL eamacn...@yahoo.ca
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Monday,
t...@harminc.net (Tony Harminc) writes:
These were re-integrated only with the OS/390 bundling. I doubt any
one present -- even Lynn Wheeler -- knows all the politics behind all
these changes.
re:
http://www.garlic.com/~lynn/2014d.html#54 Difference between MVS and z / OS
systems
OS/390 ...
dasdbi...@comcast.net (DASDBILL2) writes:
Close. OS/VS2 was released having been already pre-morphed into SVS
and MVS. SVS was first called OS/VS2 Release 1, was first available
in 1974, and that's when I worked with it. MVS was first called
OS/VS2 Release 2, was first available slightly
I think your dates are wrong.
VM was CP67 released in guess what year?
MVS was first released in 1974.
SVS was OS/VS1 and MVS was OS/VS2, IIRC.
I'm sure, if I'm wrong, somebody'll correct me.
-
-teD
-
Original Message
From: DASDBILL2
Sent: Monday, March 17, 2014 15:09
To:
Gil,
While the exits are not needed if the volser has alpha/numeric on the left and
all numerics on the right; the exits are still available. And we have worked up
the 01-01 ranges, as well as the base-16 ranges. The client wanting
base 36 (0-Z) decided against it after seeing how
On Mar 17, 2014, at 9:35 PM, Ted MacNEIL wrote:
I think your dates are wrong.
VM was CP67 released in guess what year?
MVS was first released in 1974.
SVS was OS/VS1 and MVS was OS/VS2, IIRC.
I'm sure, if I'm wrong, somebody'll correct me.
-
-teD
Ted:
SVS was *NOT* os/vs1 many many reasons
63 matches
Mail list logo
