QualityStage (QS) information and files to collect

-
For server job run problems
Commands
  1. Export to a dsx file the job that is failing or has produced unexpected output (including rule sets and match specifications if used).
  2. Provide the input to the above job.
  3. Extract DS log to the above job (from DS Director).
  4. Provide the QS job artifacts using the following method:
    - Ascertain the DS job # by using DS Director>View>Detail (Job no.).
    - Provide the contents of     <IS_HOME>\Server\Projects\{ProjectName}\RT_QS{JobNo} folder.
  5. If the job is run in multi-node, collect information about the number of nodes that are used.
 For GUI problems


Commands
  1. Export to a dsx file the job that is failing or has produced unexpected output (including rule sets and match specifications if used).
  2. Provide screenshots of any error messages.
  3. Provide a replication scenario.
QualityStage Standardization Rules Designer (Information Server 9.1)
Files and Data to collect
Description
<IS_HOME>/Server/Projects/{ProjectName}/RT_QS{JobNo}/*
Collect all files inside the project folder and subfolder with the Job number
<TEMP>/RulesConsoleCache/*
Only on the Engine tier. Collect all files contained in this directory and its subdirectories. They are QualityStage standardized rule-set control files used within QualityStage Standardization Rules Designer

Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more