Date:         Mon, 6 Dec 1999 16:44:11 -0000
Reply-To:     Neil.Simpson@NATWEST.COM
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
Comments:     To: dean.bross@MAIL.VA.GOV
From:         Neil Simpson <Neil.Simpson@NATWEST.COM>
Subject:      Re: Accessing archived flat files on MVS using SAS/Connect
Comments: To: SAS-L@LISTSERV.VT.EDU
Content-Type: text/plain; charset="ISO-8859-1"

Dean Bross (clearly being MVSist) said
        "I have found, in general, that it is hard to get a
> migrated data set back from MVS when you are in an
> interactive session.  This includes just plain old
> TSO SPF sessions.  When you run a batch job, MVS
> automatically goes out and gets the data back."
>
>
This is patently untrue. If DFHSM is recalling a dataset from tape and you
are in ISPF, then your session goes into a Detected Wait (I think) until
DFHSM recalls the dataset. This is the same in batch.
It would appear that SAS/CONNECT has trouble handling the session going into
a DW. Or perhaps it's TCP/IP. It is not, however, a problem with MVS.

        "don't know any way around the problem except to
> do what you are doing or submit a job full of
> IEFBR14 steps before doing anything with a SAS
> CONNECT session."
>
I'm sure there is a more elegant solution than this....


Keeping the faith in MVS (OS/390 actually) !



> ----------
> From:         Bross, Dean S[SMTP:dean.bross@MAIL.VA.GOV]
> Sent:         06 December 1999 15:55
> To:   SAS-L@LISTSERV.VT.EDU
> Subject:      Re: Accessing archived flat files on MVS using SAS/Connect
>
> I have found, in general, that it is hard to get a
> migrated data set back from MVS when you are in an
> interactive session.  This includes just plain old
> TSO SPF sessions.  When you run a batch job, MVS
> automatically goes out and gets the data back.
>
> I don't know any way around the problem except to
> do what you are doing or submit a job full of
> IEFBR14 steps before doing anything with a SAS
> CONNECT session.
>
> Dean Bross
>
> > -----Original Message-----
> > From: Edel, Christoph (Frankfurt) [mailto:CEdel@DE.IMSHEALTH.COM]
> > Sent: Monday, December 06, 1999 9:50 AM
> > To: SAS-L@LISTSERV.UGA.EDU
> > Subject: Q: Accessing archived flat files on MVS using SAS/Connect
> >
> >
> > Gentle Folks,
> >
> > this query comes from someone not yet very well-versed in
> > MVS, so please bear with me if the problem description is
> > less than precise.
> >
> > Platforms: Local host - PC WinNT4.0 / SAS 6.12 (TS020),
> > remote host - IBM main frame /MVS, SAS 6.09 (TS450).
> >
> > Software: SAS/Connect (Access method: TCP/IP).
> >
> > The problem is that when trying to read archived MVS flat
> > files with SAS/Connect, the job simply halts at the point
> > where such files are to be accessed, with a message as shown
> > in the log attached (preceding the TCP/IP break).
> >
> > Signon and remote session start work flawlessly.
> >
> > The same data step will run smoothly in batch under MVS when
> > the file association is made via JCL: The job stops, the file
> > will be un-archived, and the job continues (or the files are
> > unarchived, and then the job starts - my vague understanding
> > of MVS). For SAS/Connect, JCL file associations need to be
> > replaced by appropriate FILENAME statements.
> >
> > To circumvent the problem, I currently try to browse all data
> > files to be read on the main frame using the ISPF editor, and
> > will be prompted whether or not I want to un-archive, and
> > then submit the code. This method is, of course, highly inefficient.
> >
> > SI Tech Support could not help so far, and I did RTFM the MVS
> > Companion (admittedly not understanding all the options due
> > to MVS knowledge deficiencies) to no avail so far.
> >
> > A sample program and log follow.
> >
> > Any help will be greatly appreciated.
> >
> > Christoph Edel
> > IMS Health, Frankfurt (Germany)
> > CEdel@de.imshealth.com
> >
> >
> > %* *** sample program;
> > options source source2 notes;
> >
> > %* *** configure SAS/Connect;
> > %* *** this requires the following settings;
> > %* *** the RLINK file referred to contains prompts for
> > user-id and password;
> > %let IMSMF = XYZ.AB.C.D;
> >
> > filename rlink "X:\YYY\zz_prog\tcptso.scr";
> > options  comamid = tcp
> >          remote = IMSMF
> >          ;
> >
> > %* *** establish connection to the main frame / remote host;
> > signon;
> >
> >
> > %* *** submit code on the remote host;
> > rsubmit;
> >
> >   %* *** set options in remote session;
> >   options source source2 notes mprint;
> >
> >   filename t109 "KPA.t109tap.m01.G0005V00" DISP = SHR;
> >
> >   data work.t109 ( drop = rectype );
> >
> >         format pfc z7.;
> >
> >         infile t109;
> >         input rectype 1@;
> >         if rectype = 1;
> >
> >         input @4 units pd3.
> >               pfc 14 - 20
> >               phcode 37-42
> >               ;
> >   run;
> >
> >   %* *** download the data set to the local host;
> >   proc download
> >     data = work.t109 out = work.t109;
> >   run;
> >
> >
> > endrsubmit;
> >
> > signoff;
> >
> >
> >
> >
> > %* **** LOG *** LOG *** LOG;
> >
> > NOTE: Copyright (c) 1989-1996 by SAS Institute Inc., Cary, NC, USA.
> > NOTE: SAS (r) Proprietary Software Release 6.12  TS020
> >       Licensed to ACME AG, Site XXXXXXXXXXX.
> >
> >
> >
> >
> > NOTE: AUTOEXEC processing beginning; file is c:\sas\autoexec.sas.
> >
> >
> > NOTE: AUTOEXEC processing completed.
> >
> > 1    options source source2 notes;
> > 2    %* *** configure SAS/Connect;
> > 3    %* *** this requires the following settings;
> > 4    %* *** the RLINK file referred to contains prompts for
> > user-id and password;
> > 5    %let IMSMF = XXX.AB.C.D;
> > 6    filename rlink "X:\YYY\zz_prog\tcptso.scr";
> > 7    options  comamid = tcp
> > 8             remote = IMSMF
> > 9             ;
> > 10   %* *** establish connection to the main frame / remote host;
> > 11   signon;
> > NOTE: Remote signon to IMSMF commencing (SAS Release
> > 6.12.0020P103196).
> > NOTE: Script file 'tcptso.scr' entered.
> > NOTE: Logged on to TSO.... Starting remote SAS now.
> > NOTE: SAS/CONNECT conversation established.
> > NOTE: Copyright (c) 1989-1996 by SAS Institute Inc., Cary, NC, USA.
> > NOTE: SAS (r) Proprietary Software Release 6.09  TS450
> >       Licensed to ACME AG OFFICE FRANKFURT, Site XXXXXXXXX.
> >
> > NOTE: Running on IBM Model 9672 Serial Number 031122,
> >                  IBM Model 9672 Serial Number 131122,
> >                  IBM Model 9672 Serial Number 231122.
> >
> >
> > NOTE: SAS system options specified are:
> >       DMR,COMAMID=TCP,TCPIPPRF=SYS1.TCPIP.V3R2,
> > NOTERMINAL,NO$SYNTAXCHECK
> >
> > NOTE: The initialization phase used 0.04 CPU seconds and 1111K.
> > NOTE: Remote signon to IMSMF complete.
> > 12   %* *** submit code on the remote host;
> > 13   rsubmit;
> > NOTE: Remote submit to IMSMF commencing.
> > REMOTE(IMSMF): DMS2987 DATA SET CATALOGED TO SAMS:DISK
> > PSEUDO-VOLUME ARCIVE
> > REMOTE(IMSMF): DMS2987 SAMS:DISK HAS ARCHIVED KPA.T109TAP.M01.G0005V00
> > REMOTE(IMSMF):
> >
> > NOTE: TCP/IP Break choice was 'I'.
> >
> >
> > NOTE: TCP/IP Break choice was 'A'.
> >
> > ERROR: Communication partner has terminated the conversation.
> > ERROR: Remote submit to IMSMF cancelled.
> > 14
> > 15   signoff;
> > NOTE: A link to IMSMF does not exist.  SIGNOFF is not necessary.
> > ERROR: Remote signoff from IMSMF cancelled.
> >
>

---------------------------------------------------------------------------
The contents of this e-mail may be privileged and are confidential.  It may not be disclosed to or used by anyone other than the addressee(s), nor copied in any way.  If received in error, please advise the sender, then delete it from your system.
National Westminster Bank Plc is regulated by the Personal Investment Authority and IMRO for investment business. A member of the NatWest and Gartmore Marketing Group advising on the life assurance, pensions and unit trust products only of that Marketing Group.
Registered Office: 41 Lothbury London EC2P 2BP
Registered Number: 929027 England
---------------------------------------------------------------------------