About masiqmoselli

masiqmoselli · ‎08-04-2021

I've tried use the Reactivate after a Score Increase, and even used some high percentages like 100%, but it still Activing alerts that was closed. About the agregation scenarios, I'm not using it. I'm using the Scenario in row level (think that in english is that way), and I don't have any of the options.

masiqmoselli · ‎08-04-2021

Hello all, I'm using Visual Investigator 10.7 and whenever I close an alert it got active again after the flow execution. In other queues I got it solved (the action of move an alert from one queue to another after flow execution) with priority of strategies and queue. I've noticed that when I close it manually by the disposition on PGAdmin it shows alert_status_id = 'CLOSED' and queue_id equals to the queue the alert was before I close it. But everytime flow runs it gets active. Anyone have any suggestion? Thanks.

masiqmoselli · ‎10-21-2020

Hello everyone, I need some help to convert a number which is stored in string (no problem so far) into an hexadecial. Yet no problem, but the thing is, I got convert it back to either a number or a string when it's needed. Basically what I'm using is: hexa = put(number, hex16.); And it aparently it converts but I don't know if it's possible to convert it back. Thanks in advance.

masiqmoselli · ‎10-15-2020

Hello, this codes is mean't to run all day long everyday. For most of the codes it runs under 10 seconds. It's some analisys which I verify transactions, so it's close as possible of real time. The looping in code don't sound very intresting because I will not have the log for every execution separatedely.

masiqmoselli · ‎10-15-2020

Hi all, At the moment on the code I'm working on I need to schedule some codes on SAS Viya. The problem is that, the default configurations I have don't support the execution interval that I need. On Jobs and Flow when I click on "Schedule" a job and I choose Frequency: "Minute" I got just: 5, 10, 15, 20 and 30 minutes. I need to execute some codes every 2 or 1 minute. That's any configuration or solution that I can use to start this jobs on this intervals? (I know it's on Portuguese-BR, but that's is my screen at this moment.) Thanks in advance.

masiqmoselli · ‎09-22-2020

Thanks @s_lassen using the DBTYPE worked, I created the table and it allows me to simply insert data latter. @jimbarbour Thank you as well, the link you sent also worked, and is a configurantion for the 9.4.

masiqmoselli · ‎09-22-2020

Hello Jim, we make this configuration as you suggest. On 9.4 it worked, but did not worked on viya. Trying to reach other solution for Viya.

masiqmoselli · ‎09-21-2020

Hi Jim, Sorry for the misunderstanding. So I've executed as you asked and got the same error when exporting to SQL Server. The sum of the dates went well on SAS. NOTE: SAS variable labels, formats, and lengths are not written to DBMS tables. ERROR: Error attempting to CREATE a DBMS table. ERROR: CLI execute error: [SAS][ODBC 20101 driver][Microsoft SQL Server]Line 1: Specified scale 27 is invalid..

masiqmoselli · ‎09-21-2020

Using this code, I got an error on SAS and for SQL Server printed missing: PROC SQL; INSERT INTO work.table VALUES( 2, '1893369600'dt) ; quit; run; ERROR: Invalid date/time/datetime constant '1893369600'dt. NOTE: PROC SQL set option NOEXEC and will continue to check the syntax of statements. Using this one, in SAS it worked, and on SQL Server missing: PROC SQL; INSERT INTO work.table VALUES( 2, '01Jan1900:00:00:00'dt) ; quit; run;

masiqmoselli · ‎09-21-2020

Using this PROC SQL returns missing in SQL. PROC SQL; INSERT INTO SQLSERVER.table VALUES( 2, '01Jan1900:00:00:00'dt) ; quit; run; Using to insert in a SAS table, the value is inserted. PROC SQL; INSERT INTO work.table VALUES( 2, '01Jan1900:00:00:00'dt) ; quit; run; Trying to use the value 1893369600 in SQL server I got missing value, and on SAS returned this error: PROC SQL; INSERT INTO work.table VALUES( 2, '1893369600'dt) ; quit; run; ERROR: Invalid date/time/datetime constant '1893369600'dt. NOTE: PROC SQL set option NOEXEC and will continue to check the syntax of statements.

masiqmoselli · ‎09-21-2020

Got the same result here: NOTE: DIFFERENCE_DAYS=21914 DIFFERENCE_SECS=1893369600

masiqmoselli · ‎09-21-2020

Hello Jim, Yes probably SAS is making some conversion, the date on SQL Server makes sense the format is: yyyy-mm-dd:hh:mm:ss. But I searched for this format and SAS do not have specifically this one, so I tried to use informat as SAS specifies: datetime22.3, and anothers like: datetime20., datetime20.2. I tried the conversion, returning each part of the date: year, month, day, etc. And put it together in an string, and try to convert into SAS date. But since SAS don't have this format, I got this errors.

masiqmoselli · ‎09-21-2020

Hello all, I'm trying to export SAS data to SQL Server. This date comes from a SQL Server and goes to another instance (SQL Server as well), whenever I try to export a number or text it run nicely, but on datetime I got an error: NOTE: SAS variable labels, formats, and lengths are not written to DBMS tables. ERROR: Error attempting to CREATE a DBMS table. ERROR: CLI execute error: [SAS][ODBC 20101 driver][Microsoft SQL Server]Line 1: Specified scale 27 is invalid.. I'm simply trying to export this table from my work, to SQL Server, this happens just when I try to export this datetime column. Some infos about the table: Just two columns, the first is number and the second is datetime. SAS is recognizing datetime informat as: datetime22.3; Trying to do it with proc sql: PROC SQL; CREATE TABLE SQLSERVER.table2 AS SELECT c1_number, c2_date FROM work.table; QUIT; Thanks in advance.

Online Status	Offline
Date Last Visited	‎08-24-2023 02:30 PM

Re: Visual Investigator alerts reopening after workflow execution

Visual Investigator alerts reopening after workflow execution

Hexadecimal conversion

Re: Scheduling Jobs on Viya - Every minute

Scheduling Jobs on Viya - Every minute

Re: Error to export datetime into SQL Server

Re: Error to export datetime into SQL Server

Re: Error to export datetime into SQL Server

Re: Error to export datetime into SQL Server

Re: Error to export datetime into SQL Server

Re: Visual Investigator alerts reopening after workflow execution

Re: Hexadecimal conversion

Re: Error to export datetime into SQL Server

Re: Error to export datetime into SQL Server

Re: Error to export datetime into SQL Server

Re: Error to export datetime into SQL Server

Re: Visual Investigator alerts reopening after workflow execution

Visual Investigator alerts reopening after workflow execution

Hexadecimal conversion

Re: Scheduling Jobs on Viya - Every minute

Scheduling Jobs on Viya - Every minute

Re: Error to export datetime into SQL Server

Re: Error to export datetime into SQL Server

Re: Error to export datetime into SQL Server

Re: Error to export datetime into SQL Server

Re: Error to export datetime into SQL Server

Re: Error to export datetime into SQL Server

Re: Error to export datetime into SQL Server

Error to export datetime into SQL Server