Advertisements

#Qlikview preceding Load versus resident Load wisdom of HIC

I would put any transformation or string operation or creation of a new field in a preceding Load, rather than in a resident Load. I.e. if possible – always choose preceding Load.

But there are some transformations you cannot do in a preceding Load, e.g anything that you want to do after a Crosstable Load or after a Join. For these I would use a resident Load.

From

https://community.qlik.com/blogs/qlikviewdesignblog/2013/03/04/preceding-load

Advertisements

automate juniper switch backup

From KB11194 http://kb.juniper.net/InfoCenter/index?page=content&id=KB11194

JUNOS Command Line interface allows the user to export the configuration file into an FTP server and to import it back to the switch. The information below describes the steps to backup and restore JUNOS configuration file on FTP server.

Backup configuration file on FTP.

The following configuration sample shows how to backup the JUNOS configuration file on FTP server.

On every commit applied on CLI, the EX switch will transfer a copy of the configuration file to an ASCII file on FTP server. The filename created on the FTP server contains hostname, date and time signature.

system {

archival {

configuration {

transfer-on-commit;

archive-sites {

“ftp://username:password@172.30.36.59”;

}

}

}

}

A first chance exception of type ‘System.DllNotFoundException’ occurred in System.Data.SQLite.dll solution

Copy all the .dlls from System.Data.SQLite\2010\bin into your debug\release bin

Use rConfig to backup an F5

Don’t bother

Just download the F5 backup appliance

http://sourceforge.net/projects/f5configbackup/

http://sourceforge.net/p/f5configbackup/wiki/Appliance1.0/

How to actually get the AS400 oledb connection with .net

Get yourself a copy of DB2OLEDBV4_x86.msi (or a 64 bit version DB2OLEDBV4_x64.msi)

Get yourself the Microsoft Visual C++ Redistributable Package http://www.microsoft.com/en-us/download/confirmation.aspx?id=8328

Or get the 64bit version as well

Install yourself a version of SQL Server 2008 or later version

And… get yourself a copy of .net 4.0 yeesh

OK….. after fighting that for way too long time to try the IBM odbc driver.

It is downloaded from here

https://www-304.ibm.com/support/docview.wss?uid=swg27016878

Have fun getting an account and getting the Driver for ODBC and CLI (64-bit) downloaded

Then unzip it and run

cd <uncompressed driver folder>/bin
db2cli install -setup

Now I have a new data source called IBM DB2 ODBC DRIVER

Scratch that, I finally got the stupid OLEDB driver to work. The key is to use verbatim string literal (which doesn’t exist in vb.net) So instead use <![CDATA[
SELECT * FROM [TABLE] where RTTICK = ‘852’
]]>.Value

From this post

https://mikearnett.wordpress.com/2013/04/12/query-db2-from-net/#comment-650

Dim connectionString As String = “Provider=DB2OLEDB;User ID=;Password=;Initial Catalog=;Network Transport Library=TCPIP;Host CCSID=1208;PC Code Page=1252;Network Address=;Network Port=446;Package Collection=;Default Schema=;Units of Work=RUW;Default Qualifier=;DBMS Platform=DB2/AS400;Use Early Metadata=False;Defer Prepare=False;DateTime As Char=False;Rowset Cache Size=0;Binary CodePage=0;Datetime As Date=False;AutoCommit=True;Database Name=;Authentication=Server;Decimal As Numeric=False;Derive Parameters=True;LoadBalancing=False;Persist Security Info=True;Cache Authentication=False;Connection Pooling=False;”

Using connection = New OleDbConnection(connectionString)

Dim command = New OleDbCommand()
command.CommandText = <![CDATA[
SELECT * FROM [TABLE] where RTTICK = ‘852’
]]>.Value

command.Connection = connection
connection.Open()
Dim reader = command.ExecuteReader()
If reader.HasRows Then
While reader.Read()
System.Diagnostics.Debug.Write(reader.GetValue(1))
End While
reader.Close()
End If
connection.Close()
End Using