We can certainly take this issue up in the Documentathon; it will be a good task to get familiar with the documentation structure and workflow.
I am still working on the task list; I will add this item there unless somebody wants to do the editing in the meantime.
Timo
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of "Johnson, Andrew N. via Tech-talk" <tech-talk at aps.anl.gov>
Reply to: "Johnson, Andrew N." <anj at anl.gov>
Date: Tuesday, 18 July 2023 at 18:46
To: Michael Davidsaver <mdavidsaver at gmail.com>, "Rivers, Mark L." <rivers at cars.uchicago.edu>
Cc: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Subject: Re: PHAS and PINI
On 7/18/23 11:29 AM, Michael Davidsaver via Tech-talk wrote:
On 7/18/23 08:57, Mark Rivers via Tech-talk wrote:
Folks,
Does PHAS control the order in which records with PINI=YES are processing during iocInit, even is SCAN=Passive?
Yes.
https://github.com/epics-base/epics-base/blob/42604fc794b6f26b60db953a230b52c1118d3039/modules/database/src/ioc/misc/iocInit.c#L593-L594
The Release Notes for R3.14.11 (when that was added) said:
PINI Processing and PHAS values
The PINI field now has its own menu type with four more choices, RUN, RUNNING, PAUSE and PAUSED.
The earlier NO and YES values for this field remain
as before and cause the same processing as before. The new values cause records to be processed during the announcement of the new initHookAtIocRun, initHookAfterIocRunning, initHookAtIocPause and initHookAfterIocPaused states
respectively.
Records with PINI=YES will be processed during the iocBuild stage
of iocInit, follwed by records with PINI=RUN during
the iocRun stage and records with PINI=RUNNING during
the initHookAfterIocRunning stage. If an iocPause command
is given, any records with PINI=PAUSE will be processed at the initHookAtIocPause stage
followed by records with PINI=PAUSED will be processed at the initHookAfterIocPaused stage.
A subsequent iocRun command causes the PINI=RUN and PINI=RUNNING records
to be processed again.
The PHAS field now controls the order in which records are processed as a result of the PINI mechanism; within each stage, lower values of PHAS are scanned before higher ones.
I agree that the
dbCommonRecord.html wording could be fixed (in dbCommon.dbd.pod), that page doesn't mention the choices for PINI other than YES either but if you follow the link in the table below to the
menuPini.html file that describes them, and there it also mentions that PHAS is honored during PINI processing.
@Timo — a task for the Documentathon?
- Andrew
--
Complexity is free, it's Simplicity that takes work.