New iMO Procedure

Now iMO Helpdesk informed that there is no requirement of getting Static IP. New iMO willl work on any internet connection.
They have to just give one particular IP to their iMO machine provided by the iMO National Coordinatore and do not change it, they have to set it in their TCP/IP properties so that the IP will remain the same.


iMO HELP DESK
Phone: 011-23036054
Fax :011-23096008
email_id : helpdesk.imo@indiapost.gov.in

1.Sri. J. Sukumar, LAN project Officer , Southern Region, Madurai 

( Secretary, AISBCU - (SBCO) Circle Secretary , Tamilnadu)

2.Shri M.Arivalagan, Divisional System Manager, Kanjipuram, Division. He is working as system manager from 19.04.1995 at Kanchipuram Division.

They are promoted as Assistant Accounts Officer in Department of Telecom and joined on 16.02.2010.

Congrats to Both the officials

Guidelines for new iMO software

Annexure-I

 (Guidelines for new iMO software)

This is in continuation of earlier communications from this office, regarding the modifications in the procedure for activation of iMO centers without the use of Digital Smart Cards.

It has been decided by the competent authority that Circle Coordinators would be designated in each Circle who would be the interface between National Coordinator, Dak Bhawan & the iMO Centres in the respective Circles. iMO service will be made available in all connected POs in the Circle.

The detailed presentation in this regard by NIC, is being enclosed for reference and may be circulated to all concerned well in advance. It has been directed by Member (T) that all the connected iMO Centres have to be activated by 15th March 2010.

The request for registration of POs would be filled online, the Supervisor IDs would be created online and user/operator id will be created at the PO level. Machine registration would be done as is being done at present.

The procedure would be as follows: -

1.                  Circles shall designate Circle level coordinators who shall be responsible for registering the Post offices in their respective Circles and sending the registration requests online,to National Coordinator for authorization. Once the National Coordinator authorizes the registration of the Post offices the Supervisor User ID and Password will be created and will be visible to the Circle Coordinator when he logs into the system. He would further communicate the same to the iMO centers who shall then create the operator ID & Password. Also, each Post office shall have 1 Supervisor & 2 operators (Maximum).

2.                  On registration of the Post offices, the post office shall send an online request for registration of the machine for iMO transaction to Circle Coordinator. This procedure would be same as being done at present. The machine registration request shall be sent through the Circle Coordinator to the National Coordinator. Once the machine is authorized the post office shall start the iMO operation.

3.                  A training session would be held by NIC for all the Circle Coordinators, System Managers, DAP officials, Regional & Divisional level officials of all the Circles on 23^rd February 2010 from 1400 Hrs to 1700 Hrs, through Video conferencing. In this the entire procedure including filling up of online request registration forms etc, would explained in detail by NIC. The presentation will also be available on iMO website for reference. It is imperative that the same is distributed to all concerned well in time for better understanding during the training session.

Role and functions of the Circle Coordinator:-

1. Ensuring broadband connectivity with fixed I.Ps in the identified POs.
2. Filling up Registration request form (which will be available online) and sending it to National Coordinator (online).
3. Communicating the Supervisor ID & Password to the concerned PO.
4. Forwarding request for Machine registration request from the PO to National Coordinator.
5. Ensuring activation of the identified centers.
6. Monitoring the entire operation & reporting to National Coordinator.

Role of Post office/iMO Centre : -

1.                  Creation of User ID & Password and operators on receiving Supervisor ID & Password from the Circle Coordinator.

2.                  Getting the operator ID & Password authorized by the Circle Coordinator.

3.                  Download/install iMO software in the system.

4.                  Request for Machine registration to be forwarded to Circle Coordinator.

5.                  Starting iMO operations once Machine is registered.

6.                  Ensuring regular change in passwords & security of operations.

7.                  Providing training to the new operator.

8.                  Activation/deactivation of operator ID & password.

Role of National Coordinator : -

1.                  Authorising request for registration of POs received from Circle Coordinators.

2.                  Authentication of Machine registration request received from the Circle Coordinators.

3.                  Resetting of locked/disabled passwords on request received from Circle Coordinators.

4.                  iMO 16-digit Confidential No. communication in case of specific problem authorized by Circle Coordinator.

5.                  Providing support & guidance in case of any problem.

6.                  Co-ordinating with NIC with regard to any issue in relation to the application.

4.                  The following should be completed before 22^nd February2010 :-

a.       Identifying all internetconnected Post offices as iMO Centres and communicating the same to National Coordinator.

b.      Designation of Circle Coordinators (not below the rank of AD/APMG) by the Circles.

c.       Ensuring availability of Broad band connectivity with Fixed I.P.

Address in all identified locations.

National Coordinator will correspond only with Circle Coordinators & the guidelines should be kept in mind by all concerned for smoother operations. This entire procedure will be applicable for all iMO centers, existing as well as for newly created centers. Any addition, alteration in the above procedure will be communicated as and when applicable.

Department created Postmasters Cadre in the GP Rs 4800, 4600, 4200 and 2800

The Postal Department is more than 150 years old and the qualification for feeding cadre (Postal Assistant) to this Department was only Matriculation. Recently, the qualification for Postal Assistant has been changed as Higher Secondary with some basic computer knowledge.

These officials are promoted to LSG/HSG-II/HSG-I Postmasters as per seniority and the service to the public is depend upon these cadre only. Fast track examination conducted for LSG promotion was also stopped due to various reasons.


However to improve the efficiency further and to cope up with the present technlogical issues, Department has issued orders vide Order No 13-2/2010-PE-I dated 3.2.2010 to constitute Postmaster Cadre which is reproduced as follows:-

It has been decided with the approval of the Competent Authority to constitute a separate cadre of Postmasters with following number of posts by carving them out from the existing General Line Cadre Posts and Postal Services Group - B of Postal Wing and to designate them as Senior Postmaster, Postmaster Grade-III, Postmaster Grade-II and Postmaster Grade-I as detailed below:-

SlNo	Existing Cadre	Proposed Cadre	Number of Posts
1.	Postal Services Group - B Officer	Senior Postmaster Rs 9300-34800 + GP Rs 4800 (PB-3) and Rs 5400 after 4 years(PB-2)	116
2	Higher Selection Grade-I (HSG-I)	Postmaster Grade-III Rs 9300-34800 + GP Rs 4600 (PB-2)	495
3	Higher Selection Grade-II (HSG-II)	Postmaster Grade-II Rs 9300-34800 + GP Rs 4200 (PB-2)	511
4	Lower Selection Grade (LSG)	Postmaster Grade-I Rs 9300-34800 + GP Rs 2800 (PB-2)	2097

The Posts will be deemed to have been designated as Senior Postmaster, Postmaster Grade-III, Postmaster Grade-II and Postmaster Grade-I with effect from the dates these are filled up.
The consequential action like framing of Recruitment Rules shall be taken by the Personnel Division.

ISSUE OF SAs IN JCM SUBJECTS

Click Here




Dear Comrades,

                After the massive attempt made in our Delhi Seminar in getting an exact focus on the what is required for the SAs as democratically decided by SAs has to been submitted in a crystal clear manner  to the NFPE Leadership. In the clarity got from the Delhi Seminar the NFPE leadership has now placed the demand of SAs in the JCM (Standing Committee).

              Those who speak about forming any association should understand what is JCM. The Joint Consultative Missionary (JCM) is the ultimate forum of negotiation between the Government and Staff-side. Staff-side will comprise of Union representatives from the recognised Federation (NFPE & FNPO). The number of representatives of JCM (Staff-side) will be determined based on the strength of the membership in each of the Federations. Hence NFPE being the largest Federation of the Postal employees having more than 70% of the membership will have more number of representatives in the JCM on the other hand FNPO having more or less 30% of the membership will have few representatives accordingly. Hence the bargaining capacity will be more for the Federation having more representatives.

          Hence any individuals having formed any association will not have any legal representation in the JCM which is official negotiating body of Staff issues. Hence in this context the issue of System Administrator as decided by us democractically in the Delhi Seminar is now included in the JCM Subjects submitted. The details of the Subjects submitted to our Department is avaialble in the following link: 

http://www.scribd.com/doc/25981567/JCM-Departmental-Council-Subjects-Final

             Now the date of meeting of JCM Standing Committee will shortly intimated shortly. The meeting in proposed to be held in the month of March. Hence in order get a concrete committment or nod from our DOP placing it as a JCM Subject is very essential. When department has given a nod recordically in JCM almost 60% of the job is over. Then the formal approval from MOF and then finally DOPT has to follow through.

INSPECTOR OF POST - MOVEMENT IN TAMILNADU CIRCLE

Western Region

01. shri.c.kamalesh, ip, tech, ro, coimbatore to be ip, legal cell, ro, coimbatore.
02. shri.r.venkat ragavan, ip, ooty sub dn to be ip, tech, ro, coimbatore.
New IP posting orders.
03. smt.radha to be ip, bd, ro, coimbatore.
04. smt.jayageetha to be ip, dharapuram sub dn, tirupur dn.
05. shri.rajasundaram to be ip, ooty sub dn, nilgiri dn.
06. shri.selvam to be ip, gudalur sub dn, nilgiri dn.
07. ms.bharathi to be ip, atur salem sub dn.
08. ms.hemavathi to be krishnagiri east sub dn, dharamapuri dn.
09. ms.kanimozhi to be rasipuram sub dn, namakkal dn.


Southern Region


01. Shri.Saravanan, IP, MA 4 Sub Dn, Madurai to be OS, RMS MA Dn.
02. Shri.S.Subramanian, IP, Sivaganga to be IP, Karaikudi.
03. Ms.Meenakshi to be IP, Vallioor.
04. Ms.M.Jothilakshmi to be IP, Vedasandur.
05. Ms.Annalakshmi to be IP, Nagercoil West.
06. Ms.M.Uma to be IP, Sivaganga.
07. Shri.P.Selvam to be IP, Gudalur in WR.


CCR  Region


01. Shri.GUnasekar to be IP, Cuddalore to be IP, Vandavasi.
02. Ms.L.Srividya, IP, Pattukottai East to be IP, Sriperumbadur.
03. Ms.Indra, IP, Kallakurichi to be IP, Vellore West.
04. Shri.T.Vivekananda, IP, Gingee.
05. Ms.G.S.Sujatha to be IP, Tiruttani East.
06. Ms.Pratheeba to be IP, Polur.


Central Region
01. Ms.Kalaivani to be IP, Kumbakonam South.
02. Shri.Prabu Sankar to be IP, Thirukoilur.
03. Ms.Sharmila to be IP, Pudukottai South.
04. Shri.Arunachalam to be IP, Alangudi.
05. Shri.Hussain Ahmed to be IP, Orathanad.
06. Shri.Ravishankar to be IP, Pattukottai East.
07. Shri.Thanikachalam to be IP, Cuddalore.


 CONGRATULATIONS TO ALL IPs.

SQL Mirroring Using Batch Files

By : R.SENTHIL KUMAR, SYSTEM ADMINISTRATOR, CHENNAI CITY NORTH DIVISION

MOBILE 9884373390

---

I HOPE OUR SYSTEM ADMINISTRATORS WILL HAVE THE PATIENCE TO READ THE FOLLOWING AND ALSO SUGGEST ANY OTHER BETTER METHODS WHICH THEY ARE ADOPTING AT THEIR RESPECTIVE WORK PLACE

In today's scenario of our department after three to four years of implementation of Total Computerisation we encountering frequent server breakdowns. The AMC service providers also do not attend the Server breakdowns in time which results in total stoppage of office functioning till the Server is set right. Even after the Server is set right we still rely on the automatic "Database maintenance plan" which we configure in SQL Server. But how many of us have consiously made an effort to frequently restore the backup files created vide the Maintenance plans.
In this context recently I have been trying to configure a SQL server mirroring with the existing provision available in SQL server which is called "Replication". Unfortunately though it is an built-in utility available in SQL Server I tried it but its not effective enough because if you configure replication SQL databases from one server to another Server it slows down the entire process on the both the Server which is not desirable.
Hence recently I had glimpse reading about the "OSQL Utility". In OSQL Utility you can display the results of any SQL Query in the command prompt. Just simply try typing the following command in DOS prompt.
osql ?

The above command will show the osql switches that can be used. With this as the baseline I tried to develop a batch program which runs on a client machine automatically when the user logs in. Immediatly when the user logs this batch program will fire in the startup. The prerequisites for running is batch program and the procedure of how to configure a backup server is given below:

1. Configure another client machine and load Windows Server 2003 / 2008 OS. While doing "dcpromo" select the option "Additional Domain Controller for an existing Domain" and give the administrator password and Domain name of the Main Server. At the end of the dcpromo wizard you restart the please check in "Active Directly User and Computers" that the same Domain Users of the Main Server is shown in this also.

2. If you are having all the database files (i.e mdf,ldf and dat files) in a drive other than "C" drive please ensure that the same drive is available in the client machine. Because while restoring the database from a backup file it will be restored in the same drive only. Let us say for example you have all your database files in D drive in the Main Server. In that case create a D drive partion in the client machine also with enough disk space.

3. Create a folder named "backup" in E drive of you Main Server(or any other drive as you wish) share the folder with permissions as "Full control".

4. Install SQL Server 2000 / 2005 in the newly configured client machine (i.e your additional domain controller).

5. Create a folder name "restore" in the newly configured client machine in the D drive.

6. Open SQL query analyser in the newly configured client machine and type the following coding given below and save it with a file name "bkpquery1.sql" in D drive.

BACKUP DATABASE BPRO TO DISK='E:\BACKUP\BPRO.BAK'
BACKUP DATABASE BPLOG TO DISK='E:\BACKUP\BPLOG.BAK'
BACKUP DATABASE COUNTER TO DISK='E:\BACKUP\COUNTER.BAK'
BACKUP DATABASE ECOUNTER TO DISK='E:\BACKUP\ECOUNTER.BAK'
BACKUP DATABASE EMO TO DISK='E:\BACKUP\EMO.BAK'
BACKUP DATABASE EIOD TO DISK='E:\BACKUP\EIOD.BAK'
BACKUP DATABASE IPO TO DISK='E:\BACKUP\IPO.BAK'
BACKUP DATABASE PATCH TO DISK='E:\BACKUP\PATCH.BAK'
BACKUP DATABASE POSPCC TO DISK='E:\BACKUP\POSPCC.BAK'
BACKUP DATABASE POSPCCBACKUP TO DISK='E:\BACKUP\POSPCCBACKUP.BAK'
BACKUP DATABASE POST TO DISK='E:\BACKUP\POST.BAK'
BACKUP DATABASE POSTMAN TO DISK='E:\BACKUP\POSTMAN.BAK'
BACKUP DATABASE PROJECT TO DISK='E:\BACKUP\PROJECT.BAK'
BACKUP DATABASE ROUTING TO DISK='E:\BACKUP\ROUTING.BAK'
BACKUP DATABASE SIGN TO DISK='E:\BACKUP\SIGN.BAK'
BACKUP DATABASE SOSB TO DISK='E:\BACKUP\SOSB.BAK'
BACKUP DATABASE SUBTREASURY TO DISK='E:\BACKUP\SUBTREASURY.BAK'
BACKUP DATABASE TREASURY TO DISK='E:\BACKUP\TREASURY.BAK'

(The above code when executed from the client machine after connecting to the SQL Server instance of Main Server will backup all you databases in the path E:\Backup of the Main Server.)
(Note: in the above coding I have just included the databases of a Sub-Offices only if you are working in an head office incorporate the databases like Accounts, Schedules, CashBook and all other Sanchay Post Sub Office databases)


7. In the same way open SQL Query Analyser in the newly configured client machine and type the following code and save it with the name "restorequery1.sql" in the path "d:\restore".

RESTORE DATABASE BPRO FROM DISK='D:\RESTORE\BPRO.BAK'
RESTORE DATABASE BPLOG FROM DISK='D:\RESTORE\BPLOG.BAK'
RESTORE DATABASE COUNTER FROM DISK='D:\RESTORE\COUNTER.BAK'
RESTORE DATABASE ECOUNTER FROM DISK='D:\RESTORE\ECOUNTER.BAK'
RESTORE DATABASE EMO FROM DISK='D:\RESTORE\EMO.BAK'
RESTORE DATABASE EIOD FROM DISK='D:\RESTORE\EIOD.BAK'
RESTORE DATABASE IPO FROM DISK='D:\RESTORE\IPO.BAK'
RESTORE DATABASE PATCH FROM DISK='D:\RESTORE\PATCH.BAK'
RESTORE DATABASE POSPCC FROM DISK='D:\RESTORE\POSPCC.BAK'
RESTORE DATABASE POSPCCRESTORE FROM DISK='D:\RESTORE\POSPCCRESTORE.BAK'
RESTORE DATABASE POST FROM DISK='D:\RESTORE\POST.BAK'
RESTORE DATABASE POSTMAN FROM DISK='D:\RESTORE\POSTMAN.BAK'
RESTORE DATABASE PROJECT FROM DISK='D:\RESTORE\PROJECT.BAK'
RESTORE DATABASE ROUTING FROM DISK='D:\RESTORE\ROUTING.BAK'
RESTORE DATABASE SIGN FROM DISK='D:\RESTORE\SIGN.BAK'
RESTORE DATABASE SOSB FROM DISK='D:\RESTORE\SOSB.BAK'
RESTORE DATABASE SUBTREASURY FROM DISK='D:\RESTORE\SUBTREASURY.BAK'
RESTORE DATABASE TREASURY FROM DISK='D:\RESTORE\TREASURY.BAK'



8. Now comes the actual part where we are going to write a batch program incorporating the OSQL Utility which will call the backup.sql and restore.sql in its program. The coding of the batch program is as follows given in colours. Type the following code in notepad and save it with some name with extention as *.bat for eg.senthil.bat and not the default as *.txt. Further after creating this batch create a shortcut and paste the shortcut in C:\Documents and Setting\All Users\Startmenu\Program\Startup
:BEGIN
@ECHO OFF
ECHO.
CD\
D:
CD RESTORE
DEL *.BAK
ECHO.
BACKING UP FILES
osql -U SA -P password1 -S SQL_SERVER1 -i D:\RESTORE\BKPQUERY1.sql
ECHO COPYING BACKUP FILES
COPY \\MainServerName\backup D:\RESTORE
ECHO.
ECHO COPY FILES COMPLETED
DEL file://mainservername/backup *.bak
ECHO.
ECHO RESTORATION PROCESS GOING ON PLEASE WAIT
osql -U SA -P password2 -S SQL_SERVER2 -i D:\RESTORE\restorequery1.sql
GOTO BEGIN


INDEX
-----

SQL_SERVER1= The SQL instance name of the Main Server
SQL_SERVER2= The SQL instance name of the newly configure Server (i.e the clinet machine which you loaded with Win 2k3 OS)
password1= The SA password of the Main Server
password2= The SA password of the newly configured Server

DESCRIPTIVE EXPLANATION OF THE ABOVE BATCH PROGRAM STEP BY STEP.

I. I have created a loop with the key words :BEGIN AND GOTO BEGIN which is first and last line of the batch program. This will create a loop so that when the program ends the GOTO will direct the control to the place where it find the word BEGIN. Hence a loop is created.
II. In the next few steps reproduced below I am opening the folder d:\restore (you can know this if you are familiar with DOS commands)
CD\
D:
CD RESTORE

III. In the next step reproduced below I am deleting the existing backup files which are present in the path "d:\restore" as they are file created during previous cycle.
DEL *.BAK

IV. Then I am logging into the SQL Server of the main server and backing up file in the main server itself in the path "E:\BACKUP" of main Server by calling the SQL Query "backup.sql" which we have saved in the client machine in the line given below.

osql -U SA -P password1 -S SQL_SERVER1 -i D:\RESTORE\BKPQUERY1.sql

(Leave a black space between each work after "osql" in the above line except the place where I have written the path)

V. Then in the next step reproduced below I am copying the backup files (*.bak files) from the shared folder of the Main Server to the local folder "d:\restore" of the client machine which we have newly configured.
COPY \\MainServerName\backup D:\RESTORE
After copying the backup files to the client using I am deleting the backup files in the Shared folder of the Main Server with the command
DEL \\MainServerName\backup *.bak

in order to clear the disk space in the Main Server.

VI. Then I am logging into the SQL Server of client machine and calling and executing the SQL Queries stored in the file restorequery1.sql in order to restore the backed up data into the SQL server of the client machine in the following code:

osql -U SA -P password2 -S SQL_SERVER2 -i D:\RESTORE\restorequery1.sql

VII. Then the program completes and starts from the beginning. 




Now the main advantage of using the above program is that you can have a back to back replication of the databases from one Server to another. Further if you are relying on "SQL Database Maintenance Plans" you are not sure whether the backup created can be restored properly. Where as in the above case as the backup and restoration happens back-to-back there wont be any problem.
Further the workload will only be on the Client Machine or the Additional Server which we newly configure and this process will not affect the performance of the Main Server thus ensuring normal functioning.
In the event of failure of the Main Server just go that office edit all the "config.xml" files of our Meghdoot programs in the each of the client machine with the new SQL Server Name and the office is up and running. For Sanchay Post as usual run the DB Analyser and updating the DCL user and the office is up and running.
Yes there will be data loss in the event of failure of the Main Server but the loss will be very minimum to quantity of just data fed in before 20 minutes of 30 minutes would have been lost. The reason being the above batch program to complete one cycle will take some 20 minutes time. If it is an HO and if the databases are more it may take time accordingly.

I HOPE THE ABOVE METHOD IS SUGGESTED WOULD BE USEFUL TO EVERYONE IN REDUCING THE DOWNTIME OF OUR OFFICE FUNCTIONING IN THE EVENT OF A SERVER BREAKDOWN. ANY OTHER BETTER SUGGESTION PLEASE POST IN THIS THREAD IF THIS METHOD IS NOT USEFUL ALSO PLEASE GIVE YOU FEEDBACK IT WILL HELP ME IN REFINING OF FINE TUNING THIS METHODOLOGY.