Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-23 Thread Scott Ford
using SETENV and C run time environment In <1319119689.78129.yahoomail...@web65503.mail.ac4.yahoo.com>, on 10/20/2011   at 07:08 AM, Scott Ford said: >Yep, me too John, I had to add it to my SYSLMOD stmts in the LKED SYSLMOD? Shirley you mean SYSLIB. --     Shmuel (Seymour J.) Metz

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-23 Thread Scott Ford
: Re: Cobol dynamic file allocation using SETENV and C run time environment In <1319326715.98941.yahoomailmob...@web161421.mail.bf1.yahoo.com>, on 10/22/2011   at 04:38 PM, Ed Gould said: >I had asked as to why he had DCB specified on SYSUT1 in his JCL for >the linkage editor aka

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-23 Thread Ed Gould
The program was linked under Z/os and the program executed was IEWL so unless there was a JOBLIB that wasn't shown the user did not supply the entire JCL stream, there was no way to prove what was really used. so if you think there is/was a difference please ask the user. My question was rel

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-23 Thread Shmuel Metz (Seymour J.)
In <1319326715.98941.yahoomailmob...@web161421.mail.bf1.yahoo.com>, on 10/22/2011 at 04:38 PM, Ed Gould said: >I had asked as to why he had DCB specified on SYSUT1 in his JCL for >the linkage editor aka binder. The linkage editor and the binder are two different programs. >I have only seen i

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-22 Thread Ed Gould
Seymour, I had asked as to why he had DCB specified on SYSUT1 in his JCL for the linkage editor aka binder. I have only seen it used in sysgens. Not even in compiler JCL from IBM. Ed -- For IBM-MAIN subscribe / signoff / archiv

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-22 Thread Shmuel Metz (Seymour J.)
In , on 10/20/2011 at 06:15 PM, Uriel Carrasquilla said: >Do you still have to put a //SYSLMOD DD in the LKED step (link >editing) if you already have in in the SYS1.PARMLIB(LPALST00)? Il va sans dire! SYSLMOD identifies the output library and has nothing to do with the LPA. Neither SYS1.PARM

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-22 Thread Shmuel Metz (Seymour J.)
In <1319158632.66007.yahoomailmob...@web161421.mail.bf1.yahoo.com>, on 10/20/2011 at 05:57 PM, Ed Gould said: >I have seen it used as far back as MFT sysgen and I wondered why IBM >put it in. What is "it"? Without an attribution line and enough quoted text to provide context, the reader is le

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-22 Thread Shmuel Metz (Seymour J.)
In <1319119689.78129.yahoomail...@web65503.mail.ac4.yahoo.com>, on 10/20/2011 at 07:08 AM, Scott Ford said: >Yep, me too John, I had to add it to my SYSLMOD stmts in the LKED SYSLMOD? Shirley you mean SYSLIB. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-21 Thread Scott Ford
  From: Rick Fochtman To: IBM-MAIN@bama.ua.edu Sent: Friday, October 21, 2011 5:13 PM Subject: Re: Cobol dynamic file allocation using SETENV and C run time environment Yes Rick - Scott Ford wrote: >Rick: > >Your sayin

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-21 Thread Rick Fochtman
Fochtman To: IBM-MAIN@bama.ua.edu Sent: Thursday, October 20, 2011 7:59 PM Subject: Re: Cobol dynamic file allocation using SETENV and C run time environment - Scott, Interesting side point to me. Does specifying a DCB on

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-20 Thread Tom Ross
>>>SCEELKED contains SETENV and PUTENV. >>'setenv' may be in SCEELKED, but that does not help the dynamic call case, >>where the call would be resolved at runtime, not link time. >> >>You cannot call lower case names dynamically from COBOL at this time. >>The dynamic call routine 'normalizes' all

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-20 Thread Ed Gould
Rick, I have seen it used as far back as MFT sysgen and I wondered why IBM put it in. Anyone? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN I

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-20 Thread Scott Ford
dynamic file allocation using SETENV and C run time environment - > Scott, > > Interesting side point to me. Does specifying a DCB on sysut1 on the linkedit > make a difference on the "block size" of the

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-20 Thread Scott Ford
: Cobol dynamic file allocation using SETENV and C run time environment Scott, Interesting side point to me. Does specifying a DCB on sysut1 on the linkedit make a difference on the "block size" of the lmod? Not the size but the block

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-20 Thread Rick Fochtman
- Scott, Interesting side point to me. Does specifying a DCB on sysut1 on the linkedit make a difference on the "block size" of the lmod? Not the size but the block size? Ed

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-20 Thread Ed Gould
Scott, Interesting side point to me. Does specifying a DCB on sysut1 on the linkedit make a difference on the "block size" of the lmod? Not the size but the block size? Ed -- For IBM-MAIN subscribe / signoff / archive access

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-20 Thread Clark Morris
On 20 Oct 2011 10:48:07 -0700, in bit.listserv.ibm-main you wrote: >>SCEELKED contains SETENV and PUTENV. > >'setenv' may be in SCEELKED, but that does not help the dynamic call case, >where the call would be resolved at runtime, not link time. > >You cannot call lower case names dynamically from

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-20 Thread Scott Ford
   DD DDNAME=SYSIN //SYSIN DD * Scott J Ford Software Engineer http://www.identityforge.com   From: Uriel Carrasquilla To: IBM-MAIN@bama.ua.edu Sent: Thursday, October 20, 2011 2:15 PM Subject: Re: Cobol dynamic file allocation using SETENV and C run time

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-20 Thread Uriel Carrasquilla
, October 20, 2011 10:08 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Cobol dynamic file allocation using SETENV and C run time environment Yep, me too John, I had to add it to my SYSLMOD stmts in the LKED...Once I did that no problem Scott J Ford Software Engineer http://www.identityforge.com

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-20 Thread Uriel Carrasquilla
Engineer http://www.identityforge.com From: Ed Gould To: IBM-MAIN@bama.ua.edu Sent: Thursday, October 20, 2011 12:36 PM Subject: Re: Cobol dynamic file allocation using SETENV and C run time environment John, That is one solution. However there is a potential to

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-20 Thread Uriel Carrasquilla
Scott Ford [scott_j_f...@yahoo.com] Sent: Thursday, October 20, 2011 10:04 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Cobol dynamic file allocation using SETENV and C run time environment Uriel: We use it all the time for LE Cobol, etc and we had to do nothing to place it in the LINKLIST. IBM packag

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-20 Thread Tom Ross
>SCEELKED contains SETENV and PUTENV. 'setenv' may be in SCEELKED, but that does not help the dynamic call case, where the call would be resolved at runtime, not link time. You cannot call lower case names dynamically from COBOL at this time. The dynamic call routine 'normalizes' all names, inclu

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-20 Thread Scott Ford
://www.identityforge.com   From: Ed Gould To: IBM-MAIN@bama.ua.edu Sent: Thursday, October 20, 2011 12:36 PM Subject: Re: Cobol dynamic file allocation using SETENV and C run time environment John, That is one solution. However there is a potential to break a lot of working code

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-20 Thread Ed Gould
John, That is one solution. However there is a potential to break a lot of working code. Compatibility has never been one of LE's strong points. Ed -- For IBM-MAIN subscribe / signoff / archive access instructions, send email

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-20 Thread Scott Ford
ubject: Re: Cobol dynamic file allocation using SETENV and C run time environment If you're going to CALL it from COBOL, using the DYNAM compiler option, then the library needs to be available to the job during execution. That means in the LNKLST or STEPLIB/JOBLIB DD statement. Another possibi

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-20 Thread Scott Ford
. Scott J Ford Software Engineer http://www.identityforge.com   From: Uriel Carrasquilla To: IBM-MAIN@bama.ua.edu Sent: Thursday, October 20, 2011 9:04 AM Subject: Re: Cobol dynamic file allocation using SETENV and C run time environment I found CEE.SCEELKED with

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-20 Thread McKown, John
should it be placed on the LINKLIST? > Thank you. > > > > From: IBM Mainframe Discussion List [IBM-MAIN@bama.ua.edu] on > behalf of McKown, John [john.mck...@healthmarkets.com] > Sent: Wednesday, October 19, 2011 5:33 PM > To: IBM-MAIN@bama.ua.edu > Subject:

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-20 Thread Uriel Carrasquilla
Mainframe Discussion List [IBM-MAIN@bama.ua.edu] on behalf of McKown, John [john.mck...@healthmarkets.com] Sent: Wednesday, October 19, 2011 5:33 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Cobol dynamic file allocation using SETENV and C run time environment SCEELKED contains SETENV and PUTENV

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-20 Thread McKown, John
Company.SM > -Original Message- > From: IBM Mainframe Discussion List > [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Scott Ford > Sent: Wednesday, October 19, 2011 5:10 PM > To: IBM-MAIN@bama.ua.edu > Subject: Re: Cobol dynamic file allocation using SETENV and C >

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-19 Thread Scott Ford
t; [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Uriel Carrasquilla > Sent: Wednesday, October 19, 2011 3:32 PM > To: IBM-MAIN@bama.ua.edu > Subject: Cobol dynamic file allocation using SETENV and C run > time environment > > I have a developer that is not being able to make a call

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-19 Thread McKown, John
rasquilla > Sent: Wednesday, October 19, 2011 3:32 PM > To: IBM-MAIN@bama.ua.edu > Subject: Cobol dynamic file allocation using SETENV and C run > time environment > > I have a developer that is not being able to make a call to > SETENV from within Cobol (Cobol snippet:

Re: Cobol dynamic file allocation using SETENV and C run time environment

2011-10-19 Thread Scott Ford
Wednesday, October 19, 2011 4:31 PM Subject: Cobol dynamic file allocation using SETENV and C run time environment I have a developer that is not being able to make a call to SETENV from within Cobol (Cobol snippet: call 'setenv' using envname,...). I found that the C routines in the LE

Cobol dynamic file allocation using SETENV and C run time environment

2011-10-19 Thread Uriel Carrasquilla
I have a developer that is not being able to make a call to SETENV from within Cobol (Cobol snippet: call 'setenv' using envname,...). I found that the C routines in the LE run time environment must be available. Does anybody know what I need to check in the linklist/lpa to make sure that Cobol f