topic Re: Problem with encoding CIS in Administration and Deployment

Problem with encoding CIS

grudos20 — Tue, 28 Jun 2022 16:56:51 GMT

Hi all.

We deployed a test environment and applied the settings as a production environment, completely the same. Os Linux(utf -8) server encoding was chosen, local language is Portuguese.
But for some reason, the data pulled into SAS CIS is displayed in incomprehensible characters, as if the encoding has gone astray.
To check, we decided to connect the test environment to the database of the production environment, but we still get strange characters in SAS CIS, which means that the problem is not in the Oracle database.
The info-map is imported from the production circuit, but I don't think it could be the problem.
Please share your ideas what could be the reason?

Re: Problem with encoding CIS

grudos20 — Wed, 29 Jun 2022 09:38:29 GMT

A few more points that may be useful to understand:
1. Installation was carried out in the following order:
meta date 01, 02, 03 (configuration and installation of the cluster);
wipd (configuration and installation); SASAppMA (installer) ;
SASAppEM (installation); Middle tear (installer);
SASAppMA (configuration);
SASAppEM (configuration);
Middle tear (configuration);
Middle tear kit (configuration);
Middle tear cis (configuration);

On the production environment, the encoding is displayed correctly, but on the test environment, strange characters are displayed.

Re: Problem with encoding CIS

SASKiwi — Thu, 30 Jun 2022 02:45:07 GMT

Run PROC CONTENTS on one of the problem tables and post what the encoding is like this:

Re: Problem with encoding CIS

grudos20 — Thu, 30 Jun 2022 07:33:46 GMT

Hey,
done:

Data Set NameWORK._PRODSAVAILObservations8

Member Type	DATA	Variables	6
Engine	V9	Indexes	0
Created	30.06.2022 10:26:34	Observation Length	78
Last Modified	30.06.2022 10:26:34	Deleted Observations	0
Protection		Compressed	BINARY
Data Set Type		Reuse Space	NO
Label		Point to Observations	YES
Data Representation	SOLARIS_X86_64, LINUX_X86_64, ALPHA_TRU64, LINUX_IA64	Sorted	NO
Encoding	utf-8 Unicode (UTF-8)

This is a table from which data is opened incorrect CIS

The CONTENTS Procedure

Data Set NameCICOMMON.AGENT_INFOObservations.
Member Type	DATA	Variables	7
Engine	ORACLE	Indexes	0
Created	.	Observation Length	0
Last Modified	.	Deleted Observations	0
Protection		Compressed	NO
Data Set Type		Sorted	NO
Label
Data Representation	Default
Encoding	Default

Schema/Userci_commonEngine/Host Dependent Information

Client version:

19.3.0.0.0

Server version:

19.0.0.0.0

7AGENT_CLASSIFIERChar1020$1020.$1020.AGENT_CLASSIFIERAlphabetic List of Variables and Attributes# Variable Type Len Format Informat Label

AGENT_ID

Num

AGENT_ID

AGENT_NAME

Char

1020

$1020.

AGENT_NAME

CHANNEL_ID

Num

CHANNEL_ID

CHANNEL_NAME

Char

1020

$1020.

CHANNEL_NAME

LEVEL_1

Char

$84.

LEVEL_1

LEVEL_2

Char

$64.

LEVEL_2

Re: Problem with encoding CIS

SASKiwi — Thu, 30 Jun 2022 22:18:25 GMT

Might be worth just confirming your CIS session encoding by running this:

proc options option = encoding;
run;

I'd also recommend opening a SAS Tech Support track as CIS is a specialist product that not many on the Communities use.

Re: Problem with encoding CIS

grudos20 — Fri, 01 Jul 2022 07:37:50 GMT

Hi, thanks for the reply.
Unfortunately, CIS does not have a line or field for executing a command for a specific session. Accordingly, such a parameter must be written in the configuration file, but in which configuration file and in what form to enter the command - I do not know.
We cannot contact SAS support, because There are some complications, not that I don't want to.

Re: Problem with encoding CIS

SASKiwi — Sun, 03 Jul 2022 23:14:36 GMT

I've never used CIS, but behind the application would be a SAS Compute (App) server which you could start a "vanilla" SAS session on using Enterpriser Guide or SAS Studio. These would allow you to run any SAS code.

Re: Problem with encoding CIS

grudos20 — Thu, 01 Dec 2022 08:09:17 GMT

Hi
The problem was solved, we added a few settings
On the operating system, the NLS we need was prescribed
export NLS_LANG=
After we added the encoding we needed in the file
...../SASHome/SASFoundation/9.4/sasv9_local.cfg
-encoding *substitute language*

Hope this helps someone