× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. May 2007

RE: Putting a display file into production.

Yes, the potential exists to duplicate all display files.

I have found that display files follow the 80/20 rule. Users normally are
in a few screens 80% of the time, normally these are the ones that "can
not wait" for a modification to be promoted. Duplicate only those that
meet this criteria(or come to meet this critera).

Michael

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Walden H. Leverich
Sent: Wednesday, May 09, 2007 3:32 PM
To: Midrange Systems Technical Discussion
Subject: RE: Putting a display file into production.

The problem I see w/this approach is you're requiring the system to
duplicate every display file for every user at login, not a quick process.
Alan's has the advantage of allowing the user to run from the native
library. Plus, there have been many times I've looked at the locks on a
display file to determine who is in a program. <G>

-Walden

--
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
jmichael.smith@xxxxxxxxxxx
Sent: Wednesday, May 09, 2007 2:23 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Putting a display file into production.

Using a "normal" library will work as well.

Library list would look like:
1> QTEMPUSER - Where every user has a unique library
2> PRODOBJLIB

At application startup:
DLTF QTEMPUSER/DSPFILE
CRTDUPOBJ to QTEMPUSER

As a personal standard(for me) QTEMP is always 1st in the library list.
Newer object versions are created in other libraries, these are then
tested by: ADDLIBLE LIB(X) POSITION(*BEFORE QTEMP).

Michael




-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
Sent: Wednesday, May 09, 2007 11:34 AM
To: Midrange Systems Technical Discussion
Subject: RE: Putting a display file into production.


Michael
NICE idea (and even better, really simple), I'm jealous I didn't think
of
this myself..
Unfortunately, the standard we have at our site is that QTEMP is at the
bottom of our library list.
I went through a REALLY lengthy e-mail thread just recently on the pro's
&
cons of placing QTEMP at the top, bottom or somewhere in between, of the
library list.



Alan Shore

NBTY, Inc
(631) 244-2000 ext. 5019
AShore@xxxxxxxx
"If you're going through Hell, keep going" - Winston Churchill

midrange-l-bounces@xxxxxxxxxxxx wrote on 05/09/2007 12:20:39 PM:

Assuming that QTEMP is ahead of your production library in your
library list, consider creating a duplicate object in QTEMP when ever
the applications does a "start up".

Then you can promote as often as you like.

Michael

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
Sent: Tuesday, May 08, 2007 8:37 AM
To: Midrange Systems Technical Discussion
Subject: Re: Putting a display file into production.


Morning Bob
We just did the same thing with our order entry This is how we did it
The WORKSTN in you program make user open (USROPN) Create a new field
(stand-alone or whatever) that will contain the id of the DDS In our
instance

D Wrkstnid s 20A inz('DDSNAMEA')

We have 3 Work stations
DDSNAME
DDSNAMEA
DDSNAMEB
In all instances we make changes to DDSNAME.
Then whichever is the value of Wrkstnid (in this instance DDSNAMEA)
we copy DDSNAME to the other one (in this instance DDSNAMEB is the
opposite of
DDSNAMEA) and we change WRKSTNID to DDSNAMEB

Then within the C-specs we have the following command

C eval Clpstatement = 'OVRDSPF FILE(ORD122) -
C TOFILE(*LIBL/' +
C %trim(Wrkstnid) +
C ')'
C eval Errorflag = As400cmd(Clpstatement)
C open ORD122

and obviously a

C if %open(Ord122)
C close Ord122
C endif
C MOVEL '1' *INLR
C RETURN

and within the D-specs

// Execute Command (system) Subprocedure Variables
D As400cmd PR 10I 0 ExtProc('system')
D CmdText * Value Options(*String)
D
D ErrorCPF S 7A Import('_EXCP_MSGID')
D ErrorFlag S 10I 0 Inz(0)

This may seem convoluted, and I've tried to explain it to other people

here, but I know it works.
Whenever we need to make a change to the DDS, we promote everything
(NOT DDSNAMEB in this instance) to PRODUCTION, then inform the users
that they need to sign-off and sign back on again at their earliest
convenience to start using the new version.

If you have any further questions
of if you think I've left something out, please feel free to ask



Alan Shore

NBTY, Inc
(631) 244-2000 ext. 5019
AShore@xxxxxxxx
"If you're going through Hell, keep going" - Winston Churchill




Bob.Voltz@colaik.

com

Sent by:
To

midrange-l-bounce Midrange Systems Technical

s+alanshore=nbty. Discussion

com@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>


cc



05/08/2007 09:01
Subject

AM Putting a display file into

production.



Please respond to

Midrange Systems

Technical

Discussion

<midrange-l@midra

nge.com>









Is there a way to put a display file into production when users are
using the program and have a lock on it?



The information transmitted is intended only for the person or entity
to which it is addressed and may contain confidential, proprietary,
and/or privileged material. Any review, retransmission, dissemination
or other use of, or taking of any action in reliance upon this
information by persons or entities other than the intended recipient
is prohibited. If you received this in error, please contact the
sender and delete the material.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.




------------------------------------------------------------------------
--
----

This message contains information from Certegy, Inc which may be
confidential and privileged. If you are not an intended recipient,
please refrain from any disclosure, copying, distribution or use of
this information and note that such actions are prohibited. If you
have received this transmission in error, please notify by e:mail
postmaster@xxxxxxxxxxxx

========================================================================
==
====


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.




------------------------------------------------------------------------
------
This message contains information from Certegy, Inc which may be
confidential and privileged. If you are not an intended recipient,
please refrain from any disclosure, copying, distribution or use of this
information and note that such actions are prohibited. If you have
received this transmission in error, please notify by e:mail
postmaster@xxxxxxxxxxxx
========================================================================
======


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.