home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!paladin.american.edu!auvm!PENNDRLS.UPENN.EDU!YETTER
- Return-Path: <YETTER@PENNDRLS.UPENN.EDU>
- Message-ID: <9301230158.AA15915@noc2.dccs.upenn.edu>
- Newsgroups: bit.listserv.notis-l
- Date: Fri, 22 Jan 1993 20:40:26 EST
- Sender: NOTIS discussion group list <NOTIS-L@TCSVM.BITNET>
- From: Peggy Yetter <YETTER@PENNDRLS.UPENN.EDU>
- Subject: RE: 24 hour OPAC
- Comments: To: NOTIS-L%TCSVM.BITNET@NOC2.DCCS.UPENN.EDU
- Lines: 37
-
- > We've had 24-hr a day access for four years now. CICS stays up all
- > the time, and I code our JCL so that when a file is scheduled for
- > update, the operator closes that file, reopening it after the job
- > completes. This results in a few minutes or so when the database
- > might not truly be available, but nobody ever seems to notice it. The
- > advantage to folks dialing in and telnetting to us is obvious and well
- > worth the time I spend putting PAUSEs in the JCL -- and the relatively
- > few times an operator who is asleep at the switch has forgotten to close a
- > file for update! This "feature" of our OPAC is greatly appreciated by
- > both faculty and students.
- >
- > Leigh Williams
- > SFASU
- > F_WILLIAMS@CCSVAX.SFASU.EDU
- Leigh,
- When we were a VSE site we did the same thing but what about LB010JC6?
- Don't you get strange results when you run this with CICS up? I was under
- the impression that bringing CICS down puts an EOF in the journal 6 so
- that LB010JC6 knows when to stop processing. Anyway, we brought our system
- down for LB010JC6 and since LB610 requires updates to the bib, patron and
- item file, we kept it down for that too. So we were running for 23.5 hours
- with no complaints from patrons when they found some files closed.
- But that brings up another question. Now that we are a MVS site, we
- can't seem to do the same thing. If we run a job that requires a deletion
- of a VSAM file (like LD200), closing and disabling the file does not
- allow us to delete it as it did under VSE. We get an error message that
- CICS is using the file. Is there something that we can do to right this
- or is this the way MVS works? We have found the same phenomena when
- using the backup utility, DFSS. CICS has to be down to backup our data
- files. Anybody have a suggestion?
- -------------------------------------------------------------------------
- | Peggy Yetter : Van Pelt Dietrich Library Center |
- | Systems Analyst : 3420 Walnut Street |
- | University of Pennsylvania : Philadelphia, PA 19104-6206 |
- | yetter@penndrls.upenn.edu : (215)898-4824 |
- | MVS/ESA 4.2; CICS 2.1; NOTIS 5.1; MDAS 1.3; GTO 3.1 |
- -------------------------------------------------------------------------
-