date:20210106

Re: Progam directory AD/Cycle C/370

2021-01-06 Thread Clark Morris

[Default] On 6 Jan 2021 11:34:45 -0800, in bit.listserv.ibm-main
r.skoru...@bremultibank.com.pl (R.S.) wrote:

>W dniu 06.01.2021 o 09:19, Tom Ross pisze:
>> snip
>
>Tom,
>Thank you for the table.
>Actually I found some table in COBOL Migration Guide manual
>https://www.ibm.com/support/knowledgecenter/hu/SS6SG3_6.3.0/migrate/igympreab2.html
> 
>
>but your table is more detailed - I mean dates.
>To make things more complex your table lack of third dimension ;-) I 
>mean MLC vs VUE flavours, which is technically irrelevant, but introduce 
>new PIDs (program numbers).
>And this is good you preserved version numbering - that simplifies 
>identification.
>
>Funny fact: I vaguely remember 1999 and some official announcements 
>about OS/VS COBOL withdrawals which were obscure and incomprehensible 
>for me at the time. ;-)
>
>BTW: This is pure curiosity, however was there any COBOL life on earth 
>before 1974? I'm sure it was some COBOL, but it was really looong time 
>ago. Maybe different product packaging and numbering, etc.

I used COBOL (19)61 and COBOL (19)63 on an RCA 301 in the 1963 - 1965
timeframe, then started with COBOL D on a 32K 360/30 with DOS
progressing to COBOL F on either the 64K mod 30 or 128K mod 40.  I
think I have used most versions on OS360 through MVS/XA in the time
frame 1977 - 1991 plus VS COBOL II release 1.4 (a major improvement)
followed by either COBOL 370 or COBOL for MVS and VM.

Clark Morris 
>
>Regards

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

Re: Progam directory AD/Cycle C/370

2021-01-06 Thread Seymour J Metz

> entire history

No, it's missing a decade.

360S-C0-503 COBOL (E)

360S-CB-524 COBOL (F)

360S-CB-545 COBOL (U)

5734-CB1 OS FULL AMERICAN NATIONAL STANDARD COBOL Versions 1-3

5734-CB2 OS FULL AMERICAN NATIONAL STANDARD COBOL Version 4, 5



--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Tom 
Ross [tmr...@stlvm20.vnet.ibm.com]
Sent: Wednesday, January 6, 2021 3:19 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Progam directory AD/Cycle C/370

>BTW: Is there description/list of COBOL versions anywhere?

 I don't know, but I have lists!  Here is the entire history, no names, just
 product ids, but you can kind of tell which is which by the dates.
OS/VS COBOL, VS COBOL II, etc etc
Note: You need fixed-width caharacters to view this table:

 Program  Marketing   Service
 Number   VRM Announced   Available   Withdrawn   Discontinued

 5740-CB1 1.02.4  1974/05/13  1974/09/23  1992/12/18  1999/12/31

 5668-958 1.03.0  1988/09/13  1988/12/16  1997/06/30  1996/06/30
 5668-958 1.03.1  1989/09/19  1989/12/29  1997/06/30  1996/06/30
 5668-958 1.03.2  1990/09/05  1990/12/28  1997/06/30  1996/06/30
 5668-958 1.04.0  1992/09/15  1993/03/12  1997/06/30  2001/03/31

 5688-197 1.01.0  1991/09/11  1991/12/20  2000/09/06  1997/09/30
 5688-197 1.02.0  1995/10/24  1995/10/27  2000/09/06  2001/12/31

 5648-A25 2.01.0  1997/05/06  1997/05/23  2000/09/29  2004/12/31
 5648-A25 2.02.0  2000/09/26  2000/09/29  2002/12/31  2004/12/31

 5655-G53 3.01.0  2001/11/27  2001/11/30  2002/09/27  2004/04/04
 5655-G53 3.02.0  2002/08/20  2002/09/27  2004/02/27  2005/10/03
 5655-G53 3.03.0  2004/02/17  2004/02/27  2005/07/01  2007/04/30
 5655-G53 3.04.0  2005/06/21  2005/07/01  2008/09/29  2015/04/30

 5655-S71 4.01.0  2007/12/11  2007/12/14  2009/08/25  2014/04/30
 5655-S71 4.02.0  2009/08/25  2009/08/28  2018/03/12  2021/09/30

 5655-W32 05.01.00 2013/04/23 2013/06/21  2015/01/14  2020/04/30
 5655-W32 05.02.00 2015/01/14 2015/02/27  2017/09/11  2020/04/30

 5655-EC6 06.01.00 2016/02/16 2016/03/18  2020/03/09  -
 5655-EC6 06.02.00 2017/07/17 2017/09/08  2020/03/09  -
 5655-EC6 06.03.00 2019/09/03 2019/09/06  -   -

Cheers,
TomR  >> COBOL is the Language of the Future! <<

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

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

Re: Progam directory AD/Cycle C/370

2021-01-06 Thread Mike Schwab

The Turnkey collections have the 1968 compilers adapted to MVS.

On Wed, Jan 6, 2021 at 1:34 PM R.S.  wrote:
>
> W dniu 06.01.2021 o 09:19, Tom Ross pisze:
> >> BTW: Is there description/list of COBOL versions anywhere?
> >   I don't know, but I have lists!  Here is the entire history, no names, 
> > just
> >   product ids, but you can kind of tell which is which by the dates.
> > OS/VS COBOL, VS COBOL II, etc etc
> > Note: You need fixed-width caharacters to view this table:
> >
> >   Program  Marketing   Service
> >   Number   VRM Announced   Available   Withdrawn   Discontinued
> >
> >   5740-CB1 1.02.4  1974/05/13  1974/09/23  1992/12/18  1999/12/31
> >
> >   5668-958 1.03.0  1988/09/13  1988/12/16  1997/06/30  1996/06/30
> >   5668-958 1.03.1  1989/09/19  1989/12/29  1997/06/30  1996/06/30
> >   5668-958 1.03.2  1990/09/05  1990/12/28  1997/06/30  1996/06/30
> >   5668-958 1.04.0  1992/09/15  1993/03/12  1997/06/30  2001/03/31
> >
> >   5688-197 1.01.0  1991/09/11  1991/12/20  2000/09/06  1997/09/30
> >   5688-197 1.02.0  1995/10/24  1995/10/27  2000/09/06  2001/12/31
> >
> >   5648-A25 2.01.0  1997/05/06  1997/05/23  2000/09/29  2004/12/31
> >   5648-A25 2.02.0  2000/09/26  2000/09/29  2002/12/31  2004/12/31
> >
> >   5655-G53 3.01.0  2001/11/27  2001/11/30  2002/09/27  2004/04/04
> >   5655-G53 3.02.0  2002/08/20  2002/09/27  2004/02/27  2005/10/03
> >   5655-G53 3.03.0  2004/02/17  2004/02/27  2005/07/01  2007/04/30
> >   5655-G53 3.04.0  2005/06/21  2005/07/01  2008/09/29  2015/04/30
> >
> >   5655-S71 4.01.0  2007/12/11  2007/12/14  2009/08/25  2014/04/30
> >   5655-S71 4.02.0  2009/08/25  2009/08/28  2018/03/12  2021/09/30
> >
> >   5655-W32 05.01.00 2013/04/23 2013/06/21  2015/01/14  2020/04/30
> >   5655-W32 05.02.00 2015/01/14 2015/02/27  2017/09/11  2020/04/30
> >
> >   5655-EC6 06.01.00 2016/02/16 2016/03/18  2020/03/09  -
> >   5655-EC6 06.02.00 2017/07/17 2017/09/08  2020/03/09  -
> >   5655-EC6 06.03.00 2019/09/03 2019/09/06  -   -
> >
> > Cheers,
> > TomR  >> COBOL is the Language of the Future! <<
> >
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> > .
>
>
> Tom,
> Thank you for the table.
> Actually I found some table in COBOL Migration Guide manual
> https://www.ibm.com/support/knowledgecenter/hu/SS6SG3_6.3.0/migrate/igympreab2.html
>
> but your table is more detailed - I mean dates.
> To make things more complex your table lack of third dimension ;-) I
> mean MLC vs VUE flavours, which is technically irrelevant, but introduce
> new PIDs (program numbers).
> And this is good you preserved version numbering - that simplifies
> identification.
>
> Funny fact: I vaguely remember 1999 and some official announcements
> about OS/VS COBOL withdrawals which were obscure and incomprehensible
> for me at the time. ;-)
>
> BTW: This is pure curiosity, however was there any COBOL life on earth
> before 1974? I'm sure it was some COBOL, but it was really looong time
> ago. Maybe different product packaging and numbering, etc.
>
> Regards
> --
> Radoslaw Skorupka
> Lodz, Poland
>
>
>
>
>
> ==
>
> Jeśli nie jesteś adresatem tej wiadomości:
>
> - powiadom nas o tym w mailu zwrotnym (dziękujemy!),
> - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub 
> zapisałeś na dysku).
> Wiadomość ta może zawierać chronione prawem informacje, które może 
> wykorzystać tylko adresat. Przypominamy, że każdy, kto rozpowszechnia 
> (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza 
> prawo i może podlegać karze.
>
> mBank S.A. z siedzibą w Warszawie, ul. Prosta 18, 00-850 
> Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. 
> Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, 
> NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 
> 01.01.2020 r. wynosi 169.401.468 złotych.
>
> Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
> prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
> wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
> działalnością bankową.
> Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz 
> w Pakietach RODO (w wersji polskiej i angielskiej), które są na 
> www.mbank.pl/rodo
>
>
> If you are not the addressee of this message:
>
> - let us know by replying to this e-mail (thank you!),
> - delete this message permanently (including all the copies which you have 
> printed out or saved).
> This message may contain legally protected information, which may be used 
> exclusively by the addressee.Please be reminded that anyone who disseminates 
> (copies, distributes) this message or takes any

Re: Progam directory AD/Cycle C/370

2021-01-06 Thread Charles Mills

I came to the platform in 1968 and COBOL definitely beat me to it.

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of R.S.
Sent: Wednesday, January 6, 2021 11:35 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Progam directory AD/Cycle C/370

W dniu 06.01.2021 o 09:19, Tom Ross pisze:
>> BTW: Is there description/list of COBOL versions anywhere?
>   I don't know, but I have lists!  Here is the entire history, no names,
just
>   product ids, but you can kind of tell which is which by the dates.
> OS/VS COBOL, VS COBOL II, etc etc
> Note: You need fixed-width caharacters to view this table:
>
>   Program  Marketing   Service
>   Number   VRM Announced   Available   Withdrawn   Discontinued
>
>   5740-CB1 1.02.4  1974/05/13  1974/09/23  1992/12/18  1999/12/31
>
>   5668-958 1.03.0  1988/09/13  1988/12/16  1997/06/30  1996/06/30
>   5668-958 1.03.1  1989/09/19  1989/12/29  1997/06/30  1996/06/30
>   5668-958 1.03.2  1990/09/05  1990/12/28  1997/06/30  1996/06/30
>   5668-958 1.04.0  1992/09/15  1993/03/12  1997/06/30  2001/03/31
>
>   5688-197 1.01.0  1991/09/11  1991/12/20  2000/09/06  1997/09/30
>   5688-197 1.02.0  1995/10/24  1995/10/27  2000/09/06  2001/12/31
>
>   5648-A25 2.01.0  1997/05/06  1997/05/23  2000/09/29  2004/12/31
>   5648-A25 2.02.0  2000/09/26  2000/09/29  2002/12/31  2004/12/31
>
>   5655-G53 3.01.0  2001/11/27  2001/11/30  2002/09/27  2004/04/04
>   5655-G53 3.02.0  2002/08/20  2002/09/27  2004/02/27  2005/10/03
>   5655-G53 3.03.0  2004/02/17  2004/02/27  2005/07/01  2007/04/30
>   5655-G53 3.04.0  2005/06/21  2005/07/01  2008/09/29  2015/04/30
>
>   5655-S71 4.01.0  2007/12/11  2007/12/14  2009/08/25  2014/04/30
>   5655-S71 4.02.0  2009/08/25  2009/08/28  2018/03/12  2021/09/30
>
>   5655-W32 05.01.00 2013/04/23 2013/06/21  2015/01/14  2020/04/30
>   5655-W32 05.02.00 2015/01/14 2015/02/27  2017/09/11  2020/04/30
>
>   5655-EC6 06.01.00 2016/02/16 2016/03/18  2020/03/09  -
>   5655-EC6 06.02.00 2017/07/17 2017/09/08  2020/03/09  -
>   5655-EC6 06.03.00 2019/09/03 2019/09/06  -   -
>
> Cheers,
> TomR  >> COBOL is the Language of the Future! <<
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> .

Tom,
Thank you for the table.
Actually I found some table in COBOL Migration Guide manual
https://www.ibm.com/support/knowledgecenter/hu/SS6SG3_6.3.0/migrate/igymprea
b2.html 

but your table is more detailed - I mean dates.
To make things more complex your table lack of third dimension ;-) I 
mean MLC vs VUE flavours, which is technically irrelevant, but introduce 
new PIDs (program numbers).
And this is good you preserved version numbering - that simplifies 
identification.

Funny fact: I vaguely remember 1999 and some official announcements 
about OS/VS COBOL withdrawals which were obscure and incomprehensible 
for me at the time. ;-)

BTW: This is pure curiosity, however was there any COBOL life on earth 
before 1974? I'm sure it was some COBOL, but it was really looong time 
ago. Maybe different product packaging and numbering, etc.

Regards
-- 
Radoslaw Skorupka
Lodz, Poland

==

Jeśli nie jesteś adresatem tej wiadomości:

- powiadom nas o tym w mailu zwrotnym (dziękujemy!),
- usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub
zapisałeś na dysku).
Wiadomość ta może zawierać chronione prawem informacje, które może
wykorzystać tylko adresat. Przypominamy, że każdy, kto rozpowszechnia
(kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza
prawo i może podlegać karze.

mBank S.A. z siedzibą w Warszawie, ul. Prosta 18, 00-850
Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st.
Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS
025237, NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości)
według stanu na 01.01.2020 r. wynosi 169.401.468 złotych.

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz
w Pakietach RODO (w wersji polskiej i angielskiej), które są na
www.mbank.pl/rodo

If you are not the addressee of this message:

- let us know by replying to this e-mail (thank you!),
- delete this message permanently (including all the copies which you have
printed out or saved).
This message may contain legally protected information, which may be used
exclusively by the addressee.Please be reminded that anyone who disseminates
(copies, distributes) this message or takes any similar action,

Re: Progam directory AD/Cycle C/370

2021-01-06 Thread R.S.


W dniu 06.01.2021 o 09:19, Tom Ross pisze:

BTW: Is there description/list of COBOL versions anywhere?

  I don't know, but I have lists!  Here is the entire history, no names, just
  product ids, but you can kind of tell which is which by the dates.
OS/VS COBOL, VS COBOL II, etc etc
Note: You need fixed-width caharacters to view this table:

  Program  Marketing   Service
  Number   VRM Announced   Available   Withdrawn   Discontinued

  5740-CB1 1.02.4  1974/05/13  1974/09/23  1992/12/18  1999/12/31

  5668-958 1.03.0  1988/09/13  1988/12/16  1997/06/30  1996/06/30
  5668-958 1.03.1  1989/09/19  1989/12/29  1997/06/30  1996/06/30
  5668-958 1.03.2  1990/09/05  1990/12/28  1997/06/30  1996/06/30
  5668-958 1.04.0  1992/09/15  1993/03/12  1997/06/30  2001/03/31

  5688-197 1.01.0  1991/09/11  1991/12/20  2000/09/06  1997/09/30
  5688-197 1.02.0  1995/10/24  1995/10/27  2000/09/06  2001/12/31

  5648-A25 2.01.0  1997/05/06  1997/05/23  2000/09/29  2004/12/31
  5648-A25 2.02.0  2000/09/26  2000/09/29  2002/12/31  2004/12/31

  5655-G53 3.01.0  2001/11/27  2001/11/30  2002/09/27  2004/04/04
  5655-G53 3.02.0  2002/08/20  2002/09/27  2004/02/27  2005/10/03
  5655-G53 3.03.0  2004/02/17  2004/02/27  2005/07/01  2007/04/30
  5655-G53 3.04.0  2005/06/21  2005/07/01  2008/09/29  2015/04/30

  5655-S71 4.01.0  2007/12/11  2007/12/14  2009/08/25  2014/04/30
  5655-S71 4.02.0  2009/08/25  2009/08/28  2018/03/12  2021/09/30

  5655-W32 05.01.00 2013/04/23 2013/06/21  2015/01/14  2020/04/30
  5655-W32 05.02.00 2015/01/14 2015/02/27  2017/09/11  2020/04/30

  5655-EC6 06.01.00 2016/02/16 2016/03/18  2020/03/09  -
  5655-EC6 06.02.00 2017/07/17 2017/09/08  2020/03/09  -
  5655-EC6 06.03.00 2019/09/03 2019/09/06  -   -

Cheers,
TomR  >> COBOL is the Language of the Future! <<

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



Tom,
Thank you for the table.
Actually I found some table in COBOL Migration Guide manual
https://www.ibm.com/support/knowledgecenter/hu/SS6SG3_6.3.0/migrate/igympreab2.html 


but your table is more detailed - I mean dates.
To make things more complex your table lack of third dimension ;-) I 
mean MLC vs VUE flavours, which is technically irrelevant, but introduce 
new PIDs (program numbers).
And this is good you preserved version numbering - that simplifies 
identification.


Funny fact: I vaguely remember 1999 and some official announcements 
about OS/VS COBOL withdrawals which were obscure and incomprehensible 
for me at the time. ;-)


BTW: This is pure curiosity, however was there any COBOL life on earth 
before 1974? I'm sure it was some COBOL, but it was really looong time 
ago. Maybe different product packaging and numbering, etc.


Regards
--
Radoslaw Skorupka
Lodz, Poland





==

Jeśli nie jesteś adresatem tej wiadomości:

- powiadom nas o tym w mailu zwrotnym (dziękujemy!),
- usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś 
na dysku).
Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać 
tylko adresat. Przypominamy, że każdy, kto rozpowszechnia (kopiuje, 
rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może 
podlegać karze.

mBank S.A. z siedzibą w Warszawie, ul. Prosta 18, 00-850 Warszawa,www.mBank.pl, 
e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział 
Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. 
Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2020 r. wynosi 
169.401.468 złotych.

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

- let us know by replying to this e-mail (thank you!),
- delete this message permanently (including all the copies which you have 
printed out or saved).
This message may contain legally protected information, which may be used 
exclusively by the addressee.Please be reminded that anyone who disseminates 
(copies, distributes) this message or takes any similar action, violates the 
law and may be penalised.

mBank S.A. with its registered office in Warsaw, ul. Prosta 18, 00-850 
Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital 
City of Warsaw, 12th Commercial Division of the National Court Register, KRS 
025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 
169.401.468 as a

Re: Problem executing bpxwunix

2021-01-06 Thread Paul Gilmartin

On Wed, 6 Jan 2021 18:01:53 +, Frank Swarbrick wrote:

>"bpxwunix() can be used outside of the z/OS UNIX REXX environment (for 
>example, in TSO/E). In this case, stdin, stdout, stderr, and environment 
>variables are not inherited from the current process environment. For example, 
>when executing a REXX exec in this environment, you must either export the 
>PATH statement before invoking the REXX exec (command = 'export PATH;tsocmd 
>time'), or supply the PATH statement to BPXWUNIX (env.1='PATH=/bin') in order 
>for the REXX exec to execute properly. Otherwise, the REXX exec fails and 
>message BPXWI is displayed."
>
>From 
>https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.bpxb600/wunix.htm
>
Looking at the example  I suspect the OP followed, from:

https://www.ibm.com/support/pages/system/files/inline-files/CSM_Session_automation_v1.1.pdf

o It fails to supply stdin
o It supplies a PATH which probably doesn't contain "echo".

This ought to be worthy of an RCF.  The author should have tested his Exec
under IRXJCL.

Why "address tso"?  I see no TSO commands.


>
>From: Seymour J Metz
>Sent: Wednesday, January 6, 2021 5:20 AM
>
>What was the exact call that you used and did you provide a PATH in the 
>environment parameter?  Since there is no login shell, things don't get 
>initialized the way you might expect.
>
>
>From: Gadi Ben-Avi 
>Sent: Wednesday, January 6, 2021 2:33 AM
>
>I would like to automate some csm (Copy services manager) from z/OS.
>I installed csmcli on z/OS, and if I run csmcli.sh from the omvs shell, it 
>works ok.
>I found the TechDoc named 'IBM Copy Services Manager session automation' by 
>Thomas Luther which has a rexx program that sets up the environment to run 
>csmcli.sh, get the output from it, and act upon the results.
>
>The rexx program uses bpxwunix to call cshcli.sh
>When I run the rexx program (whether under tso or in batch) I get lots of 
>error messages.
>I added an echo command at the beginning of csmcli.sh so I will know when it 
>starts.
>The command I added is 'echo "start csmcli.sh"'
>When I run it from the omvs shell, it works fine.
>When I run it from tso I get:
>echo: csmcli.sh 10: FSUM7351 not found
>
>Does this mean that it can't find the echo command?

-- gil

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

Re: Problem executing bpxwunix

2021-01-06 Thread Frank Swarbrick

I meant to reply to Gadi, not you.  Sorry.  Just providing a bit more detail.

From: IBM Mainframe Discussion List  on behalf of 
Seymour J Metz 
Sent: Wednesday, January 6, 2021 11:26 AM
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: Problem executing bpxwunix

Yes, that's why I asked what I asked. Until Gadi post's his code we're just 
guessing.

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Frank Swarbrick [frank.swarbr...@outlook.com]
Sent: Wednesday, January 6, 2021 1:01 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Problem executing bpxwunix

"bpxwunix() can be used outside of the z/OS UNIX REXX environment (for example, 
in TSO/E). In this case, stdin, stdout, stderr, and environment variables are 
not inherited from the current process environment. For example, when executing 
a REXX exec in this environment, you must either export the PATH statement 
before invoking the REXX exec (command = 'export PATH;tsocmd time'), or supply 
the PATH statement to BPXWUNIX (env.1='PATH=/bin') in order for the REXX exec 
to execute properly. Otherwise, the REXX exec fails and message BPXWI is 
displayed."

>From 
>https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.bpxb600/wunix.htm

From: IBM Mainframe Discussion List  on behalf of 
Seymour J Metz 
Sent: Wednesday, January 6, 2021 5:20 AM
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: Problem executing bpxwunix

What was the exact call that you used and did you provide a PATH in the 
environment parameter?  Since there is no login shell, things don't get 
initialized the way you might expect.

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Gadi Ben-Avi [gad...@malam.com]
Sent: Wednesday, January 6, 2021 2:33 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Problem executing bpxwunix

Hi,
I would like to automate some csm (Copy services manager) from z/OS.
I installed csmcli on z/OS, and if I run csmcli.sh from the omvs shell, it 
works ok.
I found the TechDoc named 'IBM Copy Services Manager session automation' by 
Thomas Luther which has a rexx program that sets up the environment to run 
csmcli.sh, get the output from it, and act upon the results.

The rexx program uses bpxwunix to call cshcli.sh
When I run the rexx program (whether under tso or in batch) I get lots of error 
messages.
I added an echo command at the beginning of csmcli.sh so I will know when it 
starts.
The command I added is 'echo "start csmcli.sh"'
When I run it from the omvs shell, it works fine.
When I run it from tso I get:
echo: csmcli.sh 10: FSUM7351 not found

Does this mean that it can't find the echo command?

How can I fix this?

Gadi

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

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

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

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

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

Re: Problem executing bpxwunix

2021-01-06 Thread Seymour J Metz

Yes, that's why I asked what I asked. Until Gadi post's his code we're just 
guessing.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Frank Swarbrick [frank.swarbr...@outlook.com]
Sent: Wednesday, January 6, 2021 1:01 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Problem executing bpxwunix

"bpxwunix() can be used outside of the z/OS UNIX REXX environment (for example, 
in TSO/E). In this case, stdin, stdout, stderr, and environment variables are 
not inherited from the current process environment. For example, when executing 
a REXX exec in this environment, you must either export the PATH statement 
before invoking the REXX exec (command = 'export PATH;tsocmd time'), or supply 
the PATH statement to BPXWUNIX (env.1='PATH=/bin') in order for the REXX exec 
to execute properly. Otherwise, the REXX exec fails and message BPXWI is 
displayed."

>From 
>https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.bpxb600/wunix.htm



From: IBM Mainframe Discussion List  on behalf of 
Seymour J Metz 
Sent: Wednesday, January 6, 2021 5:20 AM
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: Problem executing bpxwunix

What was the exact call that you used and did you provide a PATH in the 
environment parameter?  Since there is no login shell, things don't get 
initialized the way you might expect.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Gadi Ben-Avi [gad...@malam.com]
Sent: Wednesday, January 6, 2021 2:33 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Problem executing bpxwunix

Hi,
I would like to automate some csm (Copy services manager) from z/OS.
I installed csmcli on z/OS, and if I run csmcli.sh from the omvs shell, it 
works ok.
I found the TechDoc named 'IBM Copy Services Manager session automation' by 
Thomas Luther which has a rexx program that sets up the environment to run 
csmcli.sh, get the output from it, and act upon the results.

The rexx program uses bpxwunix to call cshcli.sh
When I run the rexx program (whether under tso or in batch) I get lots of error 
messages.
I added an echo command at the beginning of csmcli.sh so I will know when it 
starts.
The command I added is 'echo "start csmcli.sh"'
When I run it from the omvs shell, it works fine.
When I run it from tso I get:
echo: csmcli.sh 10: FSUM7351 not found

Does this mean that it can't find the echo command?

How can I fix this?

Gadi

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

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

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

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

Re: METAL C CATTR Assembly error

2021-01-06 Thread Joseph Reichman

I understand I did a find on openfile in the member and header files and it was 
found in three places at the function 
Pragma prologue and epilog 

I believe this to be a defect and opened a service request ticket with IBM

Thank you 



> On Jan 6, 2021, at 12:22 PM, Linda Chui  wrote:
> 
> On Wed, 30 Dec 2020 21:37:56 -0500, Joseph Reichman  
> wrote:
> 
>> Hi
>> 
>> 
>> 
>> I am getting the following error on a CATTR Assembly statement
>> 
>> 
>> 
>> 0001B0A 1B51   2833 OPENFI#C CSECT ,
>> 00
>> 
>> �2834 M_WSACATTR
>> RMODE(ANY),PART(openfile),NOTEXECUTABLE,ALIGN(2)  00
>> 
>> �** ASMA155S Previous use of symbol is not this section type
>> 
>> �** ASMA167E Required name missing
>> 
>> �** ASMA435I Record 2371 in IBMUSER.TEST.SOURCE(OPENFILE) on volume: JOEABC
>> 
>> 
>> 
>> 
>> 
>> Openfile is the name of my C function it is not a global variable  don�t
>> know why the compiler is generating a CATTR statement
>> 
>> 
>> 
>>  #ifdef __MVS__   
>> 
>>BOOL  openfile(int *aletd, char *filename, void *sysptrs) 
>> 
>>{ 
>> 
>> 
>> 
>> When I change the function name from openfile to something else e.g. openfil
>> I don�t get the error don�t get it 
>> 
>> 
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> Hi Joseph,
> 
> (posted on behalf of a colleague)
> 
> The M_WSA class is for Metal C reentrancy support. The PART name there is 
> what references the objects that are re-entrant. In the user's case, they 
> have openfile listed as a part meaning that either the function is considered 
> an object (not a function) that is reentrant (perhaps due to the expansion of 
> the BOOL macro in their environment) or that they have another reentrant 
> object somewhere that is named ‘openfile’ (they can pre-process the source to 
> check which case it is). The error they get from the assembler indicates the 
> latter case. i.e. They have another definition or reference to an object 
> named ‘openfile’ somewhere in their source (or their include file chain).
> 
> 
> Hope this helps?
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

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

Re: Problem executing bpxwunix

2021-01-06 Thread Frank Swarbrick

"bpxwunix() can be used outside of the z/OS UNIX REXX environment (for example, 
in TSO/E). In this case, stdin, stdout, stderr, and environment variables are 
not inherited from the current process environment. For example, when executing 
a REXX exec in this environment, you must either export the PATH statement 
before invoking the REXX exec (command = 'export PATH;tsocmd time'), or supply 
the PATH statement to BPXWUNIX (env.1='PATH=/bin') in order for the REXX exec 
to execute properly. Otherwise, the REXX exec fails and message BPXWI is 
displayed."

>From 
>https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.bpxb600/wunix.htm



From: IBM Mainframe Discussion List  on behalf of 
Seymour J Metz 
Sent: Wednesday, January 6, 2021 5:20 AM
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: Problem executing bpxwunix

What was the exact call that you used and did you provide a PATH in the 
environment parameter?  Since there is no login shell, things don't get 
initialized the way you might expect.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Gadi Ben-Avi [gad...@malam.com]
Sent: Wednesday, January 6, 2021 2:33 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Problem executing bpxwunix

Hi,
I would like to automate some csm (Copy services manager) from z/OS.
I installed csmcli on z/OS, and if I run csmcli.sh from the omvs shell, it 
works ok.
I found the TechDoc named 'IBM Copy Services Manager session automation' by 
Thomas Luther which has a rexx program that sets up the environment to run 
csmcli.sh, get the output from it, and act upon the results.

The rexx program uses bpxwunix to call cshcli.sh
When I run the rexx program (whether under tso or in batch) I get lots of error 
messages.
I added an echo command at the beginning of csmcli.sh so I will know when it 
starts.
The command I added is 'echo "start csmcli.sh"'
When I run it from the omvs shell, it works fine.
When I run it from tso I get:
echo: csmcli.sh 10: FSUM7351 not found

Does this mean that it can't find the echo command?

How can I fix this?

Gadi

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

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

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

Re: CICS COBOL co-compiler licensing?

2021-01-06 Thread Charles Mills

@TomR Thanks.

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Tom Ross
Sent: Wednesday, January 6, 2021 12:01 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: CICS COBOL co-compiler licensing?

>Does anyone know if there is an IBM license that covers the CICS COBOL
>co-compiler short of a full-blown CICS TS license?
>
>In other words, could you license the co-compiler for a "development
>machine" without having to license the full CICS transaction server?

There is no 'partial license' for CICS that would include the
'translator services' that are called by the COBOL compiler.

You must have the CICS product in order to compile COBOL programs
that have CICS statements in them.

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

Re: METAL C CATTR Assembly error

2021-01-06 Thread Linda Chui

On Wed, 30 Dec 2020 21:37:56 -0500, Joseph Reichman  
wrote:

>Hi
>
> 
>
>I am getting the following error on a CATTR Assembly statement
>
> 
>
>0001B0A 1B51   2833 OPENFI#C CSECT ,
>00
>
>�2834 M_WSACATTR
>RMODE(ANY),PART(openfile),NOTEXECUTABLE,ALIGN(2)  00
>
>�** ASMA155S Previous use of symbol is not this section type
>
>�** ASMA167E Required name missing
>
>�** ASMA435I Record 2371 in IBMUSER.TEST.SOURCE(OPENFILE) on volume: JOEABC
>
> 
>
> 
>
>Openfile is the name of my C function it is not a global variable  don�t
>know why the compiler is generating a CATTR statement
>
> 
>
>   #ifdef __MVS__   
>
> BOOL  openfile(int *aletd, char *filename, void *sysptrs) 
>
> { 
>
> 
>
>When I change the function name from openfile to something else e.g. openfil
>I don�t get the error don�t get it 
>
>
>--
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Hi Joseph,

(posted on behalf of a colleague)

The M_WSA class is for Metal C reentrancy support. The PART name there is what 
references the objects that are re-entrant. In the user's case, they have 
openfile listed as a part meaning that either the function is considered an 
object (not a function) that is reentrant (perhaps due to the expansion of the 
BOOL macro in their environment) or that they have another reentrant object 
somewhere that is named ‘openfile’ (they can pre-process the source to check 
which case it is). The error they get from the assembler indicates the latter 
case. i.e. They have another definition or reference to an object named 
‘openfile’ somewhere in their source (or their include file chain).

Hope this helps?

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

CUCI, aka CBT Tape 967

2021-01-06 Thread Robert Prins

I just had a look at this, to see how Tom Conley had implemented user-defined 
highlighting (using the USRHILIT REXX panel-exit) for non-ISPF supported 
languages, and I've made a suggestion to make a change that may make it easier 
to keep the various keyword and colouring REXX stems easier in sync. In essence, 
I'm replacing the


kw. = 4

kw.1= ' ALLOCATE '
kw.2= ' BDAMQSAM '
kw.3= ' BUNDLE '
kw.4= ' CAPS '

atr.1   = ''
atr.2   = ''
atr.3   = 'DD'
atr.4   = ''

clr.1   = ''
clr.2   = ''
atr.3   = 'RR'
clr.4   = ''

with

kw.  = -1
atr. = -1
clr. = -1

and just the kw.x'es above and start the remainder of the code with

do ! = 1 by 1 while kw.! \= -1
  if atr.! \= -1 then/* already user-set */
atr.! = translate(strip(kw.!), 'DD',,
   'ABCDEFGHIJKLMNOPQRSTUVWXYZ_-12')
  if clr.! \= -1 then/* already user-set */
clr.! = translate(strip(kw.!), 'RRRDDD',,
   'ABCDEFGHIJKLMNOPQRSTUVWXYZ_-12')
end

I'm five-nines certain that this will be slower than the direct assignments 
(there are 295 keywords for SQL), but it will/should/might make maintaining them 
a bit easier, and it will definitely reduce the size of the code.


I've also replaced his bracket/brace highlighting code with code I use in my 
EHIxxx execs in CBT Tape 769, basically storing attributes to be used in a stem 
(starting at stem.0) and just using the // (modulo) operator, without a "if rem 
= 0 then rem = 5" follow-up, which Tom has already  commented on with a 
"hbcolor.0 as other than the number of stems in hbcolor offends my 
sensibilities, so I'll have to give that one some thought ;-)"


A follow-up email to him also suggested, as yet not tested, that his way of 
highlighting "superfluous" closing brackets/braces will be incorrect when the 
opening bracket/brace is off-screen, as USRHILIT, unlike ISPF HILITE, only looks 
at the on-screen data.


But returning to the kw./atr./crl. stems, I seem to remember a discussion in a 
grey past on the long gone MVSHELP.COM forum that multiple assignments can be 
made really, really fast by using "parse", like Dough Nadel himself does in his 
code to add highlighting to SDSF, i.e.


parse value '0 R' with jclwords.0 jcolor. jlen.

By stringing all keywords together with suitable separators, a single statement 
could initialise the whole "kw." stem, and four more statements could initialise 
the "atr." and "clr." stems. (Yes four, it's left to the reader to figure out 
the two non-"parse" ones)


Would this be faster? I'd would appreciate it if someone could give it a try, as 
this is a panel-exit that's invoked every time a user presses Enter!


Robert

PS: And lastly, given that ISPF seems to have been more-or-less abandoned by IBM 
in favour of "whiter and shinier" "alternatives", wouldn't it make sense to 
engage Share and Guide into possibly convincing IBM to open(ish)-source it? Or 
do what they did with JES3, if there's anyone up to it?

--
Robert AH Prins
robert.ah.prins(a)gmail.com
The hitchhiking grandfather - https://prino.neocities.org/
Some REXX code for use on z/OS - https://prino.neocities.org/zOS/zOS-Tools.html

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

Re: Problem executing bpxwunix

2021-01-06 Thread Paul Gilmartin

On Wed, 6 Jan 2021 07:33:41 +, Gadi Ben-Avi  wrote:
>
>I would like to automate some csm (Copy services manager) from z/OS.
>I installed csmcli on z/OS, and if I run csmcli.sh from the omvs shell, it 
>works ok.
>I found the TechDoc named 'IBM Copy Services Manager session automation' by 
>Thomas Luther which has a rexx program that sets up the environment to run 
>csmcli.sh, get the output from it, and act upon the results.
>
Is that: 
https://www.ibm.com/support/pages/system/files/inline-files/CSM_Session_automation_v1.1.pdf
???

The BPXWUNIX example is amateurish; the author doesn't know Rexx very well.
He clearly doesn't understand that RETURN restores the parent addressing
environment.

Did you change the HOME and PATH ENVIRONMENT variables?

I'll suggest prefixing each "USS" command with "set -x; "


>The rexx program uses bpxwunix to call cshcli.sh
>When I run the rexx program (whether under tso or in batch) I get lots of 
>error messages.
>I added an echo command at the beginning of csmcli.sh so I will know when it 
>starts.
>The command I added is 'echo "start csmcli.sh"'
>When I run it from the omvs shell, it works fine.
>When I run it from tso I get:
>echo: csmcli.sh 10: FSUM7351 not found
>
>Does this mean that it can't find the echo command?
>
Yes.

>How can I fix this?
>
Try "PATH=/opt/IBM/CSM/CLI/:/bin"

Check that all the directories mentioned by Rexx exist.

-- gil

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

Re: Problem executing bpxwunix

2021-01-06 Thread Seymour J Metz

What was the exact call that you used and did you provide a PATH in the 
environment parameter?  Since there is no login shell, things don't get 
initialized the way you might expect.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Gadi Ben-Avi [gad...@malam.com]
Sent: Wednesday, January 6, 2021 2:33 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Problem executing bpxwunix

Hi,
I would like to automate some csm (Copy services manager) from z/OS.
I installed csmcli on z/OS, and if I run csmcli.sh from the omvs shell, it 
works ok.
I found the TechDoc named 'IBM Copy Services Manager session automation' by 
Thomas Luther which has a rexx program that sets up the environment to run 
csmcli.sh, get the output from it, and act upon the results.

The rexx program uses bpxwunix to call cshcli.sh
When I run the rexx program (whether under tso or in batch) I get lots of error 
messages.
I added an echo command at the beginning of csmcli.sh so I will know when it 
starts.
The command I added is 'echo "start csmcli.sh"'
When I run it from the omvs shell, it works fine.
When I run it from tso I get:
echo: csmcli.sh 10: FSUM7351 not found

Does this mean that it can't find the echo command?

How can I fix this?

Gadi

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

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

Visara 5990 Tapes

2021-01-06 Thread Shaffer, Terri

Hi,
  I am curious does anyone run Hardware DASD/TAPE from Visara?  And if TAPE, 
how you have it setup?

Thanks

Ms Terri E Shaffer
Senior Systems Engineer,
z/OS Support:
ACIWorldwide – Telecommuter
H(412-766-2697) C(412-519-2592)
terri.shaf...@aciworldwide.com


 [https://go.aciworldwide.com/rs/030-ROK-804/images/aci-footer.jpg] 

This email message and any attachments may contain confidential, proprietary or 
non-public information. The information is intended solely for the designated 
recipient(s). If an addressing or transmission error has misdirected this 
email, please notify the sender immediately and destroy this email. Any review, 
dissemination, use or reliance upon this information by unintended recipients 
is prohibited. Any opinions expressed in this email are those of the author 
personally.

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

Re: Progam directory AD/Cycle C/370

2021-01-06 Thread Tom Ross

>BTW: Is there description/list of COBOL versions anywhere?

 I don't know, but I have lists!  Here is the entire history, no names, just
 product ids, but you can kind of tell which is which by the dates.
OS/VS COBOL, VS COBOL II, etc etc
Note: You need fixed-width caharacters to view this table:

 Program  Marketing   Service
 Number   VRM Announced   Available   Withdrawn   Discontinued

 5740-CB1 1.02.4  1974/05/13  1974/09/23  1992/12/18  1999/12/31

 5668-958 1.03.0  1988/09/13  1988/12/16  1997/06/30  1996/06/30
 5668-958 1.03.1  1989/09/19  1989/12/29  1997/06/30  1996/06/30
 5668-958 1.03.2  1990/09/05  1990/12/28  1997/06/30  1996/06/30
 5668-958 1.04.0  1992/09/15  1993/03/12  1997/06/30  2001/03/31

 5688-197 1.01.0  1991/09/11  1991/12/20  2000/09/06  1997/09/30
 5688-197 1.02.0  1995/10/24  1995/10/27  2000/09/06  2001/12/31

 5648-A25 2.01.0  1997/05/06  1997/05/23  2000/09/29  2004/12/31
 5648-A25 2.02.0  2000/09/26  2000/09/29  2002/12/31  2004/12/31

 5655-G53 3.01.0  2001/11/27  2001/11/30  2002/09/27  2004/04/04
 5655-G53 3.02.0  2002/08/20  2002/09/27  2004/02/27  2005/10/03
 5655-G53 3.03.0  2004/02/17  2004/02/27  2005/07/01  2007/04/30
 5655-G53 3.04.0  2005/06/21  2005/07/01  2008/09/29  2015/04/30

 5655-S71 4.01.0  2007/12/11  2007/12/14  2009/08/25  2014/04/30
 5655-S71 4.02.0  2009/08/25  2009/08/28  2018/03/12  2021/09/30

 5655-W32 05.01.00 2013/04/23 2013/06/21  2015/01/14  2020/04/30
 5655-W32 05.02.00 2015/01/14 2015/02/27  2017/09/11  2020/04/30

 5655-EC6 06.01.00 2016/02/16 2016/03/18  2020/03/09  -
 5655-EC6 06.02.00 2017/07/17 2017/09/08  2020/03/09  -
 5655-EC6 06.03.00 2019/09/03 2019/09/06  -   -

Cheers,
TomR  >> COBOL is the Language of the Future! <<

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

CICS COBOL co-compiler licensing?

2021-01-06 Thread Tom Ross

>Does anyone know if there is an IBM license that covers the CICS COBOL
>co-compiler short of a full-blown CICS TS license?
>
>In other words, could you license the co-compiler for a "development
>machine" without having to license the full CICS transaction server?

There is no 'partial license' for CICS that would include the
'translator services' that are called by the COBOL compiler.

You must have the CICS product in order to compile COBOL programs
that have CICS statements in them.

Cheers,
TomR  >> COBOL is the Language of the Future! <<

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

Re: Progam directory AD/Cycle C/370

Re: Progam directory AD/Cycle C/370

Re: Progam directory AD/Cycle C/370

Re: Progam directory AD/Cycle C/370

Re: Progam directory AD/Cycle C/370

Re: Problem executing bpxwunix

Re: Problem executing bpxwunix

Re: Problem executing bpxwunix

Re: METAL C CATTR Assembly error

Re: Problem executing bpxwunix

Re: CICS COBOL co-compiler licensing?

Re: METAL C CATTR Assembly error

CUCI, aka CBT Tape 967

Re: Problem executing bpxwunix

Re: Problem executing bpxwunix

Visara 5990 Tapes

Re: Progam directory AD/Cycle C/370

CICS COBOL co-compiler licensing?

18 matches

Site Navigation

Mail list logo

Footer information