Missing patch XM*999*172

[Kevin Toppenberg]

I have gotten patched up to the point that I have been able to apply the first 2 months of the WorldVistA multibuilds.  But not all packages have caught up yet.  As I am trying to install  BUILD 2009 06.1, I am getting a conflict with a missing XM patch.  I have fully patched up XM to all the available patches that I can find, but they are all version 8.0.  This seems to be calling for a version "999", which I suspect is some message that this is somehow a different type of patch.

Checking Install for Package HL*1.6*142

Will first run the Environment Check Routine, HLP142

Checking environment ...

'ORLANDO VAMC' entry with station number as 675 does not exist in Institution

file.

'ORLANDO.MED.VA.GOV' entry does not exist in Domain file, patch XM*999*172

must be installed first.

Aborting installation...

HL*1.6*142 Build will not be installed

               Aug 26, 2012@21:35:34

Checking Install for Package PSN*4.0*207

Will first run the Environment Check Routine, PSN207E

 

Install Questions for PSN*4.0*207

**NOTHING INSTALLED**

Any ideas?

Nancy, I looked for the patch on your server, but couldn't tell which directory to search into.

Thanks

Kevin

 

[Nancy Anthracite]

The read-me file that is in the Multibuild indicates that it is not concerned
if the Domain is missing if it is in a test account and it will not try to
restart the HL-7 Listeners. Since we don't want to send anything to Orlando
anyway, I suspect if you just add the domain entry and the institution with
only the barest of information so it can't really find them, you will be OK or
if you change your account designation to a test account during the install of
the Multibuild you will be OK.

See the read-me file in the Multibuild around line 13000

--
Nancy Anthracite

[Nancy Anthracite]

You can try to change to the test account using this option:

XU SID ASK Ask if Production Account

I think you will have to shut down Taskman and Mailman and get out of gtm and
then go back in and start up again to get it to work. You might have to stop
all processes, I am not sure. If you do stop them and you can't figure out
what is running to stop it gracefully with using ZJOB to identify the Job,
then use mupip stop.

--
Nancy Anthracite

On Sunday, August 26, 2012, Nancy Anthracite wrote:
> The read-me file that is in the Multibuild indicates that it is not
> concerned if the Domain is missing if it is in a test account and it will
> not try to restart the HL-7 Listeners. Since we don't want to send
> anything to Orlando anyway, I suspect if you just add the domain entry and
> the institution with only the barest of information so it can't really
> find them, you will be OK or if you change your account designation to a
> test account during the install of the Multibuild you will be OK.
>
> See the read-me file in the Multibuild around line 13000
>

[Kevin Toppenberg]

Thanks Nancy,

I'm headed to bed.  Will work on this tomorrow.

Thanks

Kevin

[Kevin Toppenberg]

Nancy,

There must be a version discrepancy between what you have and what I have.

I have opened README_FIRST_BEFORE_read-me-first-build-2009-06-0.txt

and did a search for "XM*999" and there is no instance found.

I then opened read-me-first-build-2009-06-0.txt

and did a search for "XM*999" and there is again not instance found.

I looked in the .csv spreadsheet in that folder, and I don't see anything about the XM*999 patch

So I don't see that the readme provides the information of how to get past this.

I have been following carefully the steps in README_FIRST_BEFORE_read-me-first-build-2009-06-0.txt, and it doesn't say anything about changing from production to a test system.

I did change to a TEST system as you suggested.  I shut down taskman.

Here is an output of ^ZJOB

GT.M Mumps users on 28-Aug-12 07:37:50

Proc. id Proc. name      PS  Device   Routine            MODE     CPU time

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

20157                    S+  pts/3    JOBSET+9^ZSY       -dir   00:00:00

                             /dev/pts/3 OPEN TERMINAL CTRA=$C(3) NOPAST NOESCA N

OREADS TYPE WIDTH=80 LENG=...

                             /tmp/_gtm_sy_20157.tmp OPEN RMS READ :

27753                    hib                             -direct00:00:01

27778                    hib                             -direct00:00:00

27878                    hib                             -direct00:00:02

Total 4 users.

Enter JOB number:

The process 20157 is the console process running ^ZJOB.  The other 3 are not killable.  I think they are system processes somehow.

I then went into the KIDS options and tried to install the build.  When I tried to load it, it told me it was already loaded.  So I chose option 6 to install the BUILD entry.  Again I get the problem with XM*999 (i.e. the ORLANDO site it missing).

So I unloaded the distribution.  Then loaded it again.  Still no go.

Screen log below.

I'm stuck

Kevin

KIDS Distribution saved on Jun 12, 2011@15:37:24

Comment: WorldVistA Multi-build for June 2009 cont.

This Distribution contains Transport Globals for the following Package(s):

   BUILD 2009 06.1

   OR*3.0*212

   DG*5.3*803

   DVB*4.0*61

   PSN*4.0*206

   DG*5.3*792

Build DI*22.0*157 has been loaded before, here is when:

      DI*22.0*157   Install Completed

                    was loaded on Aug 26, 2012@16:06:25

OK to continue with Load? NO// y  YES

   SD*5.3*555

   LR*5.2*309

Build XU*8.0*469 has been loaded before, here is when:

      XU*8.0*469   Install Completed

                   was loaded on Aug 25, 2012@20:39:57

OK to continue with Load? NO// y  YES

   PRC*5.1*122

   QAO*3.0*8

Build XU*8.0*466 has been loaded before, here is when:

      XU*8.0*466   Install Completed

                   was loaded on Aug 25, 2012@20:40:04

OK to continue with Load? NO// y  YES

   FB*3.5*110

   GMRC*3.0*62

   LR*5.2*394

   RA*5.0*96

   DG*5.3*809

Build EC*2.0*99 has been loaded before, here is when:

      EC*2.0*99   Install Completed

                  was loaded on Aug 26, 2012@19:49:41

OK to continue with Load? NO// y  YES

   PSB*3.0*45

   PSJ*5.0*208

   DG*5.3*536

Build GMRA*4.0*42 has been loaded before, here is when:

      GMRA*4.0*42   Install Completed

                    was loaded on Aug 26, 2012@19:52:22

OK to continue with Load? NO// y  YES

   OR*3.0*298

   FB*3.5*107

   FH*5.5*19

   GMTS*2.7*91

   HL*1.6*142

   PSN*4.0*207

Distribution OK!

Want to Continue with Load? YES// y  YES

Loading Distribution...

   BUILD 2009 06.1

Build OR*3.0*212 has an Enviromental Check Routine

Want to RUN the Environment Check Routine? YES//

   OR*3.0*212

Will first run the Environment Check Routine, ORY212E

   DG*5.3*803

   DVB*4.0*61

   PSN*4.0*206

Will first run the Environment Check Routine, PSN206E

   DG*5.3*792

   DI*22.0*157

Will first run the Environment Check Routine, DIPR157

Perform Environment Check...

Checking Function(s) to be deleted from FUNCTION file ^DD("FUNC"...

...Checking for function SETDATA at IEN 57

...Already deleted.

Checking Function(s) to be added to FUNCTION file ^DD("FUNC"...

...Checking for function DUPLICATED at IEN 57

...Found something at that IEN. Checking it out.

...Looks OK - DUPLICATED is already there.

Finished Environment Check.

   SD*5.3*555

   LR*5.2*309

Will first run the Environment Check Routine, LR309

           Sending transport global loaded alert to mail group G.LMI

                        --- Environment Check is Ok ---

   XU*8.0*469

   PRC*5.1*122

   QAO*3.0*8

   XU*8.0*466

   FB*3.5*110

   GMRC*3.0*62

   LR*5.2*394

   RA*5.0*96

   DG*5.3*809

   EC*2.0*99

   PSB*3.0*45

   PSJ*5.0*208

   DG*5.3*536

   GMRA*4.0*42

   OR*3.0*298

   FB*3.5*107

   FH*5.5*19

   GMTS*2.7*91

   HL*1.6*142

Will first run the Environment Check Routine, HLP142

Checking environment ...

'ORLANDO VAMC' entry with station number as 675 does not exist in Institution

file.

'ORLANDO.MED.VA.GOV' entry does not exist in Domain file, patch XM*999*172

must be installed first.

Aborting installation...

HL*1.6*142 Build will not be installed

               Aug 28, 2012@07:43:47

   PSN*4.0*207

Will first run the Environment Check Routine, PSN207E

Use INSTALL NAME: BUILD 2009 06.1 to install this Distribution.

   1      Load a Distribution

   2      Verify Checksums in Transport Global

   3      Print Transport Global

   4      Compare Transport Global to Current System

   5      Backup a Transport Global

   6      Install Package(s)

          Restart Install of Package(s)

          Unload a Distribution

Select Installation Option:

[Nancy Anthracite]

I was not talking about searching for XM*999. I am talking about the initial
HL*1.6*142 patch that failed for you. In the read-me it shows that it was
happy because it was a test system which is why I suggested that you try to
change it to a test system and reinstall it. You don't really want to contact
Orlando anyway, so the default for the test system should be good for you.
Search on HL*1.6*142 and at around line 13000 you will find what happened when
Skip installed it on a test system.

I think the XM*999 seems like a rather suspicious patch name. I wonder if it
was a temporary build what exactly it is.

--
Nancy Anthracite

[Skip]

Kevin, I see you are using HL7, so what you need to do is:

Select OPTION: ENTER OR EDIT FILE ENTRIES

INPUT TO WHAT FILE: DOMAIN// 869.3  HL COMMUNICATION SERVER PARAMETERS
                                          (1 entry)

EDIT WHICH FIELD: ALL// .03  DEFAULT PROCESSING ID
THEN EDIT FIELD:


Select HL COMMUNICATION SERVER PARAMETERS ONE: `1  1
DEFAULT PROCESSING ID: training// ?
     Enter the default PROCESSING ID for this account.
     Choose from:
       P        production
       T        training
DEFAULT PROCESSING ID: training// <===change to "T" for installation, then back to a "P"

The environment check is not checking to see if the site is a VAMC and then checking to see if it is a Production account.  Such is life.

[Nancy Anthracite]

PS, I do not have an XM*999* kids build anywhere.

--
Nancy Anthracite

On Tuesday, August 28, 2012, Nancy Anthracite wrote:
> I was not talking about searching for XM*999. I am talking about the
> initial HL*1.6*142 patch that failed for you. In the read-me it shows
> that it was happy because it was a test system which is why I suggested
> that you try to change it to a test system and reinstall it. You don't
> really want to contact Orlando anyway, so the default for the test system
> should be good for you. Search on HL*1.6*142 and at around line 13000 you
> will find what happened when Skip installed it on a test system.
>
> I think the XM*999 seems like a rather suspicious patch name. I wonder if
> it was a temporary build what exactly it is.
>

[David Whitten]

Typically a XM*999*?? build is an information only build that tells a human to add a new DOMAIN File entry. Some people call them "DBA" builds because the local DataBase Administrator creates the entries.

David

--
http://groups.google.com/group/Hardhats
To unsubscribe, send email to Hardhats+u...@googlegroups.com

[Nancy Anthracite]

I searched for XM*999* and found nothing but I also do not have all of what is
on the VA downloads site currently. I do have mostly the older patches from
FOIA CDs and prior releases.

--
Nancy Anthracite

[Nancy Anthracite]

Here is the section of the read-me I was referring to and Skip has figured out
where it is coming from. I was barking up the wrong tree.

13093 Install Started for HL*1.6*142 :
13094 Jun 13, 2011@13:58:55
13095
13096 Build Distribution Date: Mar 23, 2009
13097
13098 Installing Routines:..................
13099 Jun 13, 2011@13:58:56
13100
13101 Installing Data Dictionaries: ..
13102 Jun 13, 2011@13:58:56
13103
13104 Installing PACKAGE COMPONENTS:
13105
13106 Installing HL LOGICAL LINK..
13107
13108 Couldn't resolve Institution ORLANDO VAMC for Logical Link VAORL
13109
13110 Couldn't resolve Domain ORLANDO.MED.VA.GOV for Logical Link VAORL.
13111 Jun 13, 2011@13:58:56
13112
13113 Running Post-Install Routine: POST^HLP142.
13114
13115 Updating 'VA-VIE' logical link ...
13116
13117 Because this is not a production account, the 'DNS DOMAIN', 'TCP/IP
ADDRESS'
13118 and 'AUTOSTART' fields won't be updated.
13119
13120 Updating 'VAORL' logical link ...
13121
13122 Because this is not a production account, the 'MAILMAN DOMAIN', 'DNS
DOMAIN'
13123 , 'TCP/IP ADDRESS' and 'AUTOSTART' fields won't be updated.
13124
13125 Updating Routine file......
13126
13127 Updating KIDS files.......
13128
13129 HL*1.6*142 Installed.
13130 Jun 13, 2011@13:58:56


--
Nancy Anthracite

[Kevin Toppenberg]

Thank you Skip.  That solved it.  It's so easy when you know what to do.

Thank you also, Nancy, for your help.

Thanks you to everyone else also.

Kevin