SSH KEYS Authetication with PuTTY and Linux

Step 1: Run / Open PuTTYgen.exe.

Step 2: Click on Generate button and move the mouser over blank space to generate key. Give a key passphrase.

Step 3: Save Public Key, Private Key

Step 4: Copy to key that you see, in a notepad

Step 5: Login to the Linux box with the user that you want to use.

Step 6: Do not change the directory and create a new directory
             mkdir .ssh
             chmod 700 .ssh
             cd .ssh
             vi authorized_keys2 (this is name to be used)
             Insert / Paste the key copied to the notepad in step 4 above. Ensure that it is one line. This is very important.
             Save and quit the authorized_keys2 file
             chmod 600 authorized_keys

Step 7: Start PAGEANT.exe from your putty software directory. You will see the in your syspanel.
             Your will see an icon the right hand bottom corner.

Step 8: Right click on the pageant icon and choose Add Key. Give the  private key

YOU ARE DONE!!!

Open putty: save an entry as username@servername and enjoy !1

Change Assistant Step Parameters

This a list of parameters that we can use when we are designing a totally customized Change Assistant Template.

Used a customized template in a project where the customer had payroll in 9.2 and Core HR in a lower version. I created a customized template for the upgrade for Core HR. These list came in quite handy so thought of sharing it.

Parameter	Description
#Project=	Used primarily for functions that require a project name, like Build Project, Create Project, and Merge Project. For the Merge Project step type, you can specify two projects separated by a comma. For example, #PROJECT=PRJ656265,PRJ656265_IB_PRE848
#Directory=	Used when you need to run a script that is not located in the one of standard home directories defined for the environment. For example: #Directory=#OutputDirectory
#RunLocation= #FileLocation=	By default the scripts and processes are run on one of the current home directories defined for the environment. However if the script or process needs to run on the old release, you need to specify the old release home directories using the variable #ALL_OLD_PATHS_TGT. Example: #RunLocation=#ALL_OLD_PATHS_TGT #FileLocation=#ALL_OLD_PATHS_TGT
#P1= through #P5=	Used to pass parameters to SQR reports, for example, TEST.sqr. In this case, you would pass the necessary value, such as: #P1=#OutputDirectory
#OutputDirectory=	Used to specify the Output Directory variable that is defined in the Options, Change Assistant, Directories screen.
#NT=	Used for DB2 Command Center, for Non-Terminated SQL Scripts. Note: The #NT parameter applies to DB2 LUW only. It is ignored for DB2 zOS.
#Type=	Enables you to specify the type of record to insert into the project. Choose from the following record types: All Records, Table, View/Query, View/Derived, SubRecord, Stored Procedure, Temporary Table, Dynamic View.
#RCID=	Enables the user to override the run control ID used for Application Engine processes.
#CI =	Connect ID (Used for Data Mover – Tools).
#CW =	Connect password (Used for Data Mover – Tools).
#EXTRACT_DMS=	Extracts DMS export script from file (Used for Data Mover – Tools).
#DBSETUP=	Extracts dbsetup DMS import script from file and database connectivity parameters (Used for Data Mover – Tools).
#UNICODE=	Generates DMS script for UNICODE database (default is NON-UNICODE) (Used for Data Mover – Tools).
#TABLESPACE=	Default tablespace (PTMINITS) (Used for Data Mover – Tools, DB2 LUW, Oracle and Informix only).
#DBSPACE=	Physical dbname.tablespace (PTMINIDB.TABLESPACE) ) (Used for Data Mover – Tools, DB2 z/OS only).
#STOGROUP_TS=	Storage group for tablespace (Used for Data Mover – Tools, DB2 z/OS only).
#STOGROUP_IDX=	Storage group for index (Used for Data Mover – Tools, DB2 z/OS only).
#TABLEOWNER=	Database owner ID (same as sqlid and tableowner) (Used for Data Mover – Tools, DB2 z/OS only).
#INDEXSPC=	Default tablespace (PTMINITS) (Used for Data Mover – Tools, Informix only).
#USE_PRCS_SERVER=	(Used only for ProcessScheduler step types). Enter the name of the Process Scheduler server to run the step. Valid values are SERVER1 or SERVER2, which correlate to the Process Scheduler server definitions you have defined in your upgrade environment.
#PROCESS_TYPE=	(Used only for ProcessScheduler step types). Enter the process type, as defined in Process Scheduler. For example, Application Engine, SQR Report, Data Mover, and so on. Note: This parameter is case sensitive. That is, the value must appear in the exact case as the process type in Process Scheduler. For example, for an Application Engine program, the process type parameter should appear as PROCESS_TYPE=Application Engine, not PROCESS_TYPE=APPLICATION ENGINE.
#PROCESS_NAME=	(Used only for ProcessScheduler step types). Enter the process name, such as DDDAUDIT.
#RUNCONTROLID=	(Used only for ProcessScheduler step types). Enter the appropriate run control ID. Note: If NUM_INSTANCES is greater than one, Change Assistant will append unique sequence numbers to the end of the Run Control ID before requests are submitted to the Process Scheduler. This is required for submitting multiple instances of the same process. If NUM_INSTANCES is equal to one, Change Assistant will NOT append unique sequence numbers to the end of the Run Control ID.
#NUM_INSTANCES=	(Used only for ProcessScheduler step types). Used by Change Assistant to schedule multiple processes through Process Scheduler as individual process requests. However, the actual number of instances simultaneously executed on the Process Server is controlled by the Max Concurrent setting for the process type in the Process Scheduler server definition.
#TST	Used with the PTFTest step to identify the test
#TC	Used with the PTFTest step to identify the test cas.
#PFX	Used with the PTFTest step to identify the test prefix

Variable	Description
#ALL_PATHS_TGT	Uses the path values defined for the target database current environment.
#ALL_PATHS_SRC	Uses the path values defined for the source database current environment.
#ALL_PATHS_ODMO	Uses the path values defined for the copy of demo database current environment.
#ALL_PATHS_PROD	Uses the path values defined for the production database current environment.
#ALL_OLD_PATHS_TGT	Uses the path values defined for the target database old environment.

#PLATFORM_TGT	Uses the platform values defined for the target database current environment.
#PLATFORM_SRC	Uses the platform values defined for the source database current environment.
#PLATFORM_ODMO	Uses the platform values defined for the copy of demo database current environment.
#PLATFORM_PROD	Uses the platform values defined for the production database current environment.

Platform Used in Command Line, Press Enter to collapse

Steps where the command line includes the platform are:

·         ApplicationEngine

·         ApplicationEngineWithRunControl

·         BuildProject

·         CompareAndReport

·         CopyDatabase

·         CopyfromFile

·         CopyToFile

·         CreateProject

·         MergeProject

·         DataMoverBootstrap

·         DataMoverUser

Converting nVision Reports (Tools Upgrade)

After upgrading tools version and moving from msoffice 2003 to 10 we have to convert the nvision reports used in PeopleSoft FSCM.

It is fairly simple and here are the 12 steps .. just follow


1.  Download MS Office conversion utility and install 
      Link to download
      or
      search for nvision MigrationPlanningManager.exe in Google
2.  Take a backup of nvision directory
3.  Navigate to %PS_HOME%\nvision\LAYOUT
4.  Rename all xnv files to xls 
      for /R %1 in (*.xnv) do ren "%1" "%~n1.xls"
5.  Navigate to the directory where you have downloaded the conversion utility
6.  Edit ofc.ini
7.  Change the location to pick xls files: change it to  %PS_HOME%\nvision\LAYOUT in ofc.ini file
8.  Run ofc.exe - this will convert all xls file to xlsx
9.  It will created "Converted" directory under %PS_HOME%
10. Rename %PS_HOME%\nvision\ %PS_HOME\nvision_b4_conversion
11. Copy -R %PS_HOME%\Converted\nvision %PS_HOME%\nvision
12. Rename all xlsx files to xnv
     for /R %1 in (*.xlsx) do ren "%1" "%~n1.xnv"

PTUPGCONVERT FAILS : UPGPTHASH

Run the SYSAUDIT and try to clear them.

Thanks to Smart Panda.

Check for Licensecodes as well depending on the error.

PeopleCode-1:

DELETE FROM PSPCMNAME WHERE NOT EXISTS (SELECT ‘X’FROM PSPCMPROG B WHERE B.OBJECTID1 = PSPCMNAME.OBJECTID1 AND B.OBJECTVALUE1 = PSPCMNAME.OBJECTVALUE1 AND B.OBJECTID2 = PSPCMNAME.OBJECTID2 AND B.OBJECTVALUE2 = PSPCMNAME.OBJECTVALUE2 AND B.OBJECTID3 = PSPCMNAME.OBJECTID3 AND B.OBJECTVALUE3 = PSPCMNAME.OBJECTVALUE3 AND B.OBJECTID4 = PSPCMNAME.OBJECTID4 AND B.OBJECTVALUE4 = PSPCMNAME.OBJECTVALUE4 AND B.OBJECTID5 = PSPCMNAME.OBJECTID5 AND B.OBJECTVALUE5 = PSPCMNAME.OBJECTVALUE5 AND B.OBJECTID6 = PSPCMNAME.OBJECTID6 AND B.OBJECTVALUE6 = PSPCMNAME.OBJECTVALUE6)

PeopleCode-2:

DELETE FROM PSPCMPROG WHERE NAMECOUNT <> 0 AND NOT EXISTS (SELECT ‘X’FROM PSPCMNAME B WHERE PSPCMPROG.OBJECTID1 = B.OBJECTID1 AND PSPCMPROG.OBJECTVALUE1 = B.OBJECTVALUE1 AND PSPCMPROG.OBJECTID2 = B.OBJECTID2 AND PSPCMPROG.OBJECTVALUE2 = B.OBJECTVALUE2 AND PSPCMPROG.OBJECTID3 = B.OBJECTID3 AND PSPCMPROG.OBJECTVALUE3 = B.OBJECTVALUE3 AND PSPCMPROG.OBJECTID4 = B.OBJECTID4 AND PSPCMPROG.OBJECTVALUE4 = B.OBJECTVALUE4 AND PSPCMPROG.OBJECTID5 = B.OBJECTID5 AND PSPCMPROG.OBJECTVALUE5 = B.OBJECTVALUE5 AND PSPCMPROG.OBJECTID6 = B.OBJECTID6 AND PSPCMPROG.OBJECTVALUE6 = B.OBJECTVALUE6)

PeopleCode-3:

UPDATE PSPCMPROG SET NAMECOUNT = (SELECT COUNT(*) FROM PSPCMNAME C WHERE C.OBJECTID1 = PSPCMPROG.OBJECTID1 AND C.OBJECTVALUE1 = PSPCMPROG.OBJECTVALUE1 AND C.OBJECTID2 = PSPCMPROG.OBJECTID2 AND C.OBJECTVALUE2 = PSPCMPROG.OBJECTVALUE2 AND C.OBJECTID3 = PSPCMPROG.OBJECTID3 AND C.OBJECTVALUE3 = PSPCMPROG.OBJECTVALUE3 AND C.OBJECTID4 = PSPCMPROG.OBJECTID4 AND C.OBJECTVALUE4 = PSPCMPROG.OBJECTVALUE4 AND C.OBJECTID5 = PSPCMPROG.OBJECTID5 AND C.OBJECTVALUE5 = PSPCMPROG.OBJECTVALUE5 AND C.OBJECTID6 = PSPCMPROG.OBJECTID6 AND C.OBJECTVALUE6 = PSPCMPROG.OBJECTVALUE6)

PeopleCode-4, PeopleCode-5, PeopleCode-6:

Open the PeopleCode program in Application Designer and correct the invalid reference

PeopleCode-7:

DELETE FROM PSPCMPROG WHERE OBJECTID1 = 104 AND OBJECTID2 = 107 AND OBJECTVALUE2 NOT IN (SELECT APPCLASSID FROM PSAPPCLASSDEFN P WHERE P.PACKAGEROOT = OBJECTVALUE1 AND P.APPCLASSID = OBJECTVALUE2)

Fort with 19 tower's "buruj" .. Mahadji Shinde's Rajwada at Jamgaon

JAMGAON FORT

FORT WITH 19 TOWERS

My son Ameya loves going to treks and exploring new places with history attached , May vacations are the best times to do these activities. After his Rajgad trek .. I decide to take him to Jamgaon fort. 

This fort which is now being used as a school. Probably because it is at ground level .. to treks required. Hon. Mahadji Shinde's descendants donated it to the Rayat Shikshan Sanstha. Now you can see classes being held inside the fort.

The first thing that caught me was that his fort has 19 buruj (tower) , curved structure that you see below.

Rayat Sanstha is doing pretty good job with maintaining the interiors.

Mahadji Shinde

Wounded in the bloodshed at Panipat, he inherited the throne. He brought in new methods of warfare. He was a part of the Maratha Army that conquered the Red Fort in 1769. By 1792 Sindhias triumph was complete. His hold over the Maratha Empire in the name of the Peshwa was sealed and defacto over the nominal empire of the Mughals. His name and fame had brought the once proud Mughals and Afghans to their knees and humbled the power of the otherwise victorious British Empire. He had to leave this world in 1795 at a considerably young age.

How do you Reach Jamgaon.

Jamgaon is just 26 kms before reaching Ahmednagar. 

From Pune take the Nagar Road and keep going and cross Shikrapur - Ranjangaon - Karegaon - Shirur - take a left to go Ralegan Siddhi(Anna Hazare) - panoli - parner - Jamgaon.

It's  103 Kms from Pune Raliway Station.

Sharing some photographs.

Entrance 

From the entrance

Rajwada

Rajwada

100 year old bullock Cart

For the Parents

Shree Ram Temple

 Outside the Fort