vb.net and cobol.net - passing filenames
From: ari (unikoski_at_yahoo.com)
Date: 03/28/05
- Previous message: Howard Brazee: "Re: OT - "lie" vs "error""
- Next in thread: Pete Dashwood: "Re: vb.net and cobol.net - passing filenames"
- Reply: Pete Dashwood: "Re: vb.net and cobol.net - passing filenames"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 28 Mar 2005 09:39:26 -0800
I will need to transfer a number of mainframe cobol programs to a
windows environment (fujitsu cobol.net), and write a vb.net control
program to call them.
The cobol programs are called repeatedly for different files: the cobol
programs don't care, as they access the files using
"select input-file assign to infile"
where infile (on the mainframe) is a DDNAME and the physical filename
is a DSNNAME.
Under Micro-focus I could do this by setting an environment variable
setting DDNAME=DSNNAME and it works fine.
Is is possible to do the same here - i.e. have the VB.NET set
environment variables and the cobol program will use to get the
physical filename? Is there another option?
I noticed the post
that suggests this will work - but will I always be bothered by the
window popping up the post is asking about - or is is smart enough not
to open the window if it has all the environment variables it needs?
Unfortunately at the moment I don't yet have Fujistu so its hard for me
to make tests at the moment.
Thanks,
- Previous message: Howard Brazee: "Re: OT - "lie" vs "error""
- Next in thread: Pete Dashwood: "Re: vb.net and cobol.net - passing filenames"
- Reply: Pete Dashwood: "Re: vb.net and cobol.net - passing filenames"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|