[Jay Hammond]

From the documentation:

 

Host Server Version Control tab

In some situations, the administrator must directly revise the configuration file’s version status. For doing this, the Server Administration tool has a a Version Control tab to list version records. Users can update the version status in this tab.

• Selecting Root lists the root-level version records.
• Selecting Site enables the site name list. When a user selects a site from the list, the tab shows the specified site’s version records.

The administrator can revise the configuration file’s version status by these actions:

• Selecting Unlock to unlock the selected configuration entries.
• Selecting Remove to remove the selected configuration entries. All history version records of the selected configurations are removed from the version database and folder.
• Selecting Refresh to reload the table components.

[Jay Hammond]

Admins are able to unlock versioned files in this case (we’re on Version 20.1).  In the hciserveradmin GUI, in the Version Control tab.  See the attached screenshot.

Attachments:

You must be logged in to view attached files.

[Jay Hammond]

Very cool!  Thank you, Robert.

I have one site listed thrice (willow_pharmacy) as well as another listed twice (vcloverleafdeva1) like your list:
<p style=”padding-left: 40px;”>$ ps -ef | grep -i -e hcimon -e stime | grep -v grep
UID PID PPID C STIME TTY TIME CMD
hci 14352792 1 0 May 18 – 15:06 /hci/cis20.1/integrator/bin/hcimonitord -cl default.alrt -S hcidev_in
hci 14614886 1 0 May 18 – 1:01 /hci/cis20.1/integrator/bin/hcimonitord -cl default.alrt -S acc_reg_cycle
hci 22806974 1 0 May 18 – 0:28 /hci/cis20.1/integrator/bin/hcimonitord -cl default.alrt -S vcloverleafdeva1
hci 24314290 1 0 May 18 – 0:48 /hci/cis20.1/integrator/bin/hcimonitord -S willow_pharmacy
hci 24838534 1 0 May 18 – 0:37 /hci/cis20.1/integrator/bin/hcimonitord -cl default.alrt -S education
hci 25297248 1 0 May 18 – 1:05 /hci/cis20.1/integrator/bin/hcimonitord -cl default.alrt -S hcidev_tst2
hci 26476944 1 0 May 18 – 1:10 /hci/cis20.1/integrator/bin/hcimonitord -cl default.alrt -S him
hci 28836296 1 0 May 18 – 1:44 /hci/cis20.1/integrator/bin/hcimonitord -cl disabled_alerts.alrt -S willow_pharmacy
hci 5112428 1 0 May 18 – 0:28 /hci/cis20.1/integrator/bin/hcimonitord -cl disabled_alerts.alrt -S vcloverleafdeva1
hci 5636802 1 0 May 18 – 0:25 /hci/cis20.1/integrator/bin/hcimonitord -cl default.alrt -S resource_management
hci 7078568 1 0 May 18 – 5:24 /hci/cis20.1/integrator/bin/hcimonitord -cl default.alrt -S hoke
hci 9437764 1 0 May 18 – 0:38 /hci/cis20.1/integrator/bin/hcimonitord -cl default.alrt -S midas
hci 9765398 1 0 May 18 – 1:04 /hci/cis20.1/integrator/bin/hcimonitord -cl default.alrt -S hcidev_documents
hci 14156540 1 0 May 18 – 1:29 /hci/cis20.1/integrator/bin/hcimonitord -cl default.alrt -S hcidev_device_int
hci 15270416 1 0 May 18 – 1:13 /hci/cis20.1/integrator/bin/hcimonitord -cl default.alrt -S hcidev_cupid_rad
hci 15991426 1 0 May 18 – 23:48 /hci/cis20.1/integrator/bin/hcimonitord -cl default.alrt -S hcidev_out
hci 17826444 1 0 May 18 – 7:10 /hci/cis20.1/integrator/bin/hcimonitord -cl default.alrt -S hcidev_adt_mfn_chgs
hci 21168758 1 0 May 18 – 3:02 /hci/cis20.1/integrator/bin/hcimonitord -cl default.alrt -S hcidev_ord_res
hci 23331492 1 0 12:20:40 – 0:00 /hci/cis20.1/integrator/bin/hcimonitord -S willow_pharmacy
hci 24314620 1 0 May 18 – 1:05 /hci/cis20.1/integrator/bin/hcimonitord -cl default.alrt -S hcidev_case_mgnt
hci 26215024 1 0 May 18 – 3:28 /hci/cis20.1/integrator/bin/hcimonitord -cl default.alrt -S hcidev_beaker
hci 29360820 1 0 May 18 – 0:39 /hci/cis20.1/integrator/bin/hcimonitord -cl default.alrt -S hcidev_labor_deliv</p>
After a bit of digging, it looks like the sites listed twice may be due to a manual stop/start of the monitor daemon.  And the process isn’t removed from the list?

On the 18th, I was testing out starting/stopping monD with different *.alrt files; I guess that’s why those show up multiple times in the list with -cl <alert_name>.  I tried stopping monD in the willow_pharmacy site and the most recent entry was removed until I restarted and it showed again.  I also tried stopping/starting the host server for shiggles, but that didn’t change anything either.

Also appears that maybe Linux and AIX list things slightly differently (e.g. AIX is showing -cl <alert_name> for all sites) which isn’t surprising.

[Jay Hammond]

Thank you, Tim!  That will definitely work. I was just hoping there was something I couldn’t find with the hcisitectl (or any other) command that would return the active file name for a quick look.

[Jay Hammond]

Does this get what you’re looking for:

 

hcigvt
This command is used to access the global variables.

hcigvt {add|del|get|set|show} [varname] [varvalue] [isencrypted]
add – adds the global variable to the variable table.
del – deletes the global variable name from the variable table.
get – prints the global variable value of varname.
set – sets the global variable value of varname to a new value.
show – shows all the variable names and values in local site.
varname is the global variable name.
varvalue is the global variable value.
isencrypted determines if the global variable must be encrypted in the ini file.
1 indicates it is encrypted.
0 indicates it is not encrypted. This is the default.
For example:

C:\cloverleaf\cis6.3\integrator\bin>hcigvt show

• This reply was modified 1 year, 7 months ago by Jay Hammond.
• This reply was modified 1 year, 7 months ago by Jay Hammond.
• This reply was modified 1 year, 7 months ago by Jay Hammond.

[Jay Hammond]

I’ve attached a couple that I use from time to time to pull at least some of the info that you’re looking for.

• This reply was modified 1 year, 8 months ago by Jay Hammond.

Attachments:

You must be logged in to view attached files.

[Jay Hammond]

I agree.

[Jay Hammond]

There’s also a place on the Infor Concierge to enter and vote on enhancements, though I don’t know if many people use it.  I have entered a couple and the status on them changed from Received to In Review or something.  I can’t tell right now because the Enhancements page won’t load on the Concierge site (which seems to happen a lot), lol.  I’ve attached a screenshot of where it’s located on that site.

 

 

Attachments:

You must be logged in to view attached files.

[Jay Hammond]

I’ll be.  It’s so simple.  Thank you very much!

[Jay Hammond]

Jim,

I’m interested in the alert you have set up for the minimal.alrt.  How is that set up? Are you using a file change alert?  If so, what criteria do you have in the alert?

I have a script that we can run with options to either enable or disable all alerts in all sites.  When disable is chosen, it renamed the default.alrt and creates a new default.alrt file with nothing in it except a prologue.  If enable is chosen it renames the default.alrt (which is the deactivated one) with a timestamp in the name and renames the real file back to default.alrt.

I’d love to be able to alert our team if we don’t re-enable the default.alrt as you mentioned.

If anyone wants to see my chicken scratch script, I’ll be happy to share.

[Jay Hammond]

I’ve attached two eoaliases that I either found on here or read about on here and downloaded from the Infor Support site.  They’ve worked on version 6.2 and 20.0.1.

Maybe these will do what  you’re looking for.

EDIT:  I had to add a .txt extension to be able to upload the files.  Also, we’re on AIX if that matters with these.

 

• This reply was modified 2 years, 2 months ago by Jay Hammond.
• This reply was modified 2 years, 2 months ago by Jay Hammond.
• This reply was modified 2 years, 2 months ago by Jay Hammond.

Attachments:

You must be logged in to view attached files.

[Jay Hammond]

Be sure there is a space between eq and =

value eq =Y

That’s bitten me a few times.

[Jay Hammond]

Thank you, Keith.

[Jay Hammond]

Wait, so if I check “Do not truncate any field content,” Cloverleaf will ignore the field lengths set at the segment level?  So that for, say, PDF messages, I don’t have to remember to go back and set the OBX-5 field to unlimited?!  If that’s the case, I wish I’d seen this before; like, years ago, lol.

Are there any reasons that one would NOT want to check that box?

[Jay Hammond]

This came up a couple of years ago and I dug the following up from a couple Infor support cases where I’d asked the same question:

I’ve opened two separate Incidents with Infor when planning for OS or Cloverleaf upgrades and have been told the following on 8/1/17:

We mainly care about the core version of the OS.
In your case 7.1 is a supported platform.
We do not test or certify against all TL or patches.
We document the TL we tested in the rel notes.

And this past week (8/20/19) was told pretty much the same by different support staff at Infor:

The PowerHA is transparent to CL and is not a concern.
The TL levels are not a concern either as we mainly care about the supported core version.
For example AIX 7.1, 7.2, etc..
The TL in the release notes is the TL that was certified/tested at the time of release.

[Author]

Replies